Port Bug 511780 - Archiving does not always place the messages in the correct account's Archive folder (Archive shouldn't use X-Account-Key: header, at least when account is not Global Inbox owner)

RESOLVED INVALID

Status

RESOLVED INVALID
9 years ago
8 years ago

People

(Reporter: InvisibleSmiley, Assigned: InvisibleSmiley)

Tracking

(Depends on: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

9 years ago
Bug 511780 checkin comment was: "use server's identity for archive folder, if found, otherwise use hdr/x-mozilla-account key to determine identity".

Porting the fix is simple once bug 512507 is fixed (touches parts introduced through that bug). We only need to take care that getIdentityForHeader(msgs[0]) is again replaced by GetIdentityForHeader(msgs[0], null).

Comment 1

9 years ago
Today I archived the last 2 month's mail in my global inbox, and the mails of sep. goes into my global inbox's Archives folder, the mails of aug. goes into my imap account's Archives folder, which shouldn't happen.
I'm not sure if it's the same bug?

http://forums.mozillazine.org/viewtopic.php?f=29&t=1508675&start=0
(Assignee)

Comment 2

9 years ago
(In reply to comment #1)
> Today I archived the last 2 month's mail in my global inbox, and the mails of
> sep. goes into my global inbox's Archives folder, the mails of aug. goes into
> my imap account's Archives folder, which shouldn't happen.
> I'm not sure if it's the same bug?
> 
> http://forums.mozillazine.org/viewtopic.php?f=29&t=1508675&start=0

This bug is about porting the fix for Thunderbird bug 511780 (which was checked in after TB 3.0b4 was cut) to SeaMonkey. Since you are using TB 3.0b4 you should check a current Shredder nightly build or try TB 3.0rc1 once it is released (note that I cannot tell you when that will be). Anyway, /this/ bug won't help you.
(Assignee)

Comment 3

8 years ago
TB reverted that code part in bug 517514 so this is now obsolete.
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.