# EML_MX: MX-record contact scan

- Module: EML. Internal e-mail subsystem (queue, dispatch, inbox)
- Severity: Info
- Impact: No impact. Bookkeeping only. Nobody is affected.
- Retry: Automatic. The platform retries or self-heals on its own.
- Reference: https://docs.bizkithub.com/en/system-codes/EML_MX

## What happened

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. No action needed. Review flagged contacts in Contacts and ask them for a working address if needed.

## Related codes

- EML_DISPO: Disposable e-mail domain list sync
- EML_BOUNCE: E-mail bounce or delivery failure detected
- EML_CLS_TICK: Inbound e-mail classification run summary
- EML_DAEMON_TICK: Outbound e-mail sender run summary
- EML_RX_CROSSORG: Reply linked to an issue in a different organisation
- EML_RX_QUOTEHIT: Inbound e-mail carries our tracking pixel but was NOT short-circuited
