• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

CRAM-MD5 problems in plesk 12.0.18 #mu75

Linulex

Silver Pleskian
plesk 12.0.18 #mu75, centos 6.7 x64, all updates installed.

I have some problems with fail2ban blocking real users because cram-md5 isnt working.

/etc/courier-imap/imapd has the lines

IMAP_CAPABILITY="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5 AUTH=CRAM-SHA1 AUTH=CRAM-SHA256 AUTH=PLAIN IDLE"

IMAP_CAPABILITY_ORIG="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5 AUTH=CRAM-SHA1 AUTH=CRAM-SHA256 IDLE"

but the log is full

Feb 4 19:13:46 res9 courier-imapd: LOGIN FAILED, method=CRAM-MD5, ip=[::ffff:xx.xxx.xx.xxx]

Is this because cram-md5 must know the password and they are encrypted now or is there something i am missing?

regards
Jan
 
Back
Top