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


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

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

From Thomas Barghahn <Th.Barghahn@t-online.de>
Newsgroups alt.comp.software.thunderbird
Subject Re: Providers that allow a 3rd party address in outgoing mail
Date 2026-08-08 00:49 +0200
Organization 🐹 𝓗𝓪𝓶𝓼𝓽𝓮𝓻-𝓒𝓵𝓾𝓫 🐹
Message-ID <b4a0.140ec.acst.23thbird@barghahn-online.de> (permalink)
References <11557vb$pst4$1@dont-email.me> <11558lj$t762$1@dont-email.me> <1155e2v$v33g$1@dont-email.me> <1155hqv$t3si$1@dont-email.me>

Show all headers | View raw


*Jo-Anne* meinte:
>
> I am the OP, and I'm sorry I wasn't clear. The university offers a 
> forwarding address for alumni. You can forward emails from that address 
> to whatever regular email address you prefer, which means, for example, 
> that when your ISP changes, you can keep your university email address 
> because the university will forward the emails with that address to 
> whatever real address you choose. But that's all the university does. It 
> does not provide POP or IMAP incoming email service, and it does not 
> provide SMTP outgoing service.
> 
> Proton and most other email services (as far as I can tell) do not allow 
> outgoing mail to use a 3rd party address. This means I can receive email 
> in Proton from someone who emails me at my university address; but when 
> I respond, my response will come from my Proton email address, not from 
> the address the person emailed me at--which is confusing.

Thanks for the clarification — that helps a lot.

I think there may be a small misunderstanding about how email replies
work when you’re using a forwarding address.

Even if your university doesn’t provide IMAP/POP or SMTP service, you
can still make sure that replies to your messages go back to your
university address. You don’t need to “send from” that address in the
technical sense.

What you’re looking for is the *Reply‑To field* in your mail client.

You can send outgoing mail through Proton as usual, but set the Reply‑To
address to your university forwarding address. Then:

• people will receive your message normally
• when they hit “Reply”, their response will go to your university
   address
• the university forwards it to your real mailbox

This way, conversations stay consistent, and you don’t need SMTP access
from the university at all.

It’s a simple setting, but it solves exactly the situation you described.

[1] Reply-To field:
<https://barghahn-online.de/Pictures/tb_reply-to_adress.png>

HTH! :-)

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

Back to alt.comp.software.thunderbird | Previous | NextPrevious 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