Closed
Bug 214297
Opened 22 years ago
Closed 22 years ago
filters create duplcates in IMAP if mozilla mail running at more than one location
Categories
(MailNews Core :: Filters, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 193325
People
(Reporter: mozilla.org, Assigned: sspitzer)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
I typically have my Mozilla mail open and running 24hrs on my PC at work. I
have the same mail filters set up on my Mozilla at home. So when I log in at
home, I often end up with 2 copies of the filtered messages in the folders on
my IMAP account. (I'm using the filters to move various mailing list messages
into separate IMAP folders.) Apparently both instances of Mozilla are copying
the incoming file to same destination folder, oblivious to what the other
Mozilla is doing. It seems that Mozilla should be able to detect that the
message has already been copied, and not make such duplicates.
Reproducible: Always
Steps to Reproduce:
1. Set up filter to move messages to an IMAP folder on PC1
2. Set up same filter to move same messages to the same IMAP folder on PC2
3. Have both computers runnning mozilla simultaneously
4. Send email message to self that matches that filter.
Actual Results:
Two copies of the message show up in the destination IMAP folder
Expected Results:
The second instance of Mozilla to try to run the filter should recognize that
the same message already exists in the target folder and take no action.
I have my action on delete set to "move to trash" if that makes a difference.
Comment 1•22 years ago
|
||
Dupe of bug 193325?
Comment 2•22 years ago
|
||
*** This bug has been marked as a duplicate of 193325 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•22 years ago
|
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•