On Wed Mar 06, 2002 at 01:57:06PM -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've forwarded it to two folks I think might be able to help. If I hear anything back from them, I'll forward it to the list. > 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, postfix probably ignores all of the sasl config commands if it's not enabled. I suspect if you had smtpd_sasl_auth_enable = no it would likewise work without errors. There's something with SASL itself, or a misconfiguration on the SASL components. One last thing. Can you tell me what the permissions of /var/lib/sasl/sasl.db are? If they aren't mode 644, can you chmod it and restart saslauthd and postfix and see if that helps? > 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. :-) Check the permissions... that's about all I can think of right now... -- 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 20 hours 38 minutes.
msg50597/pgp00000.pgp
Description: PGP signature
