View Issue Details
|Fixed in Version
|0001825: Vacation record is put as the first one in SIEVE script
When enabling vacation record, it is put as the first record in sieve script file for user. That means it prepends all other filters, including spam filter. That makes system answer absolutely all mail, including SPAM's. And only after that they are put into the spam folder. I'm not sure that it would be better to put it as the last record, but putting it before spam filter definitely makes me rewrite sieve script manually on the server.
|No tags attached.
Is there a temporary workaround for this? This is a big deal! I have filters for my lists and groups that process mail into folders and shouldn't be notified of vacation. Either change the default to make it process last or at least provide an option to choose where the rule is placed. Even if it is site wide.
I think this problem is even worse than what is being already told. We have the same problem in my lab.
With the vacation filter in first position, you can't even filter Spam beforehand. So we are answering vacation message to spammers. This is especially a problem since some of the Spam is sent by 'spamtraps' of blacklisting societies. Your mail system can end up being considered malconfigured by them, then blacklisted.
So, delivering Spam to user account (tagged or not) + using the SOGo vacation message can lead your mail system to be blacklisted.
The workaround I see right now would be to use the patch found in http://sogo.nu/bugs/view.php?id=1392 (and http://sogo.nu/bugs/view.php?id=1391 as a dependency). I didn't test it right now, but I will do soon and let you know.
Fixed in revision 84638520098e5b0e2cebc6efed95a3c49beac705.
|Note Added: 0004106
|Note Added: 0004166
|Note Added: 0004223
|new => resolved
|Fixed in Version
|open => fixed