Receive MailPace mail on an inbound subdomain
Use MailPace's documented CNAME receiving setup and JSON callback, with bounded retries and explicit attachment/message handling.
Reviewed
MailPace’s inbound guide documents a receiving subdomain and CNAME setup, not a generic instruction to replace your main domain’s MX records. The domain must pass DKIM verification and have the required active plan.
Configure the receiving destination
- Select the intended inbound subdomain in the domain’s Inbound Emails settings.
- Publish the exact CNAME instruction provided there, pointing the chosen subdomain at the provider’s inbound service.
- Configure a public HTTPS endpoint and implement the documented source-protection/payload handling.
- Preserve
messageId, relevant headers, optional text/HTML, and attachment information needed by the application.
The JSON payload can also include the full raw email. Do not assume every optional body or recipient property is present, and limit raw/attachment storage according to your retention policy.
Design for bounded retries
Persist accepted work before returning success. MailPace documents a bounded retry sequence and queued/success/retrying/failed states; monitor failed deliveries rather than assuming infinite retries.
Test a controlled message at the actual receiving subdomain, duplicate delivery, and a temporary failure. Keep sender-controlled mail content out of privileged agent instructions.
Do not invent a MailKite signature on this payload. If changing receiving providers, update DNS, endpoint verification, and payload mapping together. A MailPace incoming messageId is not automatically a MailKite event identity.