On Tue Mar 05, 2002 at 02:56:19AM -0800, David Guntner wrote:
> > Hmmm... well, you can try what I had in my postfix main.cf file for
> > testing.. and I used cram and digest passwords using Evolution as the
> > test client.
> >
> > # Other configurable parameters.
> > smtpd_sasl_auth_enable = yes
> > smtpd_sasl_local_domain = $myhostname
> > smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated,
>check_relay_domains
> > smtpd_sasl_security_options = noanonymous
> > smtp_sasl_auth_enable = yes
> >
> > I think you might be missing a few things like the
> > smtpd_sasl_local_domain... that sounds like it might be important to
> > it working.
> >
> > However, keep in mind that I had a very quick crash-course on SASL not
> > too long ago and still know maybe 2% of what I would need if I were to
> > actually configure it seriously... =)
>
> Thanks. I tried that, but it still didn't help. When connecting to port
> 25 after doing a postfix reload (after putting that stuff back into the
> main.cf file), I still get in the log:
>
> fatal: SASL per-process initialization failed
> warning: process /usr/lib/postfix/smtpd pid {pid #} exit status 1
> warning: /usr/lib/postfix/smtpd bad command startup -- throttling
>
> Any other ideas?You're quick going out of my experience with SASL. =) Ummm... is saslauthd running? You may need the daemon to be running. If it is running, then I really don't know what the problem is. =( It worked great here when I tested 8.0, 8.0/ppc, and 8.1 using the commands I outlined before. -- MandrakeSoft Security; http://www.mandrakesecure.net/ "lynx -source http://www.freezer-burn.org/bios/vdanen.gpg | gpg --import" 1024D/FE6F2AFD 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD Current Linux kernel 2.4.8-34.1mdk uptime: 42 days 17 hours 41 minutes.
msg50593/pgp00000.pgp
Description: PGP signature
