Experience with postfix SASL not good

[Shawn McMahon]

Before filing a bug report (because there's one already that says this
is fixed, but it doesn't look fixed to me), I wanted to see if anybody
else is seeing this same behavior.

I installed postfix on a new system yesterday, and wanted to set up
SASL to use PAM for authentication.

By the time I was done, I had to edit three lines in
/etc/init.d/saslauthd, and one in /etc/default/saslauthd.  I had to
consult a lot of documentation on other sites, as I couldn't quickly
find the right docs on ubuntu.com; in fact, even installing saslauthd
was a kludge because I couldn't get things to work easily without it as
"pwcheck" isn't included, and I was trying to avoid writing scripts as a
test of getting things to work in ways "Joe Average" could replicate.

Also, although /etc/postfix/sasl was created, no config file was created
in there; not even a stub with commented defaults.

The key problem was that postfix is installed chrooted (good), but
saslauthd was installed to put its mux and pid file outside that chroot
(bad).  There were other minor related problems.

Since our default install of saslauthd has MECHANISMS="pam" set, this
ought to work a little more easily than surgery on the init script.  I
realize that most people don't have any need for SMTP authentication,
but those people wouldn't be installing sasl.


Or did I miss something that would have solved this in 2 seconds, that
we can clarify in a doc?


-- 
   Shawn McMahon    | Ubuntu: an ancient African word meaning "I am sick
   EIV Consulting   | of compiling Gentoo".
 http://www.eiv.com |                       - Jeff Waugh (paraphrased)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/sounder/attachments/20060321/b0262af7/attachment-0001.pgp