The following comments can be helpful in troubleshooting any SASL problems that arise.
sasl_method=LOGIN, sasl_username=sasluser
sasl_method=DIGEST-MD5, sasl_username=sasluser
Reason: ZixGateway SASL outbound is turned on but Exchange SASL is off.
Reason: Exchange 5.5 has SASL turned on but ZixGateway has SASL inbound turned off. This is bouncing off the ZixGateway.
Reason: Exchange 5.5 has SASL turned on but ZixGateway has SASL outbound turned off. This is bouncing off the outbound relay (where ZixGateway is sending mail and that requires SASL).
Reason: The current ZixGateway host name does not match the host name at the time SASL was configured.
Reason: The current ZixGateway host name does not match the host name at the time SASL was configured.
Reason: The SASL user password entered into sasl_passwd on the ZixGateway does not match the SASL user password entered into the MS Exchange security SASL/AUTH Account.
Reason: The SASL user defined in the MS Exchange Security SASL/AUTH Account is not a valid MS Exchange user.
To verify ZixGateway is responding properly for inbound mail, use telnet.
Enter telnet <IP of the ZixGateway> 25 and press Enter.
Enter “ehlo –a" and press Enter.
The following is a sample valid response. If the 250-AUTH line displays, the ZixGateway is correctly set up.
[root@mx2 tmp]# telnet 192.168.142.999 25
Trying 192.168.142.999...\
Connected to 192.168.142.999.
Escape character is ‘^]’.
220 mx2.vpmx.zixtest.com ESMTP
ehlo –a
250-mx2.vpmx.zixtest.com
250-PIPELINING
250-SIZE 52428800
250-ETRN
250-AUTH PLAIN LOGIN DIGEST-MD5 CRAM-MD5
250-XVERP
250 8BITMIME