Verify a MailPace transactional sending domain
Complete MailPace DKIM ownership verification and prepare domain-scoped credentials without treating the service as a bulk-marketing relay.
Reviewed
MailPace is a transactional-email service with HTTPS/SMTP sending and an inbound feature. Its introduction explicitly prohibits marketing emails, bulk newsletters, and other non-transactional content.
Establish sending readiness
- Add the application domain and publish the DKIM ownership records supplied by MailPace.
- Confirm verification before attempting a production send.
- Select the documented API/domain credential or SMTP setup appropriate to your client.
- Store the secret server-side and record which domain/environment it authorizes.
Optional SPF/DMARC configuration should follow MailPace’s current verification instructions and your domain policy. Do not create conflicting SPF records or change employee-mail MX merely to authenticate outbound sending.
Verify the supported workload
Send one approved transactional message and inspect provider/recipient evidence. MailPace’s documented recipient/batching limits are not permission to use a transactional connection for a newsletter.
If ownership remains pending, inspect the exact DKIM names at authoritative DNS rather than regenerating credentials. If receiving is also needed, follow the separate inbound subdomain setup in this section; sending verification alone does not point incoming mail at your app.
MailKite has independent verification/credential requirements. Do not treat a MailPace domain key as a generic token usable with another service’s SDK.