BizKitHub
EML_MX

MX-record contact scan

InfoEMLRetry: automatic
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.

When it is logged

  • The periodic scan flagged contacts whose e-mail domain publishes no mail server (MX) record.
  • Previously flagged contacts were cleared after their domain started accepting mail.

What to do

  1. 1

    No action needed. Review flagged contacts in Contacts and ask them for a working address if needed.

Where you will see it

The code tags entries in the admin Log viewer, where you can filter by it and open individual occurrences. Codes logged as error or critical can also trigger a technical notification e-mail with the code in the subject:

Notification subject
[EML_MX] [eml] …