Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

A tricky, repeatable bug found in Thunderbird Reply and Reply-All using the wrong from address

  • 2 replies
  • 0 have this problem
  • 1 view
  • Last reply by doug102

more options

This one has been vexing me literally for years, but I finally figured it out, I think. At least, I can repeat the issue.

The symptom: sometimes when picking reply or reply-all, thunderbird puts in somebody else's from address from my organization!

Version 102.10.0 (64-bit) and earlier! (at least 2 years)

Setup:

I have 2 accounts setup, a work account and a personal. The work account is the second one in the setup order (this may be significant, or not)

When I get an email to my work account, I want the reply address when I click on the reply or reply-all button to come from this account.

So, I check the checkbox under account settings that says " Reply from this identify when delivery headers match: and I put in the work *@domain.com address

But, if I use *@domain.com, in certain emails, when I click reply or reply-all, it uses somebody else's address, sometimes (not always).

If I use just domain.com without the *@, it doesn't do this. When this is combined with an email header that has a line matching:

X-Google-Original-From: <someaddress> - it will use this address!!

If I just use domain.com, it doesn't do this. If the message that I'm replying to doesn't have this header, it uses my correct from address (I have not exhaustively tested this part, but it appears to be true in a sample test of about 5 messages with and without this header)

The combination of these 2 things seems to expose a devilish bug!

I hope this helps to resolve this issue that I have seen bug reports about, seemingly back to 2014.

This one has been vexing me literally for years, but I finally figured it out, I think. At least, I can repeat the issue. The symptom: sometimes when picking reply or reply-all, thunderbird puts in somebody else's from address from my organization! Version 102.10.0 (64-bit) and earlier! (at least 2 years) Setup: I have 2 accounts setup, a work account and a personal. The work account is the second one in the setup order (this may be significant, or not) When I get an email to my work account, I want the reply address when I click on the reply or reply-all button to come from this account. So, I check the checkbox under account settings that says " Reply from this identify when delivery headers match: and I put in the work *@domain.com address But, if I use *@domain.com, in certain emails, when I click reply or reply-all, it uses somebody else's address, sometimes (not always). If I use just domain.com without the *@, it doesn't do this. When this is combined with an email header that has a line matching: X-Google-Original-From: <someaddress> - it will use this address!! If I just use domain.com, it doesn't do this. If the message that I'm replying to doesn't have this header, it uses my correct from address (I have not exhaustively tested this part, but it appears to be true in a sample test of about 5 messages with and without this header) The combination of these 2 things seems to expose a devilish bug! I hope this helps to resolve this issue that I have seen bug reports about, seemingly back to 2014.

All Replies (2)

more options

Why don't you post the bug in bugzilla?

more options

I actually started trying to get to post to Bugzilla, but somehow it looped me back to here.