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!

Este site está com funcionalidades limitadas enquanto realizamos manutenção para melhorar sua experiência de uso. Se nenhum artigo resolver seu problema e você quiser fazer uma pergunta, nossa comunidade de suporte pode te ajudar em @FirefoxSupport no Twitter e /r/firefox no Reddit.

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Disable Return-Path in email Headers

  • 2 respostas
  • 1 tem este problema
  • 3 visualizações
  • Última resposta de beeblebrox-bsd

more options

Hi,

I have a primary account with Gmail, and several alias domains (personal vs business etc). When sending email from Thunderbird, the Headers include "Return-Path", which reveals the Gmail primary domain on the account. No such Header appears when I send similar emails through the browser / Gmail web portal.

I would like to omit the Return-Path Header when using Thunderbird to send emails.

Thanks for your help.

Hi, I have a primary account with Gmail, and several alias domains (personal vs business etc). When sending email from Thunderbird, the Headers include "Return-Path", which reveals the Gmail primary domain on the account. No such Header appears when I send similar emails through the browser / Gmail web portal. I would like to omit the Return-Path Header when using Thunderbird to send emails. Thanks for your help.

Alterado por beeblebrox-bsd em

Solução escolhida

Thanks Matt,

If I understood you correctly, it's actually the Gmail MX server appending the Return-Path header per SMTP protocol, while the web portal is in fact not using SMTP thus no such header is appended through web mail.

Gmail Help sort of confirms this: Important: While these directions let you send emails from a custom email alias at your domain, email recipients can still find your personal Gmail address if they inspect the email headers.

Since each user is assigned a single Login / SMTP credential per Primary Domain name (and no additional Login / SMTP credentials exist for the Alias Domains), the best solution is to set the Primary Domain to the Business DN, because I don't mind if the Business DN is revealed in headers. This seems like the most professional looking solution.

Thanks.

Ler esta resposta 👍 0

Todas as respostas (2)

more options

Return path is defined in the RFC for email. As far as I am aware only the recipient’s mail server is supposed to add a Return-Path header. SO over riding it is Thunderbird should not be possible as it should not set it.

Just be clear, what happens with google in SMTP is nothing like what happens in Google with web mail. Using one as a reason for anything just does not fly for gmail.

Perhaps you would be best served to send your mail using the domains the accounts are associated with. Using GMail to cover all outgoing mail sort of works, but the recipient servers might tend to classify mail from gmail with other domains as spam. Or as you have identified, record where they are coming from.

more options

Solução escolhida

Thanks Matt,

If I understood you correctly, it's actually the Gmail MX server appending the Return-Path header per SMTP protocol, while the web portal is in fact not using SMTP thus no such header is appended through web mail.

Gmail Help sort of confirms this: Important: While these directions let you send emails from a custom email alias at your domain, email recipients can still find your personal Gmail address if they inspect the email headers.

Since each user is assigned a single Login / SMTP credential per Primary Domain name (and no additional Login / SMTP credentials exist for the Alias Domains), the best solution is to set the Primary Domain to the Business DN, because I don't mind if the Business DN is revealed in headers. This seems like the most professional looking solution.

Thanks.