Closed Bug 291452 Opened 16 years ago Closed 16 years ago
Drafts/Templates selects wrong 'From:' account (shared IMAP)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-1.3.1 Firefox/1.0.3 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-1.3.1 Firefox/1.0.3 When opening a draft or template, message compose window uses X-Identity-Key to identify which 'From:' account it should select. A common practice with IMAP accounts is that you use server-side Drafts and Templates folder. But if you are using one IMAP account on more different installations of thunderbird (/machines) X-Identity-Key is not very likely to identically match the account on all of them - on one machine the same account may have X-Identity-Key equal to 'id1' whereas on another it may be 'id2'. Reproducible: Always Steps to Reproduce: 1. On each of two different installations of thunderbird setup a couple (e.g. Account1, Account2) of imap acounts in _DIFFERENT_ order. 2. On one installation create a new message from 'Account1' account and save it as draft 3. On the other installation open that message from Account1's Drafts folder Actual Results: Selected 'From:' account will be 'Account2' instead of 'Account1' Expected Results: Selected 'From:' account should again be 'Account1' If you erase 'Acount2' on the second machine (i.e. the first account with 'id1'), that draft message will fail to open with error: "An error occured while creating a message compose window. Please try again." That is, of course, because thunderbird was unable to find an account with X-Identity-Key equal to 'id1'.
Summary: Drafts/Templates selects wrong 'From:' account → Drafts/Templates selects wrong 'From:' account (shared IMAP)
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/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → EXPIRED
Please reopen this bug, as I can reproduce it on: Thunderbird 184.108.40.206pre (X11/20071202) In my case, I had saved a message to the IMAP Drafts folder of the email@example.com account from machine A, and reopened the message on machine B, which has two accounts: firstname.lastname@example.org and email@example.com. firstname.lastname@example.org is the default account in Thunderbird on machine B. The From: address in the draft message changed to email@example.com, despite the fact that it was in the firstname.lastname@example.org Draft folder. I didn't notice the change in From: address, and ended up sending a work email from my personal account.
This looks like the same problem as bug 394216. It is indeed a problem with shared IMAP accounts, and needs a fix. What about a preference to NOT store X-Identity-Key in Drafts?
You need to log in before you can comment on or make changes to this bug.