Difference between revisions of "SMTP Auth Problems"

m
m (Reverted edit of Drwiii, changed back to last version by 84.189.16.170)
Line 41: Line 41:
 
command.  It means, that you MUST _do_ it to get decent SMTP authentification
 
command.  It means, that you MUST _do_ it to get decent SMTP authentification
 
but only _after_ you switched the HTTP interface to accept HTTPS.
 
but only _after_ you switched the HTTP interface to accept HTTPS.
 
 
 
[http://www.gambling-online-theory.com/online-casino/bet-online-casino.html bet online casino]
 
[http://www.casinos-new.com/blackjack.html Online casino - Blackjack online]
 
[http://www.gambling-online-theory.com/online-casino/bet-online-casino.html bet online casino]
 
[http://www.magical-casino.com/games_variations.html Casino Games and variations.]
 
[http://www.casinos-new.com/blackjack.html Online casino - Blackjack online]
 
[http://www.slots-wiki.com/index.php/online_slots online slots]
 
[http://www.slots-wiki.com/index.php/slots_tips slots tips]
 
[http://www.magical-casino.com/no_deposit.html Casinos with no deposit required.]
 
[http://www.gambling-online-theory.com/online-casino/bet-online-casino.html bet online casino]
 
[http://www.slots-wiki.com/index.php/slots_online slots online]
 

Revision as of 05:19, 18 November 2006

SMTP Authentication allows POP3 and IMAP clients to send mail from arbitrary remote networks. If POP3 and IMAP clients are unable to send mail, check the auth settings and mail mode of the server:

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.

$ 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 command "zmprov ms zimbra.domain.com zimbraMtaAuthHost mailbox.domain.com" will set them appropriately.

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 mail.mydomain.com zimbraMtaAuthHost mail.mydomain.com


Great advice!!! (Actually a life saviour)


You can use:

$ zmprov gs <your.domain.net> | grep -i -e auth -e mode

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

zmprov ms mail.mydomain.com zimbraMtaAuthHost mail.mydomain.com

command. It means, that you MUST _do_ it to get decent SMTP authentification but only _after_ you switched the HTTP interface to accept HTTPS.

Jump to: navigation, search