1 |
On 4/13/22 6:31 AM, n952162 wrote: |
2 |
> Unfortunately, I get a 550 from my network provider for all of these: |
3 |
> |
4 |
> 1. me |
5 |
> 2. localdomain |
6 |
> 3. net |
7 |
> 4. web.de |
8 |
> |
9 |
> So, how does thunderbird do it? |
10 |
|
11 |
I don't know what name Thunderbird uses in it's HELO / EHLO command(s). |
12 |
Though it shouldn't matter much which name is used. |
13 |
|
14 |
The important thing should be that the SMTP client, be it Thunderbird or |
15 |
nullmailer or something else, should authenticate to the outbound relay |
16 |
/ MSA. The MSA should then use that authentication as a control for |
17 |
what is and is not allowed to be relayed. |
18 |
|
19 |
Nominally, the name used has little effect on the SMTP session. However |
20 |
there is more and more sanity checking being applied for server to |
21 |
server SMTP connections. Mostly the sanity checking is around that a |
22 |
sender isn't obviously lying or trying to get around security checks. |
23 |
These attempts usually take the form of pretending to be the destination |
24 |
or another known / easily identifiable lie. |
25 |
|
26 |
Mail servers that send server to server traffic actually SHOULD use |
27 |
proper names that validate. Clients shouldn't need to adhere to as high |
28 |
a standard. I consider nullmailer to be a client in this case. |
29 |
|
30 |
|
31 |
|
32 |
-- |
33 |
Grant. . . . |
34 |
unix || die |