Robert Krig:
> On Wednesday 11 January 2012 07:14:14 Wietse Venema wrote:
>
> > Why do you believe that there is a problem with SASL authentication
> > between the PHP application and Postfix?
>
> Because the only error that shows up in the log file is this:
> ##########################################
> postfix/smtpd[7310]: connect from www2.domain.com[xx.xx.xx.xx]
>
> postfix/smtpd[7310]: warning: www2.domain.com[xx.xx.xx.xx]: SASL LOGIN
> authentication failed: authentication failure
Fortunately, the Postfix SMTP server is a short-lived process that
runs for a few minutes at a time without ever changing the system
configuration. Every new Postfix SMTP server process is like a
new-born with a blank memory of its past.
Therefore, if SASL logins fail, especially when they fail persistently,
then either the SASL client has changed, or the SASL server
infrastructure **outside POSTFIX** has changed.
This would be a good time to provide configuration information about
how Postfix interfaces to the SASL server infrastructure **outside
POSTFIX**.
There are two such possible infrastructures: Dovecot or Cyrus SASL.
This choice is made with the smtpd_sasl_type parameter.
Examine the output from:
# postconf smtpd_sasl_type
If this is "dovecot", you need to check the Dovecot authentication
server logs.
If this is "cyrus", you need to report what's in the smtpd.conf
file, whose location depends on how your distributor has tweaked
the details of the SASL server infrastructure **outside POSTFIX**.
This file could be located in /usr/local/lib/sasl2, in /etc/postfix,
or any number of other places.
I suggest doing:
# find / -name smtpd.conf
and reporting the contents of any files thus found.
Wietse
