By default MX Routing on accounts chooses "Automatic" and goes based off the MX record of the domain.
If said domain has no MX record RFC 5321 Section 5.1 states:
...
If an empty list of MXs is returned,
the address is treated as if it was associated with an implicit MX
RR, with a preference of 0, pointing to that host.
...
In this case, none of the four options in MX routing are toggled and mail simply fails to be accepted:
550-The mail server could not deliver mail to [email protected]. The
550-account or domain may not exist, they may be blacklisted, or missing the
550-proper dns entries.
MX Routing should fall back to making its' routing decision based on A/AAAA if no MX RR are available.
This is on cPanel version 78.0.18
P.S I know theres some opinions on whether or not "fallback" to non MX should be in place "today" but we should adhere to RFC's as much as possible.
EDIT: Workaround is to manually set the MX routing, at which point mail will work properly either locally or externally.
If said domain has no MX record RFC 5321 Section 5.1 states:
...
If an empty list of MXs is returned,
the address is treated as if it was associated with an implicit MX
RR, with a preference of 0, pointing to that host.
...
In this case, none of the four options in MX routing are toggled and mail simply fails to be accepted:
550-The mail server could not deliver mail to [email protected]. The
550-account or domain may not exist, they may be blacklisted, or missing the
550-proper dns entries.
MX Routing should fall back to making its' routing decision based on A/AAAA if no MX RR are available.
This is on cPanel version 78.0.18
P.S I know theres some opinions on whether or not "fallback" to non MX should be in place "today" but we should adhere to RFC's as much as possible.
EDIT: Workaround is to manually set the MX routing, at which point mail will work properly either locally or externally.
Last edited: