Tutorial · Published 26 August 2026
Deploying a recipient domain on Ruzayo safely
A production checklist for tenant credentials, DNS verification, MX cutover, signed webhook validation, mailbox testing, and rollback.
Prepare authority and rollback
Create a dedicated tenant credential, register the domain, and inventory the current MX, SPF, DKIM, and DMARC records before changing DNS. Define who can approve cutover and how the prior route will be restored.
Use a low-TTL rehearsal window only when it fits the domain’s operational policy; do not assume DNS changes are instant.
Verify before cutover
Complete the ownership challenge and check each required record from more than one resolver. Create a bounded test mailbox and configure a webhook endpoint that stores the raw request bytes before verification.
Reject any event whose signature, timestamp, audience, or replay identity is invalid.
Cut over and observe SMTP
Publish the Ruzayo MX and monitor DNS propagation, SMTP acceptance, LMTP delivery, durable message state, and webhook acknowledgement. Send controlled tests from multiple independent mail systems and retain their message IDs.
Do not declare success from a 250 response alone; open the authoritative mailbox record and verify raw source plus normalized fields.
Exercise export and rollback
Export the test mailbox, rotate its credential, replay one event, and prove the consumer remains idempotent. Then rehearse restoration of the previous MX without deleting Ruzayo data.
Billing disclosures must remain explicit: the published meter is not running until the implementation and invoices exist.
Production checklist
- Verify Direct recipient MX against the deployed environment, not a screenshot.
- Verify Tenant-scoped authority against the deployed environment, not a screenshot.
- Verify Signed webhooks against the deployed environment, not a screenshot.
- Verify Exit remains possible against the deployed environment, not a screenshot.