public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@gentoo.tnetconsulting.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fully-Defined-Domain-Name for nullmailer
Date: Wed, 13 Apr 2022 07:40:18 -0600	[thread overview]
Message-ID: <f6781668-8efa-5b67-cd61-a7c29ec6b0c8@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <6fa02784-588e-c137-7422-ae81c535453d@web.de>

On 4/13/22 6:31 AM, n952162 wrote:
> Unfortunately, I get a 550 from my network provider for all of these:
> 
>  1. me
>  2. localdomain
>  3. net
>  4. web.de
> 
> So, how does thunderbird do it?

I don't know what name Thunderbird uses in it's HELO / EHLO command(s). 
Though it shouldn't matter much which name is used.

The important thing should be that the SMTP client, be it Thunderbird or 
nullmailer or something else, should authenticate to the outbound relay 
/ MSA.  The MSA should then use that authentication as a control for 
what is and is not allowed to be relayed.

Nominally, the name used has little effect on the SMTP session.  However 
there is more and more sanity checking being applied for server to 
server SMTP connections.  Mostly the sanity checking is around that a 
sender isn't obviously lying or trying to get around security checks. 
These attempts usually take the form of pretending to be the destination 
or another known / easily identifiable lie.

Mail servers that send server to server traffic actually SHOULD use 
proper names that validate.  Clients shouldn't need to adhere to as high 
a standard.  I consider nullmailer to be a client in this case.



-- 
Grant. . . .
unix || die


  reply	other threads:[~2022-04-13 13:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  9:53 [gentoo-user] Fully-Defined-Domain-Name for nullmailer n952162
2022-04-13 12:31 ` n952162
2022-04-13 13:40   ` Grant Taylor [this message]
2022-04-13 15:25     ` n952162

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f6781668-8efa-5b67-cd61-a7c29ec6b0c8@spamtrap.tnetconsulting.net \
    --to=gtaylor@gentoo.tnetconsulting.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox