Vincent Danen grabbed a keyboard and wrote:
>
> On Tue Mar 05, 2002 at 02:56:19AM -0800, David Guntner wrote:
> >
> > 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.
Yea, the daemon is running. It wasn't the first time I started it up, but
then I noticed the daemon. Started it up and then tried to connect again.
No help there; still got the error. Maybe you can run this past the local
SASL guru there? :-)
I just wish I knew why the blasted thing keeps aborting when I try to turn
it on. I only seem to get that error when the smtpd_sasl_auth_enable = yes
line is uncommented. I can have the other sasl lines uncommented, and it
doesn't even seem to notice them. But without the enable line, nothing
happens. And for some reason, whatever it's trying to start keeps bombing
off.
Well, thanks for trying; I do appreciate it. If you happen to think of
anything else, please feel free to pass it on to me. :-)
--Dave
--
David Guntner GEnie: Just say NO!
http://www.akaMail.com/pgpkey/davidg or key server
for PGP Public key
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
