User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1) Gecko/20061010 Firefox/2.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1) Gecko/20061010 Firefox/2.0 I have a few identities linked to my account, e.g. 1) jan@example.com * Bcc: jan@example.com 2) jan@another.example.net * Bcc: jan@example.com * Reply-To: info@another.example.net When I send mail to bob@another.example.net using identity 1, and then reply to that message (which is in my Inbox), I expect TB to choose identity 1. Instead, it chooses identity 2, including the Reply-To header. I'm guessing it gives more weight to the "To:" field, or it first looks at the "From:" and then at the "To:" field, and chooses its identity based on that. The To: field is correctly set to the original message's To: address, in this case bob@another.example.net Reproducible: Always

I'm such a tool. I forgot to mention that I am using Thunderbird/3.0a1 ("version 3 alpha 1 (20061205)") with an IMAP account.

I believe that, if the message doesn't have an X-Account-Key header (which is applied to incoming messages), the identity selected on reply is the default identity of whichever account contains the folder with the message. Same behavior in Seamonkey, moving to Core. This is kind of the flip side of bug 327713.

Wow, I can't believe that I'm just now running into this with SM 1.1.17, but sure enough, I had an email come into an alternate address to which I replied. SM dutifully selected the proper identity for the reply, and when I just followed-up to that reply, SM reverted to my default ID. Mike, your comment is likely on target; I wonder if we can #OR# this logic to look for a sender identity which matches an existing one (just thinking out loud without looking at the code). Lewis

The code for replytoself is here: http://mxr.mozilla.org/comm-central/source/mailnews/compose/src/nsMsgCompose.cpp#2004 ... and the 20-30 lines above. Any takers?

This was actually bug 397975.