Closed
Bug 558495
Opened 14 years ago
Closed 14 years ago
Wrong REPLY-TO address default for subsequent new accounts.
Categories
(Thunderbird :: Account Manager, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 530142
People
(Reporter: dannyfox, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 In Thunderbird, when running ADD MAIL ACCOUNT, and this is second or later account, the REPLY-TO address defaults to the reply-to address of whatever account the scroll bar is sitting on. It should default to the email address being added (), or to blank/null (acceptable). Reproducible: Always Steps to Reproduce: 1.Create at least two email accounts, and give each a unique reply-to address, such as: aaa@bbb.ccc and xxx@yyy.zzz 2.Set the scroll bar on one of these accounts. 3.Run ADD MAIL ACCOUNT and enter something recognizable to create the account. Actual Results: Recall where the scroll bar was. Check REPLY-TO of the account just added. It will be from the account with the scroll bar. Expected Results: My preference is for the REPLY-TO address to be the same as the email address being entered. Acceptable default would be to leave it blank. The REPLY-TO address should NOT capture info from any other account or be related to any other account, unless deliberately keyed in. Prediction: This bug will explain problems where "replies" are mysteriously going astray. The replies are going exactly where they are being told to go -- but it's to the wrong address and the sender hasn't noticed.
Comment 1•14 years ago
|
||
This looks like bug 530142, which is slightly more general -- roughly speaking, reply-to addresses are accidentally copied whenever focus is changed from one account to another. Feel free to reopen if that's not so.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•