severity 402103 important tags 402103 + moreinfo thanks On Thu, 2006-12-07 at 23:52 -0500, andrew wrote: > I seem to miss the solution. It's December 7, i get a sasl2-bin update a > postfix update and the mailserver is done. First i get: [...] > To resolve the problem I had to revert back to 2.1.19.dfsg1-0.5. > > How is it postfix that is broken, Woudn't it be broken if I revert back?
"Broken" is a pretty loose term. Sorry if I've used it in a confusing
manner. The precise meaning that I've intended to convey is that the fix
needed to happen in the postfix package, when referring to the issue
that the newer Cyrus SASL has a different method of setting the plugin
configuration path. Postfix used the old method, which didn't work with
the new Cyrus SASL. Thus, Postfix needed to be altered to use the new
method, which is what bug #398534 was ultimately about. Now that Postfix
has been altered in this way, that bug has been closed.
Anyway, yours might be a different problem. Let's see if we can work out
what it is and how to fix it. Please check the following:
* saslauthd is running
* the saslauth socket is in /var/spool/postfix/var/run/saslauthd
(-m set in OPTIONS in /etc/default/saslauthd)
* dpkg-statoverride --list /var/spool/postfix/var/run/saslauthd
returns something like:
* root sasl 710 /var/spool/postfix/var/run/saslauthd
* postfix main.cf has
* smtpd_sasl_auth_enable = yes , and
* smtpd_recipient_restrictions = permit_mynetworks,
permit_sasl_authenticated, ... (whatever you need here)
* postfix SASL configuration is in /etc/postfix/sasl/smtpd.conf
and includes something like
* pwcheck_method: saslauthd
* you have at least version 2.1.22.dfsg1-6 of cyrus-sasl2
* you have at least version 2.3.4-3 of postfix
You may find the following useful:
* /usr/share/doc/sasl2-bin/README.Debian
* http://www.postfix.org/SASL_README.html
The former is useful only in the mentioned version of cyrus-sasl2.
For the latter, please note that the Debian version of Postfix doesn't
use directories like /usr/local/... and that smtpd.conf goes
in /etc/postfix/sasl, and not any other directory. Otherwise that
document covers the Postfix side quite well.
Please let us know how this goes, and what was the exact cause of this
error. If you need assistance, don't hesitate to ask for help. Please be
as specific as you can.
Thanks,
--
Fabian Fagerholm <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
