Amazon SES is one of the cleaner smarthost options for cPanel servers that need to fix outbound reputation. The IPs are reputable, the cost is modest, the API is stable, and Amazon handles bounce processing well. The catch is that SES rewrites the envelope sender by default and that breaks DMARC alignment unless you configure custom MAIL FROM domains. Several other quirks — sandbox mode, region selection, signature versions — trip first-time setups.
What’s happening
Amazon SES accepts SMTP submission on port 587 (or 465) at endpoints like email-smtp.us-east-1.amazonaws.com. You authenticate with an IAM-derived SMTP credential. SES delivers from its own pool of IPs and signs with its own DKIM by default, which gives you the DKIM that aligns to amazonses.com — not your domain. To get DMARC alignment, you must configure a verified custom DKIM domain in SES (the CNAME trick) and set a custom MAIL FROM that’s a subdomain of your sender.
How to verify
After signing up for SES and creating an SMTP credential, test the relay manually:
openssl s_client -starttls smtp -connect email-smtp.us-east-1.amazonaws.com:587 -crlf
EHLO test.example.com
AUTH LOGIN
[base64 username]
[base64 password]
MAIL FROM: <sender@example.com>
RCPT TO: <test@destination.com>
DATA
...
.
A 250 Ok response means authentication and routing work.
The fix
- Verify your domain in SES under “Verified identities.” This publishes three CNAME records — your DKIM selectors. Add them to your DNS (cPanel DNS Zone Editor or external provider).
- Configure a custom MAIL FROM domain in SES for the verified identity. Pick something like
bounces.example.comand publish the MX and TXT records SES generates. This makes the envelope sender align with your domain, fixing SPF alignment. - Update your SPF to include SES with
include:amazonses.com(or the regional variant). Confirm the lookup count stays under 10. - Wire SES as the smarthost in Exim (WHM > Exim Configuration Manager > Basic Editor). Use the SES SMTP endpoint, port 587 with STARTTLS, and the IAM-derived SMTP credentials.
- Request production access in SES if you’re still in the sandbox. Sandbox mode limits sends to verified-only recipients. The unsandbox request typically takes 24 hours and asks about your use case and bounce-handling.
- Wire SES feedback into your bounce processing. Bounce notifications come back to the MAIL FROM domain — handle them, suppress hard-bounced recipients, or pipe them into the cPanel user’s mailbox for visibility.
For environments where reputation has been damaged and SES is the recovery path, Stack Harbor handles the SES wiring, the DKIM/MAIL FROM setup, and the bounce processing under deployment management.