253368 - Tools/Run Filters on Folder generate javascript error.

Status: RESOLVED DUPLICATE of bug 252041

(MailNews Core :: Filters, defect)

Description

[Keith Hopkins]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616

Filtering does not take place. An error is generated (seen in Javascript console).

Reproducible: Always
Steps to Reproduce:
1. Open Javascript console.  Clear it.
2. Select some folder on server that contains messages. (I'm using an Exchange
200x server)
3. Select from menubar, Tools/Run Filters on Folders.
4. Check Javascript console for errors.
Actual Results:  
Error: [Exception... "Component returned failure code: 0x80070057
(NS_ERROR_ILLEGAL_VALUE) [nsIMsgFilterService.applyFiltersToFolders]"  nsresult:
"0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame ::
chrome://messenger/content/mailWindowOverlay.js :: MsgApplyFilters :: line 1385"
 data: no]
Source File: chrome://messenger/content/mailWindowOverlay.js
Line: 1385

Expected Results:  
For the filters to function (no errors)

msgFilterRules.dat available, contact me directly for it please. (I don't want
to include it in the case)

Comment 1

[Miguel]

*This only happens with IMAP accounts*, with POP accounts there's NO problem

And the platforms should be ALL

Comment 2

[Mike Cowperthwaite]

Reproduced with
  Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a3) Gecko/20040824

Doesn't seem to matter what the filters are.

Keith Hopkins, if you report bugs in the future, remember that the type of mail 
account is important; I didn't think to try this on IMAP when I first saw your 
report.

Comment 3

[Mike Cowperthwaite]

Also reproduced with
  Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040803

(In reply to comment #2)
> Doesn't seem to matter what the filters are.

Sorry, I was wrong about this.  As with bug 252041, the problem appears with a 
filter that accesses the Priority field of the message.  Keith Hopkins, does 
that match your experience?

Comment 4

[Keith Hopkins]

(In reply to comment #3)
> Sorry, I was wrong about this.  As with bug 252041, the problem appears with a 
> filter that accesses the Priority field of the message.  Keith Hopkins, does 
> that match your experience?

Correct.  The very first rule was Priority based (changes the Label).  I
disabled it, and ran "Tools/Run Filters" again.  No error appears, and filtering
takes place.

Comment 5

[Mike Cowperthwaite]

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