No longer able to use alternate "from" email addresses
The latest Thunderbird update seems to have negated the ability to use alternate email addresses in outgoing messages. I am able to specify an alternate email address to use as the "email" & "reply to" addresses in my identity, yet the outgoing message now always uses my base address which is the one I wish to disguise. When recipients reply, it is now always received on my base address, not the alternate address I have specified in the identity. It worked previously, so I assume a recent update ruined it.
My email uses a Google IMAP server, which I didn't want yet was forced into by my service provider. I am wondering if I must convert the Google server to POP to regain the email identity functionality.
Izmjenjeno
Izabrano rješenje
If you send from a non-gmail account, but use the gmail smtp server, gmail will replace the non-gmail address with the gmail address associated with the smtp. Recipients will see the gmail account as the sender. To avoid this, use the smtp for the non-gmail account, or add the non-gmail account to the gmail account in gmail website settings, Account & Import, Send mail as.
Pročitajte ovaj odgovor sa objašnjenjem 👍 2All Replies (4)
Odabrano rješenje
If you send from a non-gmail account, but use the gmail smtp server, gmail will replace the non-gmail address with the gmail address associated with the smtp. Recipients will see the gmail account as the sender. To avoid this, use the smtp for the non-gmail account, or add the non-gmail account to the gmail account in gmail website settings, Account & Import, Send mail as.
Fabulous, thanks sfhowes! I added the desired address to gmail as an alias, now it works from Thunderbird. Still, it is strange that this was not previously required; I wonder, did Google recently change something?
In gmail I also selected "Reply from the same address the message was sent to", since it was set to "Always reply from default address", even though it says that can be changed when sending (which did not seem to work). Perhaps that is all that was required rather than adding the alias address, yet I have done both to be certain.
I think the Google policy of swapping in the gmail address without notice has been in place for years, and it's especially useful for ISP accounts that don't have secure smtp servers. I don't know what has changed at the gmail end, although they do seem to enforce or prefer OAuth2 authentication now instead of 'normal password'.
Not sure about the 'Always reply...' setting, but some simple tests should reveal the effect. It may work on the gmail website but not through mail clients. Adding the address as a sender does work with TB.