• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

port 587 issus after update

Michael Weber

New Pleskian
Dear members,

we have a problem with port 587, after the update we cannot send any mails on port 587, port 25 and 465 is working fine?

any Ideas

Best regards

Michael
 
Have you enabled option "Enable SMTP service on port 587 on all IP addresses" in MailServer Settings?
 
Yes i do, didn't help.

Solution was, uninstall Magicspam, Change Mailserver from postfix to qmail, after that it works again, but, 2 hours later we were on the spamcop blacklist because we forgot to Change the helo (/var/qmail/Control edit "me")

Regards

Michael
 
Same problem here. Last night's update hosed SMTP.
Please provide a fix ASAP.

Code:
READ Nov 24 08:46:19.644 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:mail.myserver.com -- port:587 -- socket:0x7f9a0ced1470 -- thread:0x7f9a0b8469a0
535 5.7.8 Error: authentication failed: authentication failure
 
Last edited:
Furthermore, webmail is not working on any of my customer sites. It defaults to a random web site on the server, NOT ioncube.
 
# /etc/init.d/saslauthd status
saslauthd (pid 21914) is running...


maillog reads...
Code:
...  SASL LOGIN authentication failed: authentication failure

Please help.
 
New detail, maillot is showing this...
Code:
warning: SASL authentication problem: unable to open Berkeley db /etc/sasldb2: No such file or directory

Could this be the cause? Did plesk forget the correct place of the correct db ?
 
FIXED!

Posting this in case someone down the line needs it.

Running auto installer via command line without any errors seems to have damage postfix config files.

Primarily it wiped out the /usr/lib64/sasl2/smtp.conf file to a vanilla SASL (not plesk) default.

I had to open and manual fix with this...
Code:
pwcheck_method: auxprop saslauthd
auxprop_plugin: plesk
saslauthd_path: /var/spool/postfix/private/plesk_saslauthd
mech_list: DIGEST-MD5 CRAM-MD5 PLAIN LOGIN
auto_transition: yes
sql_engine: intentionally disabled
log_level: 4
sasldb_path: /var/spool/postfix/plesk/passwd.db

Notice that I had to include the db path, that was "forgotten" during the auto install as well.

Hope this helps someone else down the road.
 
Back
Top