From Zimbra :: Wiki

Contents 1 Zimbra usage notes 1.1 Less known settings 1.1.1 COS/Domain settings 1.1.2 Disable View Mail button 1.2 Usefull zmprov commands 1.2.1 Reindex account items 1.3 Usefull wiki pages 2 Zimbra troubleshooting notes 2.1 NE upgrade 5.0 to 6.0 2.1.1 mailboxd not running 2.2 General common issues 2.2.1 Admin console errors

Zimbra usage notes

Less known settings

COS/Domain settings

• zimbraMaxMailItemsPerPage <integer> - Change maximum allowed items per page
• zimbraFeatureWebSearchEnabled <boolean> - Disable Yahoo! search bar
• zimbraDataSourceRssPollingInterval <interval> - Change polling interval for remote RSS feeds
• zimbraDataSourceCalendarPollingInterval <interval> - Change polling interval for remote Calendars

Disable View Mail button

Use the adminLoginAs ACL right...

Usefull zmprov commands

Reindex account items

• zmprov rim <account> [start|status|cancel]

Usefull wiki pages

• Improving Anti-spam system
• Recreating a Self-Signed SSL Certificate (In 6.x you can do this with "Install Certificate" in de Admin UI)
• Tuning Postfix Settings
• Legal Intercept

Zimbra troubleshooting notes

NE upgrade 5.0 to 6.0

mailboxd not running

If mailboxd fails to start and you see the following exception in /opt/zimbra/log/zmmailboxd.out the fix seems to be to run the following command

zmprov -l mcf zimbraMailUseDirectBuffers TRUE

1326 WARN  [main] log - Config error at <Set name="useDirectBuffers"/>
1326 WARN  [main] log - Config error at <Call name="addConnector"><Arg>
        <New id="http" class="org.mortbay.jetty.nio.SelectChannelConnector"><Set name="port"><SystemProperty name="jetty.port" default="80"/></Set><Set name="maxIdleTime">30000</Set><Set name="lowResourceMax
IdleTime">1000</Set><Set name="Acceptors">2</Set><Set name="confidentialPort">443</Set><Set name="useDirectBuffers"/></New>
      </Arg></Call>
1327 WARN  [main] log - EXCEPTION
java.lang.NoSuchMethodException: class org.mortbay.jetty.nio.SelectChannelConnector.setUseDirectBuffers(class java.lang.Object)
        at org.mortbay.xml.XmlConfiguration.set(XmlConfiguration.java:424)
        at org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:248)
        at org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:626)
        at org.mortbay.xml.XmlConfiguration.itemValue(XmlConfiguration.java:915)
        at org.mortbay.xml.XmlConfiguration.value(XmlConfiguration.java:837)
        at org.mortbay.xml.XmlConfiguration.call(XmlConfiguration.java:523)
        at org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:252)
        at org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:214)
        at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:974)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.mortbay.start.Main.invokeMain(Main.java:194)
        at org.mortbay.start.Main.start(Main.java:523)
        at org.mortbay.start.Main.main(Main.java:119)

General common issues

Admin console errors

If you get this message when you access server settings in zimbra admin console

Message: system failure: exception during auth {RemoteManager: mail.mymailserver.com->zimbra@mail.mymailserver.com:22} Error code: service.FAILURE Details:soap:Receiver

you should check if the zimbra user is able to login via ssh. As the zimbra user run:

ssh -vi ~/.ssh/zimbra_identity -o strictHostKeyChecking=no zimbra@server.domain.tld -p 22

Check if ssh is running and that there isn't a firewall blocking ssh access and if those are ok run the following commands:

zmsshkeygen #Generates new ssh key
zmupdateauthkeys #Deploys new ssh key