Verify your sending domain

MailingPlatform sends your email through your own Amazon SES account. That gives you wholesale sending prices and a sender reputation you own, but it means two setup steps before you can send: verify your domain in Amazon SES, and connect SES to MailingPlatform.

1. Verify your domain in Amazon SES

1. Sign in to the AWS console and open Amazon SES in the region you want to send from
2. Under verified identities, add your domain (for example yourstore.com)
3. SES gives you DNS records, including DKIM records - add them at your DNS provider (Cloudflare, One.com, GoDaddy or wherever your domain is managed)
4. Wait for the identity to show as Verified (usually minutes, up to 24 hours)

New SES accounts start in sandbox mode with low limits; request production access in the SES console so you can send to real subscribers.

2. Create AWS credentials

MailingPlatform needs an access key to send on your behalf:

1. In AWS, open IAM and create a user for MailingPlatform
2. Attach the AmazonSESFullAccess and AmazonSNSFullAccess policies (SNS is used for bounce and complaint notifications)
3. Create an access key and copy both the access key ID and the secret access key

The Settings page has a built-in walkthrough ("How to get your AWS credentials") with the exact clicks.

3. Connect it in MailingPlatform

1. Go to Settings and find AWS SES configuration
2. Enter the AWS access key ID, secret access key and AWS region
3. Enter your verified domain in SES - this becomes your sending domain
4. Save

4. Set up a tracking domain

Still in Settings, configure a tracking domain (a subdomain like track.yourstore.com with a DNS record pointing to the platform). It is used for open and click tracking, unsubscribe links, the website tracking script, and images in your emails (uploaded assets and remote images copied at send time), so all links and images stay under your own brand.

What this means for your sending

• Campaign and automation emails are sent from addresses on your verified domain (for example hello@yourstore.com)
• Each email list has optional sender settings (name and address prefix); steps without an explicit sender fall back to those, then to noreply@your-domain
• Emails signed with your DKIM keys build your domain's reputation with every send
• Bounces and spam complaints are handled for you: when you save your credentials, the platform connects your SES identities to a notification topic, records every bounce and complaint against the campaign, suppresses the address, and turns off SES's own "email feedback forwarding" so you do not receive raw delivery failure reports in your inbox. This covers your domain and any email address under it that you have verified separately in SES. A daily check repairs the setup if anything changes on the AWS side.

If you want to understand what SPF, DKIM and DMARC actually do, read the plain-language guide: SPF, DKIM and DMARC explained simply. To see what Gmail, Yahoo and Outlook require once you send in volume, read Gmail and Yahoo sender requirements.