369460 - Filter List-Id is <list.domain.tld> does not work

Status: RESOLVED DUPLICATE of bug 184490

(Thunderbird :: General, defect)

Description

[Sebastian Mendel]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Build Identifier: Version 2 beta 2 (20070202)

if i add an filter List-Id is <list.domain.tld> does not work

Reproducible: Always

Steps to Reproduce:
1. have an email with headerline: List-Id: <list.domain.tld>
2. add Filter -> add Header 'List-Id' -> set 'is' <list.domain.tld>
3. save and run filter
Actual Results:  
nothing happens

Expected Results:  
executing the filter rules (moving email)

Comment 1

[Sebastian Mendel]

forgot:

- no addons
- clean install
- all older existent files/folders deleted before clean install
- account is an IMAP account with SSL
- filter rule is to move the email on another IMAP folder on same account
- tried with different emails from different mailinglists

Comment 2

[Sebastian Mendel]

correction - filter works on new emails reaching mailbox after filter was created - but i cannot apply filter on already existent mails in mailbox

or if there is already a filter applied the next will not be applied - i have a filter marking my own messages on mailinglist as read and assigning them keywords - this emails (even new) will not be moved

Comment 3

[Magnus Melin [:mkmelin]]

This sounds like bug 184490. The behaviour has has regressed, but it seems it never worked completely.

Comment 4

[Scott MacGregor]

I don't think we're going to get to this in time for tb2.

Comment 5

[Sebastian Mendel]

comment #3 about bug #184490: yes seems to be related, custom filters do only apply to new incoming messages - but not messages already existing in folder

comment #4: i do not know the internals of TB - but is it really such a big step to change the custom - filter to behave like the built in filter to apply to ALL messages - not only new?

Comment 6

[Magnus Melin [:mkmelin]]

(In reply to comment #5)
> comment #4: i do not know the internals of TB - but is it really such a big
> step to change the custom - filter to behave like the built in filter to apply
> to ALL messages - not only new?

The change isn't likely very large. I think the problem is more figuring out where it goes wrong... If someone happens to know more specifically where the problem lays, feel free to share;)

Resolving as dupe.