Closed Bug 327268 Opened 20 years ago Closed 19 years ago

Identical clientside rules create multiple copies of message when Thunderbird is running at two different locations with same set of rules.

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 193325

People

(Reporter: mick, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 Build Identifier: version 1.5 (20051201) Say I have a open TB client. I make a rule to move mail from foo@bar.com when it arrives, to a subfolder of my inbox. All good. It moves it no problem. Then I start another client on another machine (say, at home, the first client is at work) -- both accessing the same IMAP server. When both are open at the same time, and mail arrives, I find that I have two copies of the message in the folder specified. Reproducible: Always Steps to Reproduce: 1. Create identical client-side rules on each instance of TB on each machine. 2. Receive mail. 3. Watch duplication arise. Actual Results: I had two copies of the same message in the folder which I asked TB to move the message to (one from each client, I assume). Expected Results: One copy of the message. I expect it to check whether the message is there in the first place, before moving it. Surely Thunderbird can perform a simple task like this which even Outlook can manage.
Summary: Multiple copies of message when Thunderbird is running at two different locations → Identical clientside rules create multiple copies of message when Thunderbird is running at two different locations with same set of rules.
My apologies for the Outlook comment - didn't intend it to come out like that.
Version: unspecified → 1.5
Duplicate of bug 304735 and/or Core bug 214297 -> Core bug 193325?
Agreed, dupe. *** This bug has been marked as a duplicate of 193325 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.