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?

After upgrading to Plesk 18.0.73 dovecot refuses to start. This is because Plesk upgraded dovecot to version 2.4.1-4 which uses a completely different configuration syntax to all previous versions of dovecot. This is fixed in Warden 5.04 released on Oct 12th/2025:

Administrators must first upgrade to Warden 5.04 using our new product updater under Warden -> Settings -> Panel Application -> Application update or using the command below:

plesk bin extension --install-url https://www.danami.com/clients/downloads/warden.zip

After upgrading to Plesk 18.0.73 and Warden 5.04 run the command below to upgrade the Warden dovecot configuration to the new format required for Plesk 18.0.73:

warden --task=antispam:learning:sieve --rebuild=yes --restart=yes

Now the issue should be fixed and dovecot should be running normally.

Upgrading to Warden 5.04 on an End-Of-Life OS

We understand that some users may be using an unsupported operating system that is end-of-life with Warden installed and may still need to upgrade to fix this issue (CentOS 7.x/CloudLinux 7.x/RedHat Enterprise Linux 7.x/Debian 10.x/Ubuntu 20.04). This can be done using the following commands:

// download the latest verion of Warden
wget https://www.danami.com/clients/downloads/warden.zip

// delete the pre-install check from the archive
zip -d warden.zip plib/scripts/pre-install.php

// install the extension
plesk bin extension --install warden.zip

// apply the dovecot fix
warden --task=antispam:learning:sieve --rebuild=yes --restart=yes

Just be aware that these end-of-life OS are no longer officially supported by us as they are no longer getting ClamAV signature updates. See here for more information.

 

  • dovecot, Plesk 18.0.73, 99-warden
  • 9 Utenti hanno trovato utile questa risposta
Hai trovato utile questa risposta?

Articoli Correlati

How can I fix the error: "milter-reject: END-OF-MESSAGE from..." in the log and found the AV in error (cannot read /etc/clam.d/scan.conf).

Cloudlinux / Imunify360 added their own version of ClamAV to their repo which accidentally...

How can I fix the error: Can't connect to TCP port 10024 on ::1 [Cannot assign requested address] when trying to start Amavis?

When trying to start Amavis you see this in the mail log: Oct 02 03:20:15 condor3648 systemd[1]:...

How can I fix the error: Error [Contentfilter_Settings_Contentfilter]. Message [[QUARANTINEDIR] must be a valid directory?

This error means that Amavis was not installed correctly. Try running the Warden from the command...

How can I fix the error: host 127.0.0.1[127.0.0.1] said: 552 5.3.4 Declared message size (1208029 B) exceeds size limit for recipient?

You can set the message size limit for Amavis under Settings -> Policy Settings -> Misc...

How can I fix the error: milter-reject: DATA 451 4.7.1 Service unavailable - try again later?

Reject log In the Warden reject log you see the message: Service unavailable - try again later....