• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue sending mails no longer possible SASL error

TobiasP

Regular Pleskian
since the plesk update to 18.0.34 yesterday a lot of clients can't send mails anymore, the syslog shows:

Mar 12 10:37:59 carbon postfix/smtpd[21268]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
Mar 12 10:37:59 carbon postfix/smtpd[21268]: warning: unknown[xxx]: SASL LOGIN authentication failed: generic failure
and also:
Mar 12 10:34:59 carbon postfix/smtpd[20459]: warning: SASL authentication failure: no secret in database
Mar 12 10:34:59 carbon postfix/smtpd[20459]: warning: unknown[xxx]: SASL CRAM-MD5 authentication failed: authentication failure

content of /etc/postfix/sasl/smtpd.conf:
pwcheck_method: auxprop saslauthd
auxprop_plugin: plesk
saslauthd_path: /private/plesk_saslauthd
mech_list: CRAM-MD5 PLAIN LOGIN
sql_engine: intentionally disabled
log_level: 4

on another plesk server of mine "service saslauthd status" outputs active but on this one it outputs:
Unit saslauthd.service could not be found.

the server is debian 9.13

I tried

plesk repair installation
plesk repair mail
/usr/local/psa/admin/sbin/mchk --with-spam

but problem still persists

EDIT:

I removed
compatibility_level = 2
from postfix main.cf and now it seems to be working again... but on the other servers where there was no issue this is still present...

are there any side effects to removing (and therefore setting it to =0)? is there anything else I should check? can this setting come back? is there anything else I should do to prevent this in the future?
kind regards
 
Last edited:
  • Like
Reactions: mow
Back
Top