MailFixIt

STRATO Mail email configuration guide

STRATO Mail: MX records not receiving mail

The domain is not routing incoming mail to the STRATO service configured for its existing recipient addresses.

Problem description

A provider setup symptom may look like:

MX records not receiving mail after a provider DNS change.

Check the sending domain

What this usually means

The domain’s public mail route does not match its STRATO mail configuration, or the destination mailbox does not exist. STRATO can also be configured to use an external mail server, so registration at STRATO alone does not prove STRATO should receive mail.

Fix it

  1. In the STRATO customer area, confirm the domain’s selected mail-server mode and create every required mailbox or alias.
  2. If STRATO Mail should receive directly, use the MX configuration currently shown for that domain and product.
  3. If an external provider or security gateway should receive, keep that intended MX route and configure its next hop.
  4. Remove stale MX records only after confirming they belong to a retired mail path.
  5. After cache expiry, inspect public MX and send a new message to an existing recipient.

Common mistake

Mixing STRATO and external-provider MX records does not provide safe redundancy; it can route mail unpredictably to systems with different recipient lists.

What MailFixIt can check

MailFixIt can expose missing, mixed, or unexpected public MX records. It cannot create or inspect STRATO mailboxes.

Use the DNS-change guide when the domain still advertises a previous provider.

Frequently asked questions

What does MailFixIt check for STRATO Mail?

It can show public MX records and conflicts. STRATO must confirm the domain mail mode and that each destination mailbox or alias exists.

Should I replace every existing DNS record with the provider values?

No. Confirm the exact record type and owner, preserve unrelated legitimate services, and change only the provider-controlled record required for the intended mail route.

Related email diagnostics

Email delivery delayed or rejected after a DNS migrationDiagnose email that stopped arriving after a DNS change. Compare public MX records with the intended provider and avoid false alarms for mail gateways. SPF is not configured for the envelope sender domainDiagnose SPF missing on a bounce or MAIL FROM subdomain. Check the exact envelope domain, add only authorized senders, and verify safely. DKIM public key record is invalid or revokedDiagnose an invalid or revoked DKIM public key record. Check the exact DKIM selector in public DNS before replacing a sender-provided key.

Primary sources: STRATO Mail official setup guidance.