MailFixIt

SendGrid email configuration guide

SendGrid Inbound Parse: MX record not receiving mail

SendGrid MX is for Inbound Parse on a chosen hostname; ordinary outbound SendGrid delivery does not require an MX record.

Problem description

A provider setup symptom may look like:

Messages sent to the Inbound Parse hostname do not reach the configured webhook.

Check the sending domain

What this usually means

Inbound Parse is not receiving mail because the chosen hostname does not route to SendGrid, the host is not configured in SendGrid, or SendGrid cannot post to the webhook. This feature is separate from outbound sending.

Fix it

  1. Choose the exact domain or subdomain dedicated to Inbound Parse and authenticate it as SendGrid requires.
  2. Configure that same receiving host and the final HTTPS webhook URL under Settings → Inbound Parse.
  3. Publish its MX record to the current SendGrid Inbound Parse target and remove competing MX records from that dedicated hostname.
  4. Do not replace your normal business-domain MX unless Inbound Parse is intentionally meant to receive all employee mail.
  5. Send a message to the dedicated hostname, then check SendGrid activity and the webhook server logs.
  6. Make the webhook return a successful response without relying on an HTTP redirect, which Inbound Parse does not follow.

Common mistake

An MX record for parse.example.com receives mail addressed to that subdomain, not [email protected]. DNS can be correct while the webhook path still fails.

What MailFixIt can check

MailFixIt can expose the public MX route and conflicts. It cannot validate the SendGrid host-to-webhook mapping or application response.

Use the related MX guide if the dedicated hostname still resolves to an old provider.

Frequently asked questions

What does MailFixIt check for SendGrid?

It can show whether the selected hostname publicly routes to SendGrid and whether another MX conflicts. It cannot inspect or call the private webhook configuration.

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: Twilio SendGrid Inbound Parse setup.