17. FAQ

17.1. Postfix & SASL
Q: Postfix can't find SASL libraries
17.2. SASL & Mail Clients
Q: Troubles with MacOS X Mail and SASL
17.3. TLS
Q: 500 Unsupported command (Norton AntiVirus 2002)

17.1. Postfix & SASL

Q: Postfix can't find SASL libraries
Q:

Postfix can't find SASL libraries

A:

Some packagers, e.g. RedHat, deliver Postfix RPM in a chroot configuration. This will result in the fact that Postfix can't find the SASL libraries. Check /etc/postfix/master.cf if there are any daemons chrooted. Either copy the files needed into the chroot jail or take the daemons out of the jail.

# ==========================================================================
# service type  private unpriv  chroot  wakeup  maxproc command + args
#               (yes)   (yes)   (yes)   (never) (100)
# ==========================================================================
smtp      inet  n       -       n 1     -       -       smtpd
#smtps    inet  n       -       n 2     -       -       smtpd
1 2

If these entries are set to n the daemons do not run chrooted.

17.2. SASL & Mail Clients

Q: Troubles with MacOS X Mail and SASL
Q:

Troubles with MacOS X Mail and SASL

A:

I upgraded to MacOS 10.1.5 the other day, and now the MacOS X Mail program uses PLAIN auth successfully with Postfix. Previously, it attempted to do CRAM-MD5, got confused if that failed, then the PLAIN auth never worked. I no longer need to have the workaround of setting up a CRAM-MD5 password just for MacOS X Mail.Vivek Khera

17.3. TLS

Q: 500 Unsupported command (Norton AntiVirus 2002)
Q:

500 Unsupported command (Norton AntiVirus 2002)

A:

If you run Norton AntiVirus 2002 and try to innitiate a TLS session then Norton AntiVirus 2002 will block the STARTTLS command without any notice.