Closed Bug 280705 Opened 20 years ago Closed 20 years ago

message filters not reliably running in 1.7.5

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 275558

People

(Reporter: jim.jenn, Assigned: sspitzer)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217

My message filters do not appear to be running reliably after upgrading from
1.7.3 to 1.7.5. Running them individually with "Run Now" demonstrates that the
rules aren't broken. The filters run sometimes on new mail but not always. Also,
selecting multiple (well, all) rules in the Message Filters dialog and clicking
"Run Now" doesn't work either (not sure if this is supposed to work, some
filters aren't enabled, but dialog says "Run selected filter*(s)* on:" so it
implies that it should). Most of my filters rely on "nonstandard" headers (e.g.,
X-Text-Classification from POPFile, List-Id for ezmlm mail) -- don't know if
unpredictability is limited to these type of filters or not. No useful
information (errors, etc.) is shown in the filter log, only a normal entry when
the rule actually ran, whether automatically or manually.

Reproducible: Sometimes

Steps to Reproduce:
1. Receive new mail that matches some filter.
2. See if filter matched; if so, great/done.
3. If not, run filter manually.

Actual Results:  
A good percentage of the time, step 3 above is required (i.e., the filter didn't
run automatically). And since I also can't seem to run multiple filters manually
and because I have more than a few filters, it gets old quick.

Expected Results:  
Run the filters automatically every time. If there's a problem, report it in the
log.
duping.

*** This bug has been marked as a duplicate of 275558 ***
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.