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

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

From	"Adam H. Kerman" <ahk@chinet.com>
Newsgroups	alt.comp.software.thunderbird
Subject	Re: Providers that allow a 3rd party address in outgoing mail
Date	2026-08-11 14:19 +0000
Organization	A noiseless patient Spider
Message-ID	<115fb19$2fid$1@dont-email.me> (permalink)
References	<11557vb$pst4$1@dont-email.me> <115c243$2vlmo$1@dont-email.me> <ndtgthF3tuU1@mid.individual.net> <115f4t4$9dl$1@dont-email.me>

Show all headers | View raw

Marco Moock <mm@dorfdsl.de> wrote:
>Am 10.08.26 um 10:38 schrieb Andy Burns:
>>MikeS wrote:
>>>On 10/08/2026 07:54, Andy Burns wrote:
>>>>Marco Moock wrote:
>>>>>schrieb Jo-Anne:

>>>>>>I'd prefer not to get my own domain and would be grateful for the 
>>>>>>names of reliable email providers that either allow one to send 
>>>>>>from a 3rd party address or offer 'Reply-To' a 3rd party address 
>>>>>>(or both, of course).

>>>>>Such mail will be rejected by certain large providers like MS or 
>>>>>Google because it lacks a DKIM signature from the sender domain and 
>>>>>does not pass SPF.

>>>>Most large email providers require SPF or DKIM, not both.

>>>>If jo-anne had her own domain, she could add an SPF record to include 
>>>>the provider's own SPF record (easier than maintaining her own list 
>>>>of their servers).

>>>How does jo-anne having her own domain enable her to send emails from 
>>>the university email address which she used until she left the 
>>>university?

>>By itself it doesn't, but if the 3rd party provider (or university) 
>>allows sending as a smarthost then there's nothing to stop her 
>>configuring SPF for it ... indeed sensibly she would have to.

>This will not affect the SPF result for the university domain.
>DKIM is also only accepted if the domain name in the From: headers 
>matches the DKIM record. The times when you could use any mail server to 
>send from any address are finally over.

If From is an actual mailbox used to identify the author, there is
nothing wrong with using it on messages sent via another network. That's
the proper use, if not the intended use, of From.

In these cases, the Sender header should be included to identify the
mailbox of the user with the actual account on the network. Where DKIM
is used to authenticate, then the header that should be included in
authentication is Sender, ignoring From.

An author prefering to use a foreign email address on From is not doing
anything wrong. DKIM authentication is not precluded. Just use Sender
and not From. If that's what the author wants, then set up
authentication to accomodate it.

It's been ridiculous all along to implement these protocols, pretending
to do the world a favor by authenticating, while failing to accomodate
perfectly ordinary uses of email. The Sender header has been there from
the beginning, for exactly this purpose.

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