Bryan
2004-05-11 03:10:20 UTC
Postfix can provide vvvvverbose debugging if necessary... no doubt, this is
much appreciated.
When the problem is inside SASL, I can't seem to get much information.
I've set up a second server to be nearly identical to one that is already
running fine, but I continue to have trouble with outgoing SMTP auth from
this new machine.
Short of differing the drives (yea, right), this seems to be the best I can
get knowing that all config files look fine:
May 10 19:38:12 rabbit postfix/smtpd[18213]: warning: SASL authentication
failure: Password verification failed
May 10 19:38:12 rabbit postfix/smtpd[18213]: warning: SASL PLAIN
authentication failed
May 10 19:38:12 rabbit postfix/smtpd[18213]: 535 Error: authentication
failed
The client (kmail) simply complains about lack of support for PLAIN, which
might not be accurate.
---> How can I get more debugging detail from the SASL SMTP process, either
inside postfix, or cyrus short of using tools like strace?
- postfix-2.2-20040504
- cyrus-sasl-2.1.18
- mysql-4.0.18
Thanks,
Bryan
much appreciated.
When the problem is inside SASL, I can't seem to get much information.
I've set up a second server to be nearly identical to one that is already
running fine, but I continue to have trouble with outgoing SMTP auth from
this new machine.
Short of differing the drives (yea, right), this seems to be the best I can
get knowing that all config files look fine:
May 10 19:38:12 rabbit postfix/smtpd[18213]: warning: SASL authentication
failure: Password verification failed
May 10 19:38:12 rabbit postfix/smtpd[18213]: warning: SASL PLAIN
authentication failed
May 10 19:38:12 rabbit postfix/smtpd[18213]: 535 Error: authentication
failed
The client (kmail) simply complains about lack of support for PLAIN, which
might not be accurate.
---> How can I get more debugging detail from the SASL SMTP process, either
inside postfix, or cyrus short of using tools like strace?
- postfix-2.2-20040504
- cyrus-sasl-2.1.18
- mysql-4.0.18
Thanks,
Bryan