Closed
Bug 563486
Opened 15 years ago
Closed 14 years ago
Too many terms in message filter, unintelligible error message
Categories
(MailNews Core :: Filters, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: douger34, Unassigned)
Details
(Whiteboard: [closeme 2011-09-01])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 (.NET CLR 3.5.30729)
Build Identifier: 3.0.4
If you put too many terms in a message filter you get an unintelligible error message. Something about having an invalid term in your search expression. This message should be changed to say something like "Too many terms in your message filter".
Reproducible: Always
Steps to Reproduce:
1. Repeatedly add terms to a message filter until you get the error message
2.
3.
Actual Results:
Get message about "an invalid term in search expression".
Expected Results:
Message "Too many terms in your message filter."
Sorry if I'm missing some of the precise details. I have only a dialup connection at home and bugzilla has become unusable there because it takes so long to load. My guess is it's become bloated with JavaScript.
Comment 1•15 years ago
|
||
Can you try to add the proper error you are getting ? can you share you msgfilter.dat file with us so we have a testcase ?
Component: Preferences → Filters
Product: Thunderbird → MailNews Core
QA Contact: preferences → filters
Comment 2•14 years ago
|
||
Doug? Do you still see this problem?
(In reply to Ludovic Hirlimann [:Usul] from comment #1)
> Can you try to add the proper error you are getting ? can you share you
> msgfilter.dat file with us so we have a testcase ?
Whiteboard: [closeme 2011-09-01]
| Reporter | ||
Comment 3•14 years ago
|
||
I'm running TB 5.0. and just retested and was unable to reproduce that problem after adding a very large number of entries to my largest filter. It used to be very easy for me to reproduce. Seems fixed to me.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•