User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.2b) Gecko/20021027 Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.2b) Gecko/20021027 I am using several mail filters to file mozilla's bugs into separate local folders. Today I realized that three bugs got files into the wrong folder. The filter log says that a different filter was applied than what I expected. The filter which was actually applied was the one immediately above the one that should've been. All filters have the form "sender is firstname.lastname@example.org and subject begins with [Bug xxxxxx]". I double-checked for typos but there are none. This one filter worked before (as did all others). I don't know what the rules.dat file should look like but its contents looks consistens. I have no idea how to reproduce the problem. Just in case it should matter: The rules are defined for the 8th out of 8 POP3 accounts in my mozilla profile. Reproducible: Didn't try Steps to Reproduce:
Using mozilla 2002-12-21-08. Occiasonally messages get filed into the wrong folder (as I reported some time ago). Can anyone give me a clue as to what information is needed to identify the bug?
WFM - 2003013108 This sounds a bit like the first half of bug 162971 where a third-party added an extra character to the from header making the filter fail. Reporter: Are you still seeing this? Could you check the actual headers of an email that is not being filtered (ctrl-u to view source) and check if that might be the case? If not, could you perhaps attach an email like that to this bug for testing purposes?
The bug is still present with version 2003-01-25-08. Comment #2 was sent to me by e-mail and got filed into the wrong folder. I will create 2 attachments - the mail sent to me, and my rules.dat file.
Created attachment 114413 [details] E-mail that was filed into wrong folder (Bug 118432 instead of Bug 179259) This is comment #2 for the current bug, as it arrived in my e-mail
The bug is still here in build 2003-04-11-08.
I located the problem. One of the first filters used 'match any' instead of 'match all.'
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.