Configure a CloudMailin receiving address and endpoint

CloudMailin’s core receiving path turns incoming mail into an HTTP POST. Begin with a generated receiving address or a dedicated custom-domain setup rather than replacing a staff-mail domain’s MX records as a first test.

Establish the receiving chain

1. Create/select the incoming address in the correct CloudMailin account.
2. Choose the destination HTTPS URL and apply the current HTTP-post security guidance.
3. Select the intended normalized JSON/multipart or raw format before writing the parser.
4. Configure custom-domain DNS/forwarding only according to the provider’s instructions and your approved routing plan.

The endpoint authentication protects the HTTP delivery path. It does not make the original sender’s email address or content inherently trustworthy.

Verify the actual address

Send one controlled message to the configured incoming address and confirm receipt at the intended endpoint. Check provider delivery status and the handler’s durable outcome, not just whether a form-shaped request can reach the server.

If receipt succeeds but HTTP forwarding fails, investigate target authentication, status responses, network reachability, and payload limits before changing DNS again.

CloudMailin Outbound has separate credentials and sending-domain setup. MailKite is another receiving/sending service with its own signature and domain model; neither connection is created merely by adding a CloudMailin address.

Source: CloudMailin getting started and receiving documentation.