>[оверквотинг удален]
>7.8.39.148]: cWF6eHN3
>Apr 21 15:14:29 vps274 postfix/smtpd[11101]: xsasl_cyrus_server_next: decoded re
>sponse: 12345
>Apr 21 15:14:30 vps274 postfix/smtpd[11101]: warning: 148-39.8-67.tampabay.res.r
>r.com[67.8.39.148]: SASL LOGIN authentication failed: authentication failure
>Apr 21 15:14:30 vps274 postfix/smtpd[11101]: > 148-39.8-67.tampabay.res.rr.com[6
>7.8.39.148]: 535 5.7.8 Error: authentication failed: authentication failure
>Apr 21 15:14:30 vps274 postfix/smtpd[11101]: < 148-39.8-67.tampabay.res.rr.com[6
>7.8.39.148]: QUIT
>..... Есть еще способ через параметр debug_peer_list. Там в логи идет очень подробный вывод.
В каком виде хранятся пароли в mysql?
Попробуйте еще протестировать как описано в
Testing SASL authentication in the Postfix SMTP server
To test the server side, connect (for example, with telnet) to the Postfix SMTP server port and you should be able to have a conversation as shown below. Information sent by the client (that is, you) is shown in bold font.
$ telnet server.example.com 25
. . .
220 server.example.com ESMTP Postfix
EHLO client.example.com
250-server.example.com
250-PIPELINING
250-SIZE 10240000
250-ETRN
250-AUTH DIGEST-MD5 PLAIN CRAM-MD5
250 8BITMIME
AUTH PLAIN AHRlc3QAdGVzdHBhc3M=
235 Authentication successful
Instead of AHRlc3QAdGVzdHBhc3M=, specify the base64 encoded form of \0username\0password (the \0 is a null byte). The example above is for a user named `test' with password `testpass'.
In order to generate base64 encoded authentication information you can use one of the following commands:
% printf '\0username\0password' | mmencode
% perl -MMIME::Base64 -e \
'print encode_base64("\0username\0password");'
The mmencode command is part of the metamail software. MIME::Base64 is available from http://www.cpan.org/.
Caution: when posting logs of the SASL negotiations to public lists, please keep in mind that username/password information is trivial to recover from the base64-encoded form.