Platform capability · Email Sender & Deliverability
DKIM signing, SPF and DMARC checks and bounce suppression for each customer
Each customer has its own sender identity, set in the operator console: From address, reply-to address and display name. Mail goes through the platform’s notification service to a transactional email provider (for example Amazon SES, SendGrid or Postmark). The platform generates a DKIM key pair for each sending domain, checks SPF and DMARC against live DNS, and signs outgoing mail when the From domain is verified. Bounce and complaint reports from SES, SendGrid and Postmark go into a suppression list for each customer, which is checked on every send.
Register each sending domain in the operator console. The platform generates a DKIM key pair and the DKIM, SPF and DMARC DNS records to publish. It checks DNS again on request and signs mail sent from verified domains. Operators can rotate keys, and the previous key stays active during the change.
Set up each email provider’s webhook with the shared secret, and bounce and complaint reports go into a suppression list for each customer automatically. Hard bounces and spam complaints are added. Soft and temporary bounces are reported and are not suppressed. Every send is checked against the list before the message is handed over for delivery, so an address that complained is not mailed again. Operators can browse, filter, search, add and remove suppressions in the operator console.
Two items remain. The first is scheduled IP warm-up: a gradual increase in daily volume on a new IP address. The second is reputation dashboards for each domain: bounce, complaint, open and click rates over time. Both need real sending volumes to be useful, and they follow the parts described above.
Additions that extend the capability described above.
A solution architect will demo the live service against your domain model.