Error, Informative, News, Technology

Dovecot IMAP Doesn’t Work After Upgrade to Plesk 17.8 [FIXED]

Here we are going to provide the workaround to resolve the error that commonly appears while upgrading to Plesk 17.8. Let’s get into it.

What is “Dovecot Doesn’t Work After Plesk Update” Error?

Many users find issues in receiving or reading mail after the upgrade to Plesk 17.8. And after reading logs /var /log /maillog, the following message appears.

Cause of Plesk Error

The reason behind this error is, the latest Dovecot packages comprises of ProtectSystem=Full systemd directive in the /usr/lib/systemd/dovecot.service file. This file further blocks Dovecot from writing into a non-default directory. Due to which the mail data starts store on a different location instead of the default location.

Workaround to Fix – Dovecot IMAP Doesn’t Work After Plesk 17.8 Update Error

First of all, you can try the mount point for mail storage instead of /home. Else go with the described steps to get rid of this error.

1. Time to connect to the server through SSH.


2. Now make a service.conf file at /etc/systemd/system/dovecot.d and include the following mentioned lines to it.
   
   [Service]
ProtectHome=false


3. Afterward, you need comment the following line in the /usr/lib/systemd/system/dovecot.service file.
   
   #ProtectSystem=full
   
   Note:- It might be possible that updating or reinstalling dovecot package revert modifications made in /usr/lib/systemd/system/dovecot.service file


4. Time to reload daemon.
   
   #systemctl daemon-reload


5. At last, restart Dovecot.
   
   #systemctl restart dovecot

That’s all about how to fix “Dovecot does not work after upgrade to Plesk 17.8” error.

Hope! The workaround works for you.