User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52) Gecko/20070309 Firefox/184.108.40.206 Build Identifier: Version 3.0a1 (20070414) (ALSO TESTED ON TB2 Release Candidate 1 - version 220.127.116.11 (20070326)) Filters will not automatically pply tags to new mail when the "allow antivirus clients to quarantine individual messages" option is enabled in Privacy/Antivirus (though manually running same filter does apply tag). This is discussed in other tangents of other bug report threads, but none clearly describe the problem or point out the antivirus client option interaction. Anyone should feel free to merge or cross-reference. Reproducible: Always Steps to Reproduce: 1. Create filter that applies "Important" tag to all mail from email@example.com. 2. Enable "allow antivirus clients to quarantine individual messages" option. 3. Send mail to account from firstname.lastname@example.org. Actual Results: Filter fails to automatically apply "Important" tag to new mail from email@example.com. (Note, however, that manually running the same filter after mail arrived does apply tag). Expected Results: Filter should apply "Important" tag to new mail from firstname.lastname@example.org. Tested on TB2 RC1 and tonight's nightly build.
confirming, not because I've reproduced it, but because it's quite plausible.
Assignee: mscott → bienvenu
Status: UNCONFIRMED → NEW
Ever confirmed: true
Also reproduced that. Version 18.104.22.168 (20070326)
Also reproduced that too. Version 22.214.171.124 (20070326)
Reproduced that too. The bug is connected with the "allow antivirus clients to quarantine individual messages" option. Version 126.96.36.199 (20070309)
I forgot to add a precision : - the filter is applied on another in the inbox (instead of being applied on the mail on which the filter was launched).
Reproduced. Version 1.8.20070.32620
I can confirm, at least, that the sensitivity to the "allow antivirus clients" preference also occurs in https://bugzilla.mozilla.org/show_bug.cgi?id=355537. This should be tested as a possible dupe of Bug#355537.
please try tomorrow's 2.0 nightly branch build - it should be fixed in that build. resolving as dup
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 355537
You need to log in before you can comment on or make changes to this bug.