• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue SpamAssassin is trying to deliver SPAM msg to INBOX.Spam instead .Spam

ProDC

New Pleskian
Hi,

I have default imap (dovecot) configuration, but SpamAssassin is trying to deliver SPAM msg to INBOX.Spam with error:

save failed to open mailbox INBOX.Spam: Mailbox doesn't exist: INBOX.Spam

Default Spam folder is .Spam and I would like to deliver SPAM msg to this folder. How can I fix this issue?

BR.
 
I think that you have nothing in the output of the command:

# doveadm mailbox list -u [email protected] | grep -i Spam

Try to create a missing folder with the command:

# doveadm mailbox create -u [email protected] INBOX.Spam

and check results after that.
 
Ok, is it possible to change this to .Spam which is default for example for Roundcube and others email client?
 
I can't understand the problem. On my personal Plesk mailbox I see

# doveadm mailbox list -u [email protected] | grep -i Spam
INBOX.Spam

And in all mail clients and in Roundcube I see Spam folder in the root but not in INBOX. What is wrong here?
 
That's the problem. By default I have in doveadm:

# doveadm mailbox list -u me@domain.com | grep -i Spam
Spam

(not INBOX.Spam, I didn't change this setting.) and in all mail clients and in Roundcube I see Spam folder in the root but not in INBOX also.
But SpamAssassin is trying to deliver SPAM msg to INBOX.Spam.
I think that these settings should be the same.

In this issue the best way is to change default Spam folder for delivering msg by SA, isn't it?

PS. I have Ubuntu.
 
I can only recommend creating a request to support team to do the in-depth investigation to find the reason and to fix it. Please create a ticket to Plesk support.
 
Back
Top