Solve MX issues

wikipedia.org:
https://en.wikipedia.org/wiki/MX_record

Common failures:

  • The domain name itself is in MX: Eg the shared hosting server has a different SSL certificate. E-mail processes ignore this problem;
  • Even if a mail service is set up for the server, SPF can also authorize mail from the server itself;
  • For ‘www.’ MX can be set up like ‘0 .’. Otherwise, A/AAAA values are used. For explanation, see Proposed Standard ‘Null MX’ in RFC 7505.

Note on October 1, 2020:
Control panels DirectAdmin and CPanel refuse MX ‘0.’ setup.
If ‘Null MX’ is used, it also blocks sending via SMTP.

MTA Exim responds correctly to ‘Null MX’ in this way:
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
janwillem@www.webhostingtech.nl
an MX or SRV record indicated no SMTP service.

MTA Postfix (probably this MTA) responds with:
janwillem@www.webhostingtech.nl: Domain www.webhostingtech.nl does not accept mail (nullMX)