• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Issue After latest Plesk/Dovecot update, duplicate spam, sending, deleted items.

B1G-OS

New Pleskian
Server operating system version
Ubuntu 22.04.5 LTS
Plesk version and microupdate number
18.0.73_build1800251003.15
Hello everyone, I would like to remove the duplicate folders. Unfortunately, these folders are not being deleted. Now I have the following folders duplicated: Drafts, Spam, Deleted Items. How can I restore the order? See image. In addition, Roundcube uses the folders under the inbox, and Outlook, iOS, and Android use the other folders. What can I do?
 
The folders are in Roundcube and Outlook. I tried to delete the folders in the Roundcube settings. Unfortunately, these folders keep getting recreated. Folder_Problem_Dovecot_Plesk.jpg
 
Thanks for your feedback. Unfortunately, that has nothing to do with it. Even if Outlook is not running and you only log in via Roundcube, you cannot remove these folders. When I enter “inbox” in Outlook, the other folders I created myself are no longer displayed. Then I only see the subfolders of the “inbox” inbox. Where can I delete the duplicate folders? It's not possible in Roundcube, and it's not possible in Outlook either.
 
I found the change. How this change came about and who made it is now irrelevant to me. ;)

In the file: defaults.inc.php under /usr/share/psa-roundcube/config
The subfolders were created in the Roundcube settings and therefore could not be deleted.

The folders are listed from around line 920 onwards.
Before my change: INBOX.Sent, INBOX.Drafts, INBOX.Spam, INBOX.Trash.
After my change, I simply rewrote the folders with a slash (/) without INBOX “/Sent.”

Now the folder structure is back to how it was before the update. However, it should be noted that when you log back into Roundcube, you can set the fixed folder options under Settings. “Settings/Special Folders.”
 
I really feel like you're messing with me. Why are you changing users' personal settings?

What's the point of that?
# Plesk uses INBOX.Spam as hardcoded delivery folder
mailbox INBOX.Spam {
auto = create
special_use = \Junk
}
I can't change this setting because otherwise Sieve won't work anymore. Can you please fix this? And also set Sieve back so that there is only one spam folder and not an INBOX.Spam folder?
Neither my customers nor I want that.
 
In addition, you forgot the entry in “93-kolab-antispam.conf”:

sieve_global_extensions {
vnd.dovecot.pipe = yes
vnd.dovecot.execute = yes
}

Sieve did not filter the spam files correctly and displayed errors. I don't understand how this could have happened. I spent half the day searching for the errors, not to mention that personal folder settings can easily be changed. I have never had such serious problems with Plesk in more than 10 years. This should not happen.
 
@B1G-OS the 93-kolab-antispam.conf file belongs to Plesk Premium Email extension, do you have the Plesk Premium Email extension installed? If you do, then the following might not (completely) apply, as the extension tents to do things a bit differently compared to the default dovecot setup in Plesk.

Plesk uses a dot as a separator to be ensure compatibility with Courier. Changing the separator to a slash will cause issues, as you've already discovered. As a solution you can define the dot to be an alternative separator for compatibility in Dovecot. That way Plesk functionality will keep functioning. The Dovecot documentation describes how to configure Dovecot for use with a compatibility name: here: https://doc.dovecot.org/2.4.1/core/config/namespaces.html#backwards-compatibility-courier-imap

I am not sure if this works if you're using the Plesk Premium Email extension.
 
Last edited:
Hello Kaspar,
first of all, thank you for the information.

No, I have not installed or activated Plesk Premium Mail. Nevertheless, this file accessed the folder structure and changed the layout. I only tried it out in the past. The extension is deactivated. Especially with such a poor rating.

Initially, the mailboxes were: Sent, Drafts, Deleted, and Spam as subfolders. (After the first Dovecot update) Then I adjusted all the folders and restored the “normal” state.

Yesterday, I performed the next update via Plesk, and afterwards the spam folder was once again a subfolder of the inbox. I then tried to delete this folder, but it was automatically recreated, even though I had already customized the configuration in Roundcube and Dovecot.

After searching for the file that recreated this folder, I came across 93-kolab.conf and adjusted the folder again.

After that, the spam filter no longer worked. And then I came across the file: 93-kolab-antispam.conf. This file was missing the entries for the extensions that ensure that spam is moved to the spam folder. I also created a Python file that correctly describes a TXT file with logs so that the spam folder can learn correctly again.

This action simply went too far for me. Something like this should not be allowed to happen. That's why I will outsource the mail server in the long term or deactivate it in Plesk. The trust of my customers and myself is gone.

I have two more questions: Why does Dovecot.org create instructions for a backward installation when something new has been released? The second question is: Why doesn't Plesk intervene in the “new setting” and reject this change? It feels like taking my car to the garage for inspection and suddenly finding different seats installed when I pick it up.
 
you should delete any *kolab* config file you'll find in /etc/dovecot/conf.d/ !

These are old config files from the Plesk Premium Email extension that did not get cleaned up on deactivation/uninstallation of that extension. (do you have it only deactivated or really uninstalled? that is not 100% clear from the wording of your last email)
They are NOT present on any Plesk server that has never seen the Premium Email extension
 
I had only disabled this extension and had not activated a premium subscription. How can these files have such an impact on the standard mail server if it is disabled? Nevertheless, I have now found a solution that works very well. The mail server migration will take place soon.
 
Back
Top