12 comments

  1. Hi!, thanks for your info.
    This solution its for a single user?? it means, that i Need to add all user (emails) in the file: /opt/zimbra/conf/sasl_access ???

  2. Hi, it is possible to enter IP addresses in sasl_access ? Because i have a lot of sasl authentication failed messages on /var/log/mail.log like “postfix/submission/smtpd[25522]: warning: unknown[104.219.42.106]: SASL LOGIN authentication failed: authentication failure” but there is no email address, just the ip address…

    Thanks in advance!

  3. Hi ,

    I try this solution but all the legitimate users also reject from the server please advice

    Thanks Regards
    Namal Spencer

  4. Hi,

    I role back the settings. but you can see the log file

    Apr 24 10:47:09 mail saslauthd[18900]: auth_zimbra: hainis@domain.com auth OK
    Apr 24 10:47:10 mail postfix/submission/smtpd[34145]: NOQUEUE: filter: RCPT from unknown[192.168.1.18]: : Sender address triggers FILTER smtp-amavis:[127.0.0.1]:10026; from= to= proto=ESMTP helo=
    Apr 24 10:47:10 mail postfix/submission/smtpd[34145]: NOQUEUE: reject: RCPT from unknown[192.168.1.18]: 451 4.3.5 Server configuration error; from= to= proto=ESMTP helo=

    Server configuration error

    1. Hello,
      Server configuration error means your configuration is not properly. Please try to revert your configuration and make sure your Zimbra work properly. Then, you can try again.

  5. Thank you very much Iman,
    If I enable “Restrict SASL Login/Access” and someone try to authenticate with my user, Zimbra will authenticate first or Zimbra will prevent the authentication processes?

    Ps: We use SASL authentication with Active Directory and Password Policy.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.