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 released on Sept 30 dovecot refuses to start with the error:

Sep 30 08:34:40 el10p18.danami.com dovecot[25900]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/99-warden.conf line 10: Unknown section name: plugin

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.

To temporarily fix the issue edit the file /etc/dovecot/conf.d/99-warden.conf and replace it with the following:

If your spam action under Warden -> Content Filter Settings -> Policy Settings is set to "move" to spam folder (the default) then replace it with the following:

service imap {
  vsz_limit = 512MB
}

protocol imap {
    mail_plugins {
        imap_sieve = yes
    }
}

sieve_plugins {
    sieve_imapsieve   = yes
    sieve_extprograms = yes
}

sieve_global_extensions {
    vnd.dovecot.pipe = yes
}

sieve_pipe_bin_dir = /usr/local/bin/dovecot-sieve

sieve_script global-after {
    type = after
    path = /var/qmail/popuser/warden-server.sieve
}

If your spam action under Warden -> Content Filter Settings -> Policy Settings is set to "quarantine", "block", or "tag" then replace it with the following:

service imap {
  vsz_limit = 512MB
}

protocol imap {
    mail_plugins {
        imap_sieve = yes
    }
}

sieve_plugins {
    sieve_imapsieve   = yes
    sieve_extprograms = yes
}

sieve_global_extensions {
    vnd.dovecot.pipe = yes
}

sieve_pipe_bin_dir = /usr/local/bin/dovecot-sieve

Restart Dovecot

systemctl restart dovecot

Important: Do not change the server wide policy settings under Warden -> Content Filter Settings -> Policy Settings after applying the fix otherwise it will be reverted and dovecot will refuse to start again. This will be permanently fixed in Warden 5.03 which will be released in the next few days.

  • 18.0.73, dovecot, 99-warden.conf
  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

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....