• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

SASL authentication failure

Erwan

Regular Pleskian
Hello,

Since 3 weeks, some customers can't retrieve their messages (Outlook / POP3) for one or two hours (
the window asking the user name and password is displayed)... and and then everything returns to normal use.
All is ok with server (Plesk 12.5 / Postfix). The only thing we see in the maillog file is :

Mar 2 13:36:06 servXX postfix/smtpd[9690]: connect from unknown[x.x.x.x]
Mar 2 13:36:06 servXX postfix/smtpd[9690]: warning: SASL authentication failure: realm changed: authentication aborted
Mar 2 13:36:06 servXX postfix/smtpd[9690]: warning: unknown[x.x.x.x]: SASL DIGEST-MD5 authentication failed: authentication failure


I do not see where the problem is and why it is happening now (since Plesk update ?).

Thank you for your help.
 
I'm glad I'm not the only one! I switched to Postfix a week or so ago as all emails sent via Qmail were being blocked by Gmail.

Every other day I get hundreds of complaints from customers that their password prompt keeps popping up in Outlook, I check the logs and get

Mar 2 12:45:15 mail postfix/smtpd[859]: warning: SASL authentication failure: realm changed: authentication aborted
Mar 2 12:45:15 mail postfix/smtpd[859]: warning: unknown[41.58.154.197]: SASL DIGEST-MD5 authentication failed: authentication failure

If I restart postfix it normally fixes it for a while but not before I end up with an inbox full of complaints!

I've got over 3000 live email accounts on this server and this is getting ridiculous and is costing us time and money!
 
Hello,

I've made that:
Backup the file smtpd.conf, and replace there a string <mech_list: DIGEST-MD5 CRAM-MD5 PLAIN LOGIN> to <mech_list: CRAM-MD5 PLAIN LOGIN>.

I wait to see if that solves the problem....
 
Back
Top