On 01/18/15 09:07, Edgar Pettijohn wrote: > >>> better make a bugreport at your distribution >>> https://www.google.at/search?q=postfix+debian+chroot+problems >> Assuming this is Debian, there's no bug report needed. It's an intentional >> maintainer choice and not a bug. >> >> Scott K >> > I think its default in a lot of distros. I know it is in openbsd and I'm > pretty sure freebsd also. > What would cause the "warning: SASL: Connect to /var/spool/postfix/private/auth failed: No such file or directory" to come back after working for a while? I had to restart dovecot and postfix, Is there any postfix debug tool like doveadm that I can run to test authentication?
- fatal: no SASL authentication mechanisms James Lockie
- Re: fatal: no SASL authentication mechanisms Viktor Dukhovni
- Re: fatal: no SASL authentication mechanisms James Lockie
- Re: fatal: no SASL authentication mechani... li...@rhsoft.net
- Re: fatal: no SASL authentication mec... Scott Kitterman
- Re: fatal: no SASL authenticatio... Viktor Dukhovni
- Re: fatal: no SASL authentic... li...@rhsoft.net
- Re: fatal: no SASL authenticatio... Edgar Pettijohn
- Re: fatal: no SASL authentic... James Lockie
- Re: fatal: no SASL authe... Patrick Ben Koetter
- Re: fatal: no SASL authe... Edgar Pettijohn
- Re: fatal: no SASL authe... James Lockie
- Re: fatal: no SASL authentic... Benny Pedersen
- Re: fatal: no SASL authentication mechani... Benny Pedersen