325723 - Using Custom header to filter IMAP emails doesn't work

Status: RESOLVED DUPLICATE of bug 184490

(Thunderbird :: General, defect)

Description

[Stuart Halliday]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)
Build Identifier: 

I'm using TB version 1.5 (20051201) on a Win 2000 PC sp4 and also a Win XP Sp2 PC. 
This bug happens on both TBs. 
I read my email via IMAP. 

Our mail server adds the following header to class emails as Spam. 

X-Text-Classification: spam 
or 
X-Text-Classification: not_spam 

So I create a custom header and use the rule: 

(match any of the following) 
If Header 'X-Text-Classification' 'begins with' 'spam' then label it as Important. 

ie nice and red spam. 

But if I get a 'not_spam' header email then TB filter incorrectly marks it as Important. 

Filter log shows it as matched. 

Oh dear! 


If I alter the rule to 'is' then it also gets 'not_spam' header wrong and labels it as Important. 

This rule is also missing the following items in the drop down : 

Doesn't contain 
isn't 

So its either incomplete or very broken.

Reproducible: Always

Steps to Reproduce:
1. Make an email with the Header 'X-Text-Classification: not_spam'
2. Make a custom filter and use the header 'X-Text-Classification'
3. Now make a filter to match on this header using 'is' to find 'spam' and make it label the message so you can see by a colour change that its worked or not.
4. Run filter on the folder containing the test email.
5. The custom filter should not match but does.


Actual Results:  
filter detects 'not_spam' word in the actual email header as a match even when the filter is set to match exactly on the word 'spam'.

Expected Results:  
It should not match on the word 'not_spam' as the filter is set to match only if the word is 'spam'. ie the same.

This custom rule is also missing the following items in the drop down match menu: 

Doesn't contain 
isn't 

Other preset headers  allow these matching conditions.

IIRC there was an issue with filters where used in IMAP accounts. Perhaps this custom header was left out?

Comment 1

[zug_treno]

(In reply to comment #0)
> This rule is also missing the following items in the drop down : 
> 
> Doesn't contain 
> isn't 
 
Duplicate of bug 324326 -> Core bug 242550.

> 4. Run filter on the folder containing the test email.
> 5. The custom filter should not match but does.

Duplicate of/related to Core bug 294037 and Core bug 176283?