• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

SMTP Problem: CRAM-MD5 auth suddenly not supported.

S

Spacey@

Guest
Hiyas!

I was running Suse 9.3 with latest Plesk 7.5 and everything was running well - "never touch..." :)

Suddenly strange messages appeard for me while trying to send an eMail: My mail.app client tells me: SMTP Server xxxxxx doesn't support CRAM-MD5 identification. I had this first only at work, could send at home. But few days later I couldn't send anymore from anywhere - really strange behaviour. On a second machine I couldn't send anymore as well (tested with several domains on it). So it's not a computer problem and not domain related. So I turned on pop before send and this works - but I want to re-enable the normal password auth again. Unfortunately I can't find anything in the logs - neither an error or even the try & fail to send!

So I thought it's time to update Plesk with the hope that the problem maybe solves itself while updating. So I went through every single update step: 8.0 - 8.0.1 - 8.1... and so on. Now I'm at 8.3 (8.4 already possible!) but the problem is still the same.

I guess it's somewhat of qmail thing. I googled of course a bit but no good results came up.

Like described: OS Suse 9.3 & Plesk 8.3

Anyone an idea here? :( :)
 
Back
Top