• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

SMTP Login Breaks After Every Plesk Update.

Greg Sevastos

New Pleskian
Hi,

Im having issues with qmail after every Plesk update. Everytime Plesk updates, SMTP login breaks.

From our mail log after Plesk micro-update #12 (on my mail account):
Aug 13 06:44:57 server cmd5checkpw: SMTP connect from xxx-xx-xx-xxx.perm.iinet.net.au [xxx.xx.xx.xxx]
Aug 13 06:44:57 server cmd5checkpw: SMTP user mail: auth FAILED from xxx-xx-xx-xxx.perm.iinet.net.au [xxx.xx.xx.xxx]

I have been running this command after every update which seems to fix the issue: /usr/local/psa/admin/sbin/mchk –with-spam

It seems to install libauthpsa which fixes the issue?
Aug 13 06:46:07 server courier-authdaemon: stopping authdaemond children
Aug 13 06:46:07 server courier-authdaemon: modules="authpsa ", daemons=5
Aug 13 06:46:07 server courier-authdaemon: Installing libauthpsa
Aug 13 06:46:07 server courier-authdaemon: Installation complete: authpsa

After running the above command (on my mail account):
Aug 13 06:47:58 server cmd5checkpw: SMTP connect from xxx-xx-xx-xxx.perm.iinet.net.au [xxx.xx.xx.xxx]
Aug 13 06:47:58 server cmd5checkpw: SMTP user mail: logged in from xxx-xx-xx-xxx.perm.iinet.net.au [xxx.xx.xx.xxx]

Can anyone shed some light on why Plesk breaks SMTP logins after every update?

Many thanks.
 
Code:
# restorecon /etc/resolv.conf
will temporary solve the problem (without server reboot) until MU with fix will be released.
 
Last edited:
Uiih,

nice to see it's a known problem. I had it various times and I planned to post this today.
:) With a quick fix it's fine until final release.

So if you need more information, let me know.

Thanks
 
Back
Top