User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 Moved from Moz 1.6 to 1.7 and now the wrong recipient info is pulled from the header for display in the message lists and the Normal (as opposed to "All") headers view. Previously, the name/address of the addressee as entered by the sender would be displayed, regardless of where the message ended up. However, if the message is forwarded to another mail address (or, as in my case, forwarded from multiple accounts through several mail systems to one final collection address), the final address is shown. Not only that, but the "Normal" header no longer shows any secondary recipient addresses. For instance, an email sent to myself and one other person at my office only showed my final collection address as the recipient. I unnecessarily forwarded a copy of the mail to the other recipient as Mozilla did not show that person as being a recipient of the original mail. To be precise, it seems that Mozilla 1.6 took recipient info from the "X-Original-To:" line, whereas Mozilla 1.7 takes recipient info from the final "Received" information. Reproducible: Always Steps to Reproduce: 1. Send mail to an address that forwards to another address or send mail to multiple "To" addressees. 2. Collect that mail. 3. Read the "Normal" header and look at the recipient info column in the message list. Actual Results: Incorrect recipient info shown. Expected Results: The original address as written by the sender should have appeared in the recipient info column of the message lis, and that same information along with any secondary addresee information should have appeared in the "Normal" header view.
Retraction: This behavior appeared the same day I upgraded to 1.7. This was, conincidentally, the same day one of my mail companies "upgraded" my account and changed the behavior of their forwarding system. The bug is in THEIR system, not Mozilla.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.