Difference between revisions of "SMTP Auth Problems"

m (Reverted edit of Drwiii, changed back to last version by 84.189.16.170)
Line 1: Line 1:
SMTP Authentication allows POP3 and IMAP clients to send mail from [[zimbraMtaMyNetworks|arbitrary remote networks]]. If POP3 and IMAP clients are unable to send mail, check the auth settings and mail mode of the server:
+
==Checking and Configuring SMTP Authentication on the command-line==
  
Authentication also fails if you changed the port for the tomcat server, since the zimbraMtaAuthURL is not recreated when the port is changed. Solution is to force the recreation using the command in 3 below.
+
SMTP Authentication allows POP3 and IMAP clients to send mail from [[zimbraMtaMyNetworks|arbitrary remote networks]]. Authentication may fail if you change the zimbraMailMode server configuration attribute (with the [[CLI_zmtlsctl_to_set_Web_Server_Mode|'''zmtlsctl''']] command) or if you change the webmail access port server configuration attribute (zimbraMailPort or zimbraMailSSLPort) for the tomcat server, since the zimbraMtaAuthURL is not automatically recreated. The solution is to regenerate the zimbraMtaAuthURL with the command given in step 4 below.
 +
 
 +
If POP3 and IMAP clients are unable to send mail, check the auth settings and mail mode of the server:
  
 
<pre>
 
<pre>
Line 19: Line 21:
 
2. If '''zimbraMtaTlsAuthOnly''' is also TRUE, the POP3 and IMAP clients ''must'' be configured to use ssl/tls for smtp auth.
 
2. If '''zimbraMtaTlsAuthOnly''' is also TRUE, the POP3 and IMAP clients ''must'' be configured to use ssl/tls for smtp auth.
  
3. In a multi-node installation, make sure that '''zimbraMtaAuthHost''' and zimbraMtaAuthURL are set to a mailbox server. If not, the command "zmprov ms zimbra.domain.com zimbraMtaAuthHost mailbox.domain.com" will set them appropriately.
+
3. In a multi-node installation, make sure that '''zimbraMtaAuthHost''' and zimbraMtaAuthURL are set to a mailbox server. If not, the following command will set them appropriately.
 +
 
 +
<pre>zmprov ms zimbra.domain.com zimbraMtaAuthHost mailbox.domain.com</pre>
  
 
4. Make sure the url in the AuthURL will work with the MailMode. For example, if the AuthURL begins with "https://" (auth will be attempted over ssl) but the MailMode is "http" (tomcat is only listening on http), the authentication will fail.
 
4. Make sure the url in the AuthURL will work with the MailMode. For example, if the AuthURL begins with "https://" (auth will be attempted over ssl) but the MailMode is "http" (tomcat is only listening on http), the authentication will fail.
  
If the URL is wrong (in my case it was http:// rather than https://), simply re-set the hostname like this:
+
If the URL is wrong (in my case it was http:// rather than https:// ), simply re-set the hostname like this:
zmprov ms mail.mydomain.com zimbraMtaAuthHost mail.mydomain.com
 
----
 
Great advice!!! (Actually a life saviour)
 
----
 
You can use:
 
<pre>
 
$ zmprov gs <your.domain.net> | grep -i -e auth -e mode
 
</pre>
 
 
 
to get the info in one go.  I'm not sure about the "mixed" "Mode", it's
 
probably not so important (as long as it's either "mixed" or "https").
 
What's really magic here, is the
 
 
 
<pre>zmprov ms mail.mydomain.com zimbraMtaAuthHost mail.mydomain.com</pre>
 
  
command. It means, that you MUST _do_ it to get decent SMTP authentification
+
<pre>zmprov ms zimbra.domain.com zimbraMtaAuthHost zimbra.domain.com</pre>
but only _after_ you switched the HTTP interface to accept HTTPS.
 

Revision as of 03:18, 30 November 2006

Checking and Configuring SMTP Authentication on the command-line

SMTP Authentication allows POP3 and IMAP clients to send mail from arbitrary remote networks. Authentication may fail if you change the zimbraMailMode server configuration attribute (with the zmtlsctl command) or if you change the webmail access port server configuration attribute (zimbraMailPort or zimbraMailSSLPort) for the tomcat server, since the zimbraMtaAuthURL is not automatically recreated. The solution is to regenerate the zimbraMtaAuthURL with the command given in step 4 below.

If POP3 and IMAP clients are unable to send mail, check the auth settings and mail mode of the server:

$ su - zimbra
$ zmprov gs zimbra.domain.com | grep Auth
zimbraMtaAuthEnabled: TRUE
zimbraMtaAuthHost: zimbra.domain.com
zimbraMtaAuthURL: https://zimbra.domain.com:443/service/soap/
zimbraMtaTlsAuthOnly: TRUE

$ zmprov gs zimbra.domain.com | grep Mode
zimbraMailMode: mixed

1. In order to use smtp authentication, zimbraMtaAuthEnabled must be set to TRUE

2. If zimbraMtaTlsAuthOnly is also TRUE, the POP3 and IMAP clients must be configured to use ssl/tls for smtp auth.

3. In a multi-node installation, make sure that zimbraMtaAuthHost and zimbraMtaAuthURL are set to a mailbox server. If not, the following command will set them appropriately.

zmprov ms zimbra.domain.com zimbraMtaAuthHost mailbox.domain.com

4. Make sure the url in the AuthURL will work with the MailMode. For example, if the AuthURL begins with "https://" (auth will be attempted over ssl) but the MailMode is "http" (tomcat is only listening on http), the authentication will fail.

If the URL is wrong (in my case it was http:// rather than https:// ), simply re-set the hostname like this:

zmprov ms zimbra.domain.com zimbraMtaAuthHost zimbra.domain.com
Jump to: navigation, search