EML_MX
MX-record contact scan
The low-priority sweep that cross-checks every contact e-mail domain against the crawler DNS cache: flags contacts whose domain has been DNS-resolved but exposes no active MX record, and reverses the flag when the domain later publishes MX. Known-good mailbox providers (gmail.com, seznam.cz, outlook.com, …) are always skipped from the check and auto-recovered if previously flagged. Every no-MX detection also pulls the domain's next DNS re-check back to now, so a transient upstream failure gets a fresh chance at recovery on the next syncDnsRecords tick. Info entries summarise flagged / recovered counts; warning entries mean the reason registry was missing an expected code.
What this code means
The low-priority sweep that cross-checks every contact e-mail domain against the crawler DNS cache: flags contacts whose domain has been DNS-resolved but exposes no active MX record, and reverses the flag when the domain later publishes MX. Known-good mailbox providers (gmail.com, seznam.cz, outlook.com, …) are always skipped from the check and auto-recovered if previously flagged. Every no-MX detection also pulls the domain's next DNS re-check back to now, so a transient upstream failure gets a fresh chance at recovery on the next syncDnsRecords tick. Info entries summarise flagged / recovered counts; warning entries mean the reason registry was missing an expected code.
Where you will see it
- In the subject line of technical-notification e-mails — for example
[EML_MX] [emlHealthcheck] … - As a badge in the admin log viewer at
/log, where you can filter and drill into individual entries. - In the
core__system_logtable, stored against the code id fromcore__system_log_code.