Not An IMAP4 Server: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
{{Article Infobox|{{admin}}|{{ZCS 6.0}}|{{ZCS 5.0}}|}} | {{Archive}}{{Article Infobox|{{admin}}|{{ZCS 6.0}}|{{ZCS 5.0}}|}} | ||
==Summary== | ==Summary== | ||
This error may be experienced when setting up IMAP in a Mozilla Thunderbird mail client to connect to a server running Zimbra proxy. | This error may be experienced when setting up IMAP in a Mozilla Thunderbird mail client to connect to a server running Zimbra proxy. |
Latest revision as of 17:59, 24 March 2015
Article Information |
---|
This article applies to the following ZCS versions. |
Summary
This error may be experienced when setting up IMAP in a Mozilla Thunderbird mail client to connect to a server running Zimbra proxy.
"Mail server {name} is not a IMAP4 mail server."
The issue is described here http://kb.mozillazine.org/Not_an_IMAP4_server.
Cause
The problem is likely due to one or more missing IMAP capabilities for the Nginx proxy that is included with ZCS.
Solution
Make sure the default list of IMAP capabilities is configured for the proxy server.
Check the running configuration
At a shell prompt on the Zimbra proxy host as the zimbra user
zmprov -l gs `zmhostname` zimbraReverseProxyImapEnabledCapability
Check the global configuration
The multi-valued attribute zimbraReverseProxyImapEnabledCapability is inherited from the global configuration. For most installations, set IMAP capabilities in the global configuration so all Zimbra proxy nodes pickup the values.
zmprov -l gcf zimbraReverseProxyImapEnabledCapability
Set the global configuration to defaults
zmprov -l mcf zimbraReverseProxyImapEnabledCapability ACL zimbraReverseProxyImapEnabledCapability BINARY \ zimbraReverseProxyImapEnabledCapability CATENATE zimbraReverseProxyImapEnabledCapability CHILDREN \ zimbraReverseProxyImapEnabledCapability CONDSTORE zimbraReverseProxyImapEnabledCapability ENABLE \ zimbraReverseProxyImapEnabledCapability ESEARCH zimbraReverseProxyImapEnabledCapability ESORT \ zimbraReverseProxyImapEnabledCapability I18NLEVEL=1 zimbraReverseProxyImapEnabledCapability ID \ zimbraReverseProxyImapEnabledCapability IDLE zimbraReverseProxyImapEnabledCapability IMAP4rev1 \ zimbraReverseProxyImapEnabledCapability LIST-EXTENDED zimbraReverseProxyImapEnabledCapability LITERAL+ \ zimbraReverseProxyImapEnabledCapability MULTIAPPEND zimbraReverseProxyImapEnabledCapability NAMESPACE \ zimbraReverseProxyImapEnabledCapability QRESYNC zimbraReverseProxyImapEnabledCapability QUOTA \ zimbraReverseProxyImapEnabledCapability RIGHTS=ektx zimbraReverseProxyImapEnabledCapability SASL-IR \ zimbraReverseProxyImapEnabledCapability SEARCHRES zimbraReverseProxyImapEnabledCapability SORT \ zimbraReverseProxyImapEnabledCapability THREAD=ORDEREDSUBJECT zimbraReverseProxyImapEnabledCapability UIDPLUS \ zimbraReverseProxyImapEnabledCapability UNSELECT zimbraReverseProxyImapEnabledCapability WITHIN
Once the values are set, zmmtaconfig on each Zimbra proxy node will detect the changes and write the new configuration, then send a HUP signal to the Nginx proxy daemon. No restart is necessary.