Closed Bug 296519 Opened 20 years ago Closed 20 years ago

run filters on folder ignores priority rule

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 252041

People

(Reporter: strunk, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

The Run Filters on Folder function ignores any priority filter rules. The same
rules work fine for live incoming mail.

Reproducible: Always

Steps to Reproduce:
1. send yourself a message with a priority assigned
2. create a filter matching the assigned priority 
3. invoke Run Filters on Folder
4. no action will be performed
5. send yourself another message with the same priority
6. the chosen action for the filter will be performed




thunderbird version 1.0.2 (20050317)
tested with imap account only
This seems to be an IMAP only issue. In according to current code, it is invalid
to search by priority with IMAP. If you take a look at the code, you will see
that the priority attribute is not handled in nsMsgSearchAdapter::EncodeImapTerm().

http://lxr.mozilla.org/seamonkey/source/mailnews/base/search/src/nsMsgSearchAdapter.cpp#400

nsMsgFilterService::ApplyFiltersToFolders() -> ...
nsMsgSearchOnlineMail::ValidateTerms () -> ...
nsMsgSearchAdapter::EncodeImapTerm()
{
...
   switch (attrib)
   {
>> no priority attribute handling here
>> and execution falls into
       NS_ASSERTION(PR_FALSE, "invalid search operator");
       return NS_ERROR_INVALID_ARG;
...
}

However, I could confirm that priority rule is working with POP on Win2K3.
Note that the dupe also describes an error that appears in the JavaScript 
console in this event.

*** This bug has been marked as a duplicate of 252041 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.