Resolved Plesk Obsidian 18.0.73 Dovecot failed to start after install

[Sebahat.hadzhi]

Hi, @LRLD . I double-checked with our team and DIGEST-MD5 and CRAM-MD5 were intentionally removed, because they are considered weak in Dovecot 2.4 and cause issues with encrypted passwords and some email clients (e.g. Android-based - try to authenticate with DIGEST-MD5, fails, and results in Fail2Ban bans). The plan is to bring back CRAM-MD5 by default in Plesk Obsidian 18.0.73 upt. 2. Later on they will create a way for users to manage auth schemes and disable them without Plesk overriding the changes.

 

[growmedia]

In my case commeting out the ciphers-line worked as well - but as a side-effect the "monitoring" feature stopped working by commenting it out... is that possible or just a coincidence?


And as people mentioned before - when using warden-antispam you have another headache here:

How can I fix the error: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/99-warden.conf line 9: Unknown section name: plugin after upgrading to Plesk 18.0.73? - Knowledgebase - Danami

Thank you! It works for me!

 

[NITROFOX]

I see this topic now, I create this topic for my problem Issue - Help 18.0.73 - 1 - Dovecot failed - 4.4.1 deferred mails

After edit "ssl_prefer_server_ciphers=yes" to "#ssl_prefer_server_ciphers=yes", Dovecot start, but emails not working.

I see various emails deferred in plesk panel domains, example:

4.4.1 deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)

Details​

<[email protected]>: connect to 127.0.0.1[127.0.0.1]:10024: Connection refusedrecipient=[email protected]=2049dsn_orig_rcpt=rfc822;[email protected]=4.4.1action=delayedreason=connect to 127.0.0.1[127.0.0.1]:10024: Connection refused

Various mails error: 4.4.1 deferred (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)