241218 - "Run Filters on Folder" doesn't work when folder is local

Status: RESOLVED DUPLICATE of bug 177093

(MailNews Core :: Filters, defect)

Description

[Thomas Wolf]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040316
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040316

I have a local folder on which I want to run my mail filters.  But doing
"Tools->Run Filters on Folder" does nothing!  I know the single filter I have
active should find a bunch of messages, since I used the same filter to get
those messages from the IMAP Inbox into this folder to begin with!

Incidentally, why doesn't the "Message Filters" dialog allow one to pick a local
folder to run the selected filter(s) against?  Perhaps this whole thing is just
a design limitation?

Reproducible: Always
Steps to Reproduce:
1. With an IMAP account (also for POP?  I don't know), create a local folder on
your disk and move a few messages from the INBOX to the local folder A.
2. Create a filter that moves messages containing some keywords to another local
folder B.
3. Try to run the new filter against the local folder A.

Nothing happens.

Actual Results:  
Nothing.

Expected Results:  
Move the messages from folder A to folder B.

Comment 1

[Mike Cowperthwaite]

It *is* a design limitation.
Run Filters on Folder runs only the filters defined for the "account" containing 
the selected folder.  "Local Folders" is (internally) an account, but is not 
allowed its own filters currently (this is bug 177093).  

I'm duping your bug to that one because that is the primary issue that needs to 
be solved to achieve your ends, altho it's not directly the same.  That's 
because: even if you could define filters for Local Folders, your current IMAP 
filter wouldn't run on them; you'd have to replicate the filter for Local 
Folders. (See bug 129883.)

Then, once that was solved, there would need to be a new UI to select which 
filters get run under which contexts.  I don't think there's a bug for that yet; 
it's a big issue that I suspect requires some fundamental reworking of the 
filtering internals.

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