Mail filters skipped or munged when automatically checking for new mail on IMAP

RESOLVED WORKSFORME

Status

RESOLVED WORKSFORME
16 years ago
10 years ago

People

(Reporter: thomas.swan, Assigned: sspitzer)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030608
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030608

Three filters were created and ordered as the following
 
1. if subject contains '[listname]' and subject contains '[topicx]' move to folder a
2. if subject contains '[listname]' and subject contains '[topicy]' move to folder b
3. if subject contains '[listname]' and subject doesn't contain '[topicy]' move
to folder c

Only filter rule 3 is being applied to mail received from automatic checks.  On
checking new mail (on startup), the filters are applied correctly.   Manually
running the filters on the inbox or the misplaced messages in folder c works
correctly.  

However, when the mailbox is automatically polled for new mail only the last
filter is applied or the second filter is skipped (i.e. check for new messages
every x minutes).

I haven't been able to isolate the problem down to a specific number of filters
or the combination of multiple subject conditions.  I checked to make sure the
"match all conditions" instead of "match any condition" were applied to each
filter.   Again, this problem only occurs when Mozilla automatically polls for
new mail on an already open connection.   



Reproducible: Always

Steps to Reproduce:
1. Create filter rules
2. Check for new messages
3. Wait for new mail to come in matching conditions on 2nd rule


Actual Results:  
Mail matching rule 2 is moved to rule 3's folder

Expected Results:  
Move it to the correct folder

This is in 1.4 latest nightly (2003060805) and in the trunk.
Product: MailNews → Core
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
(Reporter)

Comment 2

13 years ago
Yes, this has not occurred in a long time.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED

Updated

13 years ago
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---

Comment 3

13 years ago
No changes were made to the code base by this bug, worksforme.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago13 years ago
Resolution: --- → WORKSFORME
(Reporter)

Comment 4

13 years ago
Wow! No changes were made in the codebase from 2003-06-10 to 2005-09-28?  

Worksforme is not an exact resolution for a legitimate problem that could be
reproduced consistently, and then after some sequence of code changes could no
longer be repeated.

Leaving alone.

Comment 5

13 years ago
he just means no patch was attached to this bug - we can't point to a particular
change that fixed this either. And that's one meaning of WFM - it works in the
latest builds...
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.