Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsTo receive email in an application with SendGrid, configure Inbound Parse: route a dedicated hostname’s MX record to SendGrid, point its parse setting at a publicly reachable webhook, and have that endpoint accept SendGrid’s multipart/form-data POST. Verify the webhook request, preserve the original body when signature validation is used, and return a 2xx response only after your application has durably accepted the message.
What you need before configuring Inbound Parse
- A hostname associated with an authenticated domain and dedicated to receiving messages for parsing.
- A stable, publicly reachable webhook URL. Use the final HTTPS endpoint directly: SendGrid does not follow redirects.
- An application endpoint that can accept multipart/form-data and store or queue messages and attachments safely.
SendGrid’s configuration requires the receiving hostname and destination URL to be set in the console or through its API. See Create a parse setting for the API option.
Configure DNS and the parse webhook
- Choose a dedicated receiving hostname. For example, use a hostname such as
parse.example.comrather than changing the MX routing for a domain that already handles ordinary mail. SendGrid warns that using the same hostname as an authenticated domain with Automatic Security enabled can create an infinite mail-routing loop. Follow the setup guide’s guidance for the domain and hostname association: Configure the inbound parse webhook. - Create the MX record at your DNS provider. Set the receiving hostname’s mail server to
mx.sendgrid.net. SendGrid’s example uses priority10; that is the example value, not a universal DNS requirement. Check whether your DNS provider automatically appends the domain name. If it does, entering the full hostname without a trailing period can accidentally create a duplicated name such asparse.example.com.example.com. - Set the parse destination. In the SendGrid console or API, associate the receiving hostname with your webhook URL. Use the final endpoint rather than a URL that redirects.
- Do not change the MX record after setup. SendGrid warns that changing it can stop that hostname from receiving email.
Choose parsed fields or raw MIME
Decide how much of the original message your application needs before choosing the payload mode. The default parsed format exposes useful fields such as raw headers, DKIM results, sender and recipient information, text and HTML body forms, envelope data, and attachment content identifiers. The POST raw/full MIME option instead delivers the complete MIME message for applications that need to process the original message structure. SendGrid describes these options in its setup guide.
Do not assume that reading only URL-encoded content will capture attachments. In the default mode, SendGrid says the message is URL encoded but attachments are not; your handler must correctly process the multipart request and attachment fields or use raw MIME processing when that better fits your parser.
#1 Best Overall
Accept multipart data without breaking verification
Inbound Parse sends a multipart/form-data POST. If you enable signature validation, verify against the original raw request body. Configure your server so middleware does not parse, transform, or consume the body before the verifier receives it; otherwise the data used for verification may no longer match the request as sent. SendGrid documents the security approaches and verification requirements in Securing your Inbound Parse Webhooks.
For signature verification, store the provided public key and validate the signature and timestamp headers. SendGrid also documents OAuth verification and a hybrid approach. Its security policy must include signature verification or OAuth; the policy API is described in Create a Parse Webhook security policy.
Rank #2
Process messages reliably and safely
Persist before acknowledging
Send a 2xx response once your application has durably accepted the message, for example by storing it or placing it on a processing queue. Avoid acknowledging first and then doing fragile background work without a durable handoff. SendGrid retries unsuccessful POST deliveries; its documentation says messages that remain undeliverable after three days are dropped without advance notification. Monitor webhook failures and your own queue or storage path rather than relying on retries as a substitute for application-side recovery. See the Inbound Email Parse Webhook documentation.
Enforce size and encoding limits
SendGrid documents a 30 MB total message limit, including attachments. Other mail handlers, ISPs, or companies involved in delivery may impose lower limits or restrict attachment types. The guide also notes that selected headers are decoded and converted to UTF-8, while fields may expose character-set metadata for other encodings; do not assume every message body part is UTF-8.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Treat message content as untrusted
Webhook authentication establishes that a request meets the configured signature or OAuth policy; it does not make the email body or attachments safe to render, execute, or trust. Apply your application’s normal validation and safe handling to both message content and files.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Test the complete delivery path
- Send a message from an email account to an address on the configured receiving hostname. The local part must not be
abuse,postmaster, orunsubscribe. - Confirm that DNS resolves to the intended MX target and that the SendGrid parse configuration points to the correct webhook URL.
- Check application logs for the multipart POST, parsed fields or raw MIME as configured, and any attachments you expect to receive.
- Verify signature or OAuth validation if enabled, and confirm that the endpoint returns a 2xx response after durable acceptance.
- Check monitoring and queue or storage records for failures, retries, or dropped processing work.
SendGrid’s setup guide recommends testing by sending a message to the configured receiving domain. The checks above help distinguish a DNS or configuration problem from a body-parsing, authentication, or downstream-processing issue.
Quick Recap
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
