* Crazedfred <crazedf...@yahoo.com>: > > If you use the pass above, change it now that you have sent it to public. > > I am substituting in fake accounts and passwords to show what's going on, > these do not match what I am actually using :) > > > Where did you put smtpd.conf? On Debian it should be in > > /etc/postfix/sasl/smtpd.conf. > > On my system that file did not exist (the sasl directory is emtpy), it was > located at /usr/lib/sasl2/smtpd.conf > The only lines are the ones I put there: > > pwcheck_method: saslauthd > mech_list: login plain
If you run Postfix from Debian packages, you need to locate smtpd.conf at /usr/lib/sasl2/smtpd.conf. You also need to add the postfix user to the sasl group: % adduser postfix sasl > > Do you run Postfix smtpd chrooted? > > Not to my knowledge; I am running a pretty default install. Then it very likely is chrooted. > How could I confirm that? 1. Check the chroot column for the smtp service in master.cf 2. Run saslfinger. It will generate a report useful for debugging Cyrus SASL on this list. If it runs chrooted and if you want to stick with that you need to change the location where saslauthd puts the socket. On Debian you edit OPTIONS at the bottom of /etc/default/saslauthd: OPTIONS="-c -m /var/spool/postfix/var/run/saslauthd" Then restart saslauthd using the init-script. It will create all necessary paths and set all permissions to establish the socket in /var/spool/postfix/var/run/saslauthd. p@rick -- All technical questions asked privately will be automatically answered on the list and archived for public access unless privacy is explicitely required and justified. saslfinger (debugging SMTP AUTH): <http://postfix.state-of-mind.de/patrick.koetter/saslfinger/>