Evening All,
I have a server named gateway.virtruenterprise.com. It had an A record,
no MX record that Yahoo! claimed it could not deliver email to the system.
Specifically, I setup a local user called gateway and emailed gateway@
without issue from cloud providers Microsoft Live, AOL, Gmail as well as
systems using local domains including Sendmail and Exchange.
So I was very surprised that Yahoo! wouldn't deliver a test email.
Sorry, we were unable to deliver your message to the following address.
<gateway(at)gateway.virtruenterprise.com>:
No mx record found for domain=gateway.virtruenterprise.com
So the error is correct. There is no MX record for this.
However, under RFC 5321, section 5.1, I had always thought that without
an MX, the system should revert to using the A record as an implicit MX.
Is this just my misreading the RFC? It seems silly that I added a
"self-referencing" MX but yes, this worked to resolve the Yahoo! issue:
gateway.virtruenterprise.com. 3600 IN A 35.165.156.36
gateway.virtruenterprise.com. 3600 IN MX 0
gateway.virtruenterprise.com. ;Added because Yahoo! refused to use the
A record and wanted an MX
Feedback appreciated as I'd like to know if I'm doing something wrong,
Yahoo! is being stricter than others or ...
KAM
_______________________________________________
mailop mailing list
[email protected]
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
