Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

Trang web này sẽ có chức năng hạn chế trong khi chúng tôi trải qua bảo trì để cải thiện trải nghiệm của bạn. Nếu một bài viết không giải quyết được vấn đề của bạn và bạn muốn đặt câu hỏi, chúng tôi có cộng đồng hỗ trợ của chúng tôi đang chờ để giúp bạn tại @FirefoxSupport trên Twitter và /r/firefox trên Reddit.

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

Disable Return-Path in email Headers

  • 2 trả lời
  • 1 gặp vấn đề này
  • 3 lượt xem
  • Trả lời mới nhất được viết bởi 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.

Được chỉnh sửa bởi beeblebrox-bsd vào

Giải pháp được chọn

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.

Đọc câu trả lời này trong ngữ cảnh 👍 0

Tất cả các câu trả lời (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

Giải pháp được chọn

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.