159645 - Mail Filter deletes messages even no filtering criteria is fulfilled (search for string in msg body)

Status: RESOLVED DUPLICATE of bug 136055

(MailNews Core :: Filters, defect)

Description

[Croco Dil]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; de-AT; rv:1.1b) Gecko/20020721
BuildID:    2002072104

I have several mail filters most of them search the body for multiple phrases 
and delete msg where those are found.
now some of may mails (about 30%)are being moved into trash but they don'T fit
to any of the cretria the filters look for not even close.

Reproducible: Always
Steps to Reproduce:
1.set up a filter "serach body for..." and delte it when found

2.watch your incoming mails
3.some of them get deleted but do not match to the filtering rule

Actual Results:  Mails get into trash that shouldn't go there

Expected Results:  only delte these mails that match the filter

Comment 1

[laurel]

Please attach one of the messages you believe was deleted in error and also a
copy of your rules.dat

Comment 2

[Croco Dil]

Attachment: Rules.dat filter file

Comment 3

[Croco Dil]

Attachment: mail that got deleted without matching a filter rule

there was a word file attached named "choclates_.doc"

thats the latest example but I have a some more

Comment 4

[R.K.Aa.]

Did all the unexpectedly deleted mails contain attachments?

If anything in a base64 encoded attachment match a filter rule to delete - it
will get deleted. Previously reported in bug 153973 and bug 136055.
Similar: bug 98141.

I wonder if that is what happens in this case as well.

Comment 5

[Croco Dil]

Seems to be, but I'll check the unexpectedly deleted mails
I changed my filter rules and we will see if this continues.
but looks quite like a dupe 

Comment 6

[Sander]

Reporter: did you indeed check your deleted emails to see if they all contained
attachments so this can thus be marked a dupe?

Comment 7

[Croco Dil]

Yes all the deleted mails containde attachments so it is indeed a dupe

Comment 8

[Sander]

okay, thank you.
(For the record, the sample message provided here contained the string "XXx"
which was caught by the case-insensitive filter rule for "XXX" in the body.)

*** This bug has been marked as a duplicate of 136055 ***