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

How to get a correct return-path for gmail alias on Windows / Linux / Mac

  • 5 replies
  • 0 have this problem
  • 1 view
  • Last reply by david

more options

I found this topic linked below describing my problem already pretty well - but I'll quickly sum up the example: https://support.mozilla.org/en-US/questions/1375576

I have a domain "mycompany.com" registered and set up for receiving and sending emails. So e.g. I receive and send emails for [email protected] via this mail/smtp server.

Some emails I forward also to my personal gmail account: "[email protected]" and also use this account to reply to incoming company emails. Doing this is easy in the gmail web client by setting up an alias in the gmail account. Replying on emails will choose the correct "from" address. Emails sent this way look like they were sent natively using the mycompany.com mail server.

Now I'm using thunderbird and set it up with the same gmail account, adjust the "email" to "[email protected]" and perfectly working - replying to mails works but makes interesting differences on windows and linux:

  • On linux, mails sent look pretty standard, as if they were sent using the mycompany.com mailserver or through the gmail web client.

this could potentially trigger spam filters and bounces don't arrive at the company account. So I'd like to avoid the wrong return-path. Is there any setting responsible for the different behaviours between linux and windows? This also proves that it's not depending on smtp being used vs using the gmail web client...

I found this topic linked below describing my problem already pretty well - but I'll quickly sum up the example: https://support.mozilla.org/en-US/questions/1375576 I have a domain "mycompany.com" registered and set up for receiving and sending emails. So e.g. I receive and send emails for [email protected] via this mail/smtp server. Some emails I forward also to my personal gmail account: "[email protected]" and also use this account to reply to incoming company emails. Doing this is easy in the gmail web client by setting up an alias in the gmail account. Replying on emails will choose the correct "from" address. Emails sent this way look like they were sent natively using the mycompany.com mail server. Now I'm using thunderbird and set it up with the same gmail account, adjust the "email" to "[email protected]" and perfectly working - replying to mails works but makes interesting differences on windows and linux: * On linux, mails sent look pretty standard, as if they were sent using the mycompany.com mailserver or through the gmail web client. * On windows, mails have set a different return path. "reply to" and "from" is correct ([email protected]) but the return path is shown as "[email protected]" this could potentially trigger spam filters and bounces don't arrive at the company account. So I'd like to avoid the wrong return-path. Is there any setting responsible for the different behaviours between linux and windows? This also proves that it's not depending on smtp being used vs using the gmail web client...

All Replies (5)

more options

I assume you are seeing the sending address in the hidden headers? And when sent from Linux, the headers are different? Technically, what you're doing is spam, sending a message that appears to come from one address when it comes from another. I respect it is a useful technique, but misused by many. So, I'm puzzled that Linux hides the sending address within the headers, or am I misunderstanding?

more options

Thanks for the quick reply! Yes I meant the hidden headers that some people also don't hide... And I'd hardly see the spam here because google does a few things againt it:

Using this "alias" account in gmail uses the original smtp server of "mydomain.com" to send mail. You have to enter smtp user and password during alias setup and additionally for verification it needs to be confirmed using a code generated for one-time verification, which is received by the owner of "[email protected]".

So using the gmail alias means actually using the original smtp for sent mails. That's why there isn't and shouldn't really be a visible difference in mail headers between using the gmail account for sending mail and using the original smtp of mydomain.com.

As a workaround I could also just enter 2 separate accounts in thunderbird: One for receiving gmail's emails and a second one just for sending through mydomain.com's smtp. However in my situation I'm not allowed to use the original smtp due to password policies. However I'm allowed to enter that password in the gmail account where it becomes non accessible for me after initially entering it once. Google saves it in a write-only manner. It's actually the best system for mail delegation and aliases that I know of - while most other mail providers are actually just spoofing names for these kind of services gmail using the legit smtp :)

Additionally I also now tried the behaviour on a mac - it's also setting the return-path to the gmail-address.

more options

OK, my error. I usually see aliases using original server, which works but has the return address issue you mention. My inference is that you have the mydomain account defined as an identity within the gmail account, but using the mydomain smtp server. I attempted to duplicate that and it works as intended. Would you mind posting a screen shot of your identity pane, and one of the smtp settings for the mydomain server? That may help, as it seems there is an incorrect setting somewhere. Thank you.

more options

Now I also must admit an error. Checking the identity setting I noticed I didn't use the gmail server on the linux system but instead the mydomain.com smtp which still set up for testing. After using the gmail server I get the same result on Mac/Linux/Windows. All 3 with the gmail address as return-path and I guess there won't be a fix since thunderbird is using the google smtp for sending. So if I understand it right only google could change that header in their smtp server but they don't seem to support that. Thanks for all the help!

more options

But I think we resolved your ccncern. By having the mydomain smtp server set to the identity, emails written from there violate no spam issues and show from and reply properly. Am I missing something?