Closed Bug 380577 Opened 18 years ago Closed 17 years ago

"apply filters to folder" doesn't work

Categories

(Thunderbird :: General, defect)

Product:
Thunderbird
Component:
General
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 184490

People

(Reporter: sven.koehler, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3 Build Identifier: Version 2.0.0.0 (20070326) When i hit the "apply filters to folder" (in german it's called "Filter auf Orner anwenden") menu, i expect Thunderbird to go through the folder and applying the filters to each message. But this does not happen. Messages stay inside my Inbox that should be moved. It doesn't work anymore, since i upgraded from latest 1.5-Version to 2.0. The filters work correctly, when Thunderbird fetches new messages from my university IMAP-Inbox. Messages already marked as read, get not filtered. So i want to filter them either, which would move them to my IMAP-account on my local server. But as described above, it doesn't work. Reproducible: Always
What filter criteria are you using?
Version: unspecified → 2.0
(In reply to comment #1) > What filter criteria are you using? I'm using lots of different filters. Filter on subject, to, from, list-id, ... How can i show them to you? Can i export them somehow?
Preferably track it down and just write the criteria for the filter that doesn't work. List-id is a custom header, so if it's only that -> bug 184490.
(In reply to comment #3) > Preferably track it down and just write the criteria for the filter that > doesn't work. List-id is a custom header, so if it's only that -> bug 184490. I have LOTS of custom header filters. So yes, this may be the bug i'm seing. It it possible, that the whole filter chain gets aborted after the first custom header filter? BTW: how to track it down? I hoped, that i would see some exception in the console. (I'm using http://console2.mozdev.org/, and it shows internals exception too, as far as i know).
Sven, do the recent comments bug 184490 make it sound even more like your problem?
I read last 10 comment of that bug. So i think, this can be marked as a duplicate of bug 184490. If i still encounter problems after that bug has been fixed, then i will reopen this one.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.