Never had an issue. As long as there is a PTR record for the sending IP, mail will usually flow. Think of a single server sending for multiple domains.
And of course, when you start to configure SPF etc, you would have to take into account the sending mail server/domain.
But the HELO/EHLO doesn't have to match the users domain. It just have to have an IP with a PTR which matches.
here some test and strange behavior of my UTM
"WorkUTM" has 2 UPLINK
Receives emails from both, but sends only from one (defined with mulipath rule). Second WAN not published in any DNS records etc.
HOW I tested sending emails to second IP? Simple, defined the mail.hostname.com with the second ip in my "homeUTM"
But my "HomeUTM" doesnt accept emails from my "WorkUTM" with the primary WAN-IP
[79.x.x.x]: 550 Invalid RDNS entry for 80.x.x.x
Tried to define the mail.hostname.com (work) with two IP, without success
You know so much, Olsi, that I didn't think of this. Like Louis said, you only need to make sure your authoritative name server entries tell the full story:
mail1.hostname.com A 22.33.44.55 <-- EDIT 2018-02-22 Corrected mail2 to mail1
55.44.33.22.in-addr.arpa ptr mail1.hostname.com
mail2.hostname.com A 22.33.44.56
56.44.33.22.in-addr.arpa ptr mail2.hostname.com
v=spf1 ip4:22.33.44.55 ip4:22.33.44.56 -all
Cheers - Bob
There can be very many domains hosted behind a single HELO string. There must be tens of thousands behind mail-cys01nam02on0094.outbound.protection.outlook.com and the other servers for Office 365.
Cheers - Bob
I don't think that there's an RFC requirement that there be a different SMTP banner for different IPs or for different domains. I can see that a hosting provider might not be set up like outlook.com and would want to offer customized SMTP banners for its customers.
Cheers - Bob