Hi community,
I am using Mailcow dockerized Version 2024-08a on a brand new setup on a dedicated server.
I have a strange problem with sieve filtering… although the goal should be very easy to achieve.
The objective is that ANY arriving eMail in one account test@test.com should be
To achieve that. I wrote an sieve script and applied it as admin in the Mailcow UI to the account “test@test.com” as a prefilter:
require ["fileinto", "mailbox", "variables", "envelope", "copy", "editheader", "subaddress"];
if header :matches "Subject" "*"{ set "subject" "${0}"; }
deleteheader "Subject";
addheader :last "Subject" "[ABC] ${subject}";
redirect :copy "a@test.com";
redirect :copy "b@test.com";
redirect :copy "c@test.com";
redirect :copy "d@test.com";
discard;
This works fine, but occasionally emails pass the filter and do not get touched / copied at all. Instead they become delivered to test@test.com inbox (which should always be clean and empty, if the filter would work all the time!)
I can see no reason, why the filter sometimes does not get applied. I cannot see any errors. To examine the problem a little bit further, I added a custom header within the global prefilter, to see, if the global prefilter is executed. This custom header is visible in any email, that the system receives, but also not in these emails where I have the prefilter activated (test@test.com) if this is ignored. When the siever prefilter on that account becomes applied, i can also see the custom header which is set in the global prefilter, which makes me assume, that sometimes any sieve filter configuration gets completely ignored.
The account receives about 200 eMails per day and around 5% do not pass the filter and I have no clue, why. Also I cannot reproduce the problem as sending the same test-eMails may pass or fail by coincidence.
If you have any hints for me, where to check or why this is happening, I´d be glad to hear from you (by the way… in an older version of mailcow this exact same setup worked without any problems… I do not remember the version unfortunately, by I am sure that there must have been some changes that lead to this problem in the latest versions)
regards,
yves