搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Interaction of email alias and Reply/Reply-All

  • 1 回覆
  • 1 有這個問題
  • 15 次檢視
  • 最近回覆由 Alan Mead

more options

I'm having trouble having my second email address cc'd when I reply-all.

For historical reasons my main email is like [email protected] but I like to use [email protected], so we set up "[email protected]" as alias and I set up TB as:

Account name: [email protected] Your name: Bob Foobar Email Address: [email protected] Reply-to Address: [email protected]

If I send an email to some addresses, and they reply, TB offers my a Reply (if there's one correspondent) or else Reply-All that goes to [email protected] and does not include [email protected]. That's perfect.

But replies from people using Yahoo and Gmail trigger TB to offer Reply-All, even if there's one recipient, and my [email protected] is included in the reply-all.

So, if I email [email protected], and Abe replies; TB then allows me to click Reply-All and the reply goes to [email protected] and [email protected]. That's semi-manageable when I'm corresponding with one person, but when I'm corresponding with a group, I need to reply-all and I often forget to delete my own email and get a copy, which is confusing to people and annoying to me. It's annoying enough to want to change my email to avoid this issue, but this is happening on a fresh install of the latest TB on a and Windows 10. I didn't have this issue yesterday with a recent version of TB on a W7 computer. I think I solved this years ago on my old computer, but I cannot recall how. I noticed this issue because I replied to a group and accidentally included myself today, wheras I had not done so earlier this week with my old TB.

I notice that if I view source that the replies that work fine (do not add in my email alias) include the Reply-All header and those that trigger the bad behavior do not include it (that's the source of the reply to my email). But I cannot tell Yahoo and Gmail to change things. Either there's something I need to do to get them to include that header, or I need to configure TB to be more robust about this issue.

Here's what I have done (none of which have helped): 1. Set the reply-all (as shown above) 2. Done 60 minutes of reading and googling about this issue 3. Managed identities, edited the identity, and under Private Data added bob*@domain.org to "Reply from this identity when delivery headers match" 4. Added myself to contacts as [email protected] with [email protected] as an alternative email. 5. Changed the "Description" of the outgoing SMTP settings to "<Bob Foo> [email protected]" 6. Changed the "Description" of the outgoing SMTP settings to "[email protected]" 7. Changed the "Description" of the outgoing SMTP settings to "[email protected]" 8. Looked for a "Smart Reply" button (I don't see one)

I'm having trouble having my second email address cc'd when I reply-all. For historical reasons my main email is like [email protected] but I like to use [email protected], so we set up "[email protected]" as alias and I set up TB as: Account name: [email protected] Your name: Bob Foobar Email Address: [email protected] Reply-to Address: [email protected] If I send an email to some addresses, and they reply, TB offers my a Reply (if there's one correspondent) or else Reply-All that goes to [email protected] and does not include [email protected]. That's perfect. But replies from people using Yahoo and Gmail trigger TB to offer Reply-All, even if there's one recipient, and my [email protected] is included in the reply-all. So, if I email [email protected], and Abe replies; TB then allows me to click Reply-All and the reply goes to [email protected] and [email protected]. That's semi-manageable when I'm corresponding with one person, but when I'm corresponding with a group, I need to reply-all and I often forget to delete my own email and get a copy, which is confusing to people and annoying to me. It's annoying enough to want to change my email to avoid this issue, but this is happening on a fresh install of the latest TB on a and Windows 10. I didn't have this issue yesterday with a recent version of TB on a W7 computer. I think I solved this years ago on my old computer, but I cannot recall how. I noticed this issue because I replied to a group and accidentally included myself today, wheras I had not done so earlier this week with my old TB. I notice that if I view source that the replies that work fine (do not add in my email alias) include the Reply-All header and those that trigger the bad behavior do not include it (that's the source of the reply to my email). But I cannot tell Yahoo and Gmail to change things. Either there's something I need to do to get them to include that header, or I need to configure TB to be more robust about this issue. Here's what I have done (none of which have helped): 1. Set the reply-all (as shown above) 2. Done 60 minutes of reading and googling about this issue 3. Managed identities, edited the identity, and under Private Data added bob*@domain.org to "Reply from this identity when delivery headers match" 4. Added myself to contacts as [email protected] with [email protected] as an alternative email. 5. Changed the "Description" of the outgoing SMTP settings to "<Bob Foo> [email protected]" 6. Changed the "Description" of the outgoing SMTP settings to "[email protected]" 7. Changed the "Description" of the outgoing SMTP settings to "[email protected]" 8. Looked for a "Smart Reply" button (I don't see one)

被選擇的解決方法

Alan Mead said

I set up TB as: Account name: [email protected] Your name: Bob Foobar Email Address: [email protected] Reply-to Address: [email protected]

I may have solved this. Looks like changing my email above to [email protected] fixes the issue.

從原來的回覆中察看解決方案 👍 0

所有回覆 (1)

more options

選擇的解決方法

Alan Mead said

I set up TB as: Account name: [email protected] Your name: Bob Foobar Email Address: [email protected] Reply-to Address: [email protected]

I may have solved this. Looks like changing my email above to [email protected] fixes the issue.