MailFixIt

Titan Email email configuration guide

Titan Email: MX records not receiving mail

The domain does not route incoming mail to the active Titan Email service or the intended recipient has not been created.

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

Incoming mail is going to another provider, or the Titan domain and recipient are not active. Titan is also sold through hosting and domain resellers, so use the values shown for your own product.

Fix it

  1. Open Titan or the reseller’s email dashboard and confirm the exact custom domain, subscription, and recipient mailbox or alias.
  2. Copy the complete MX set shown for that domain.
  3. Publish it in the authoritative DNS zone.
  4. Remove old mailbox-provider MX records only if Titan should receive directly; preserve an intentional security gateway and fix its next hop instead.
  5. After cache expiry, inspect public MX and send a new message to an address that exists.

Common mistake

Registering the domain or buying hosting does not create a Titan mailbox. Mixing Titan MX records with a previous provider can make delivery intermittent.

What MailFixIt can check

MailFixIt can expose missing, mixed, or unexpected public MX. It cannot activate Titan or create recipients.

Use the DNS-change guide when public MX still includes a retired provider.

Frequently asked questions

What does MailFixIt check for Titan Email?

It can show public MX and provider conflicts. Titan or the reseller dashboard must confirm the active domain and recipient mailbox.

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: Titan Email official setup guidance.