Connect Amazon SES to MorphyMail with the right expectations
Follow the correct path from verified domain and production access to regional SMTP credentials—without outdated quota promises or inbox guarantees.
AWS pricing, quotas, and approval are controlled by Amazon and can change by region and account.
Low pay-as-you-go cost with account-specific sending quotas
Amazon SES currently lists outbound email at $0.10 per 1,000 messages, before applicable data, dedicated-IP, or other charges. That is approximately $1 per 10,000 outbound messages—not a flat promise for every setup.
Pay for usage
SES charges by messages, data, and optional features rather than a MorphyMail contact tier.
Verify identity
Verify an email identity or domain and publish the authentication records AWS provides.
Request production access
New accounts begin in the SES sandbox. Submit your sending use case and request production access.
Create SMTP credentials
Generate region-specific SMTP credentials in the SES console; they differ from ordinary AWS access keys.
Add to MorphyMail
Enter server, port, username, password, and TLS settings in MorphyMail, then test.
Protect reputation
Send expected mail, manage bounces/complaints, authenticate the domain, and increase volume gradually.
From AWS account to first controlled send
1. Choose your AWS Region
SES identities, sandbox status, endpoints, and SMTP credentials are regional. Keep all settings in the same region.
2. Verify your sending domain
Add the DNS records supplied by SES, including DKIM records. Configure SPF and DMARC as appropriate for the domain.
3. Request production access
Explain the mail type, recipient acquisition, complaint and bounce handling, and unsubscribe process. Approval and quotas are determined by AWS.
4. Create SES SMTP credentials
Copy the SMTP endpoint, port, generated username, and password. Store credentials securely.
5. Test with MorphyMail
Add the credentials under SMTP settings, enable TLS, test with a small expected-recipient list, and increase volume gradually.
Use-policy note: SES is designed for legitimate transactional and permission-based email. Purchased or extracted lists can create complaint and suspension risk. No software or SMTP can guarantee inbox placement.
Use Amazon SES when
- You have a legitimate, documented sending use case
- You can authenticate your own domain
- You actively process bounces and complaints
- Your recipients expect the email
Choose another route when
- Your list source violates the provider’s policies
- You need managed infrastructure and hands-on setup
- You cannot maintain authentication or reputation
- Your use case is cold outreach rather than opt-in bulk mail
Need the software before configuring SES?
Choose the MorphyMail product that fits your workflow, then connect approved SES SMTP credentials.
