Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.software.thunderbird > #21728

Re: Providers that allow a 3rd party address in outgoing mail

Show all headers | View raw

*Jo-Anne* meinte:
> On 8/7/2026 5:49 PM, Thomas Barghahn wrote:
>>
>> Thanks for the clarification — that helps a lot.
>>
>> [...] 
>> 
> Thank you, Thomas. I tried that, but it doesn't work with Proton Mail. 
> The Reply-To line simply disappears on sending. I contacted Proton Mail 
> and received the following response:
> 
> "Currently, Proton Mail does not support using a custom Reply-To address 
> that is not associated with your Proton account when sending emails 
> through Proton Mail Bridge. Even if you set a Reply-To address in 
> Thunderbird, Proton Mail will remove it from outgoing messages if it is 
> not one of your verified addresses or aliases."
> 
> Gmail currently accepts a Reply-To address, so I could switch my 
> university forwarding address to my gmail account. However, Reply-To is 
> limited. I experimented with it earlier today and found that it works 
> for the first email in a conversation. However, once the other party 
> replies to my university address and I try to reply to that party, 
> Reply-To has disappeared.

Thanks again for checking and for sharing Proton’s explanation — that 
makes the situation very clear.

In this case, the limitation isn’t in Thunderbird, but in Proton Mail 
itself. Proton removes any Reply‑To address that isn’t one of your 
verified Proton identities, so Thunderbird can’t override that behavior.

Forwarding‑only university addresses are normally handled through 
Reply‑To, but Proton’s policy prevents exactly that use case.

Gmail allows more flexibility, but only for the first message in a 
conversation. After the first reply, Gmail rewrites the conversation 
flow and the Reply‑To header disappears.

If you want your university forwarding address to work consistently 
across an entire conversation, you may need an email provider that does 
not remove custom Reply‑To headers.

Outlook.com is one of the few large, free, internationally available 
providers that generally keeps Reply‑To intact and does not rewrite 
message headers in ongoing conversations. I can’t speak for every detail 
of their “send as” policies, but for Reply‑To specifically, Outlook 
tends to behave much more predictably than Proton or Gmail.

Your forwarding setup is perfectly valid — it’s just that some providers 
make it easier than others.

Thomas
-- 
== S E N D E Z E I T ===============
+  DATUM  : Samstag, 08. August 2026
+  UHRZEIT: 02:53:40 UHR (MESZ)
== +++ Friedensfest +++ ============

Back to alt.comp.software.thunderbird | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Providers that allow a 3rd party address in outgoing mail Jo-Anne <Jo-Anne@nowhere.com> - 2026-08-07 13:25 -0500
  Re: Providers that allow a 3rd party address in outgoing mail "David E. Ross" <nobody@nowhere.invalid> - 2026-08-07 11:37 -0700
    Re: Providers that allow a 3rd party address in outgoing mail MikeS <MikeS@fred.com> - 2026-08-07 21:10 +0100
      Re: Providers that allow a 3rd party address in outgoing mail "David E. Ross" <nobody@nowhere.invalid> - 2026-08-07 13:26 -0700
      Re: Providers that allow a 3rd party address in outgoing mail Jo-Anne <Jo-Anne@nowhere.com> - 2026-08-07 16:14 -0500
        Re: Providers that allow a 3rd party address in outgoing mail Thomas Barghahn <Th.Barghahn@t-online.de> - 2026-08-08 00:49 +0200
          Re: Providers that allow a 3rd party address in outgoing mail Jo-Anne <Jo-Anne@nowhere.com> - 2026-08-07 18:55 -0500
            Re: Providers that allow a 3rd party address in outgoing mail Thomas Barghahn <Th.Barghahn@t-online.de> - 2026-08-08 02:53 +0200
              Re: Providers that allow a 3rd party address in outgoing mail Jo-Anne <Jo-Anne@nowhere.com> - 2026-08-08 12:26 -0500
    Re: Providers that allow a 3rd party address in outgoing mail Gmail User <gmail@invalid.invalid> - 2026-08-07 21:48 +0100
      Re: Providers that allow a 3rd party address in outgoing mail "Adam H. Kerman" <ahk@chinet.com> - 2026-08-08 16:07 +0000
  Re: Providers that allow a 3rd party address in outgoing mail Gmail User <gmail@invalid.invalid> - 2026-08-07 22:14 +0100
    Re: Providers that allow a 3rd party address in outgoing mail Jo-Anne <Jo-Anne@nowhere.com> - 2026-08-07 16:38 -0500
  Re: Providers that allow a 3rd party address in outgoing mail Stan Brown <someone@example.com> - 2026-08-07 17:07 -0700
    Re: Providers that allow a 3rd party address in outgoing mail Jo-Anne <Jo-Anne@nowhere.com> - 2026-08-08 12:34 -0500
      Re: Providers that allow a 3rd party address in outgoing mail MikeS <MikeS@fred.com> - 2026-08-08 21:11 +0100
        Re: Providers that allow a 3rd party address in outgoing mail "J. P. Gilliver" <G6JPG@255soft.uk> - 2026-08-09 13:08 +0100
          Re: Providers that allow a 3rd party address in outgoing mail Andy Burns <usenet@andyburns.uk> - 2026-08-09 13:35 +0100
            Re: Providers that allow a 3rd party address in outgoing mail "J. P. Gilliver" <G6JPG@255soft.uk> - 2026-08-09 15:34 +0100
              Re: Providers that allow a 3rd party address in outgoing mail Andy Burns <usenet@andyburns.uk> - 2026-08-09 15:45 +0100
  Re: Providers that allow a 3rd party address in outgoing mail "J. P. Gilliver" <G6JPG@255soft.uk> - 2026-08-08 19:59 +0100
    Re: Providers that allow a 3rd party address in outgoing mail Mike Easter <MikeE@ster.invalid> - 2026-08-08 13:23 -0700
      Re: Providers that allow a 3rd party address in outgoing mail Mike Easter <MikeE@ster.invalid> - 2026-08-10 08:15 -0700
        Re: Providers that allow a 3rd party address in outgoing mail Andy Burns <usenet@andyburns.uk> - 2026-08-10 17:24 +0100
    Re: Providers that allow a 3rd party address in outgoing mail Jo-Anne <Jo-Anne@nowhere.com> - 2026-08-08 17:02 -0500
      Re: Providers that allow a 3rd party address in outgoing mail dillinger <dillinger@not.invalid> - 2026-08-09 12:25 +0200
      Re: Providers that allow a 3rd party address in outgoing mail Dnews <dnews@triffid.co.uk> - 2026-08-09 12:14 +0100
        Re: Providers that allow a 3rd party address in outgoing mail "J. P. Gilliver" <G6JPG@255soft.uk> - 2026-08-09 13:33 +0100
  Re: Providers that allow a 3rd party address in outgoing mail Marco Moock <mm@dorfdsl.de> - 2026-08-10 08:34 +0200
    Re: Providers that allow a 3rd party address in outgoing mail Andy Burns <usenet@andyburns.uk> - 2026-08-10 07:54 +0100
      Re: Providers that allow a 3rd party address in outgoing mail MikeS <MikeS@fred.com> - 2026-08-10 09:28 +0100
        Re: Providers that allow a 3rd party address in outgoing mail Andy Burns <usenet@andyburns.uk> - 2026-08-10 09:38 +0100
          Re: Providers that allow a 3rd party address in outgoing mail Marco Moock <mm@dorfdsl.de> - 2026-08-11 14:34 +0200
            Re: Providers that allow a 3rd party address in outgoing mail Andy Burns <usenet@andyburns.uk> - 2026-08-11 14:51 +0100
              Re: Providers that allow a 3rd party address in outgoing mail Marco Moock <mm@dorfdsl.de> - 2026-08-12 15:05 +0200
            Re: Providers that allow a 3rd party address in outgoing mail "Adam H. Kerman" <ahk@chinet.com> - 2026-08-11 14:19 +0000
              Re: Providers that allow a 3rd party address in outgoing mail MikeS <MikeS@fred.com> - 2026-08-12 13:55 +0100
                Re: Providers that allow a 3rd party address in outgoing mail "Adam H. Kerman" <ahk@chinet.com> - 2026-08-12 15:59 +0000
              Re: Providers that allow a 3rd party address in outgoing mail Marco Moock <mm@dorfdsl.de> - 2026-08-12 15:08 +0200
                Re: Providers that allow a 3rd party address in outgoing mail "Adam H. Kerman" <ahk@chinet.com> - 2026-08-13 20:27 +0000
                Re: Providers that allow a 3rd party address in outgoing mail Marco Moock <mm@dorfdsl.de> - 2026-08-14 06:59 +0200
                Re: Providers that allow a 3rd party address in outgoing mail "Adam H. Kerman" <ahk@chinet.com> - 2026-08-14 13:45 +0000
                Re: Providers that allow a 3rd party address in outgoing mail Mike Easter <MikeE@ster.invalid> - 2026-08-14 15:04 -0700
                Re: Providers that allow a 3rd party address in outgoing mail dillinger <dillinger@not.invalid> - 2026-08-15 00:32 +0200
                Re: Providers that allow a 3rd party address in outgoing mail Mike Easter <MikeE@ster.invalid> - 2026-08-14 15:40 -0700
                Re: Providers that allow a 3rd party address in outgoing mail "Adam H. Kerman" <ahk@chinet.com> - 2026-08-15 00:38 +0000
                Re: Providers that allow a 3rd party address in outgoing mail Gmail User <gmail@invalid.invalid> - 2026-08-15 00:07 +0100
                Re: Providers that allow a 3rd party address in outgoing mail Gordon <Gordon@leaf.net.nz> - 2026-08-15 09:06 +0000
                Re: Providers that allow a 3rd party address in outgoing mail Gmail User <gmail@invalid.invalid> - 2026-08-14 23:35 +0100
                Re: Providers that allow a 3rd party address in outgoing mail Mike Easter <MikeE@ster.invalid> - 2026-08-14 16:32 -0700
                Re: Providers that allow a 3rd party address in outgoing mail Nobody <jock@soccer.com> - 2026-08-14 17:14 -0700
                Re: Providers that allow a 3rd party address in outgoing mail Mike Easter <MikeE@ster.invalid> - 2026-08-14 17:31 -0700
                Re: Providers that allow a 3rd party address in outgoing mail Nobody <jock@soccer.com> - 2026-08-14 17:38 -0700
                Re: Providers that allow a 3rd party address in outgoing mail Mike Easter <MikeE@ster.invalid> - 2026-08-14 17:47 -0700
                Re: Providers that allow a 3rd party address in outgoing mail Nobody <jock@soccer.com> - 2026-08-14 18:30 -0700
                Re: Providers that allow a 3rd party address in outgoing mail Mike Easter <MikeE@ster.invalid> - 2026-08-14 19:39 -0700
        Re: Providers that allow a 3rd party address in outgoing mail Gmail User <gmail@invalid.invalid> - 2026-08-10 20:53 +0100

csiph-web