How to connect
Amazon SES.
Use an SES SMTP endpoint, matching regional credentials, and a verified sending identity.
Connection preview. You can read this guide and save a mailbox for later. Live authorization and warm-up remain off. Do not enter real credentials while the connection form is disabled.
Before you start
- A verified sending identity in the AWS Region you will use.
- SES SMTP credentials for that same Region.
- SES production access for that Region before sending to unverified recipients.
Step-by-step setup
Check the SES Region and sending access
Open SES in the Region for your sending identity. Sandbox accounts can send only to verified recipients and simulator addresses; do not use that restriction as a warm-up workaround.
Obtain regional SMTP credentials
Use SES SMTP settings to obtain credentials for the chosen Region. Your SMTP password is not your AWS secret access key. Copy the endpoint shown in SES rather than guessing a regional hostname.
Choose Other provider in MailboxWarm
Open Mailboxes → Add mailbox, choose Other provider, and enter your sending email address. Named SMTP services all use this same Other provider connection option.
Enter the connection details
When connections are enabled, enter the SMTP values listed below. Choose Test & connect. MailboxWarm checks authentication and the encrypted connection without sending a message.
Connection settings
Match these values to the fields in MailboxWarm. Keep passwords and keys private.
- Connection option
- Other provider
- SMTP host
- The SMTP endpoint shown in your SES Region
- Encryption / port
- STARTTLS / 587
- SMTP username
- Regional SES SMTP username
- SMTP password
- Regional SES SMTP password
SMTP sends; it does not read your inbox. This connection does not include IMAP access to your mailbox. Placement and rescue activity concern the controlled seed inboxes receiving warm-up messages. Provider-specific compatibility still needs live validation.
Check the result
In today’s preview, expect Mailbox saved for later. When connections are enabled, a successful check shows Mailbox connected, with warming still paused. A failed connection check is not proof of delivery or a reason to add the same mailbox again.
Once live warming is available, choose the mailbox’s plan and schedule before starting. Connecting alone does not begin warm-up, and your provider’s sending limits still apply.
Open setup previewTroubleshooting
Authentication fails
Check that the SMTP credentials and endpoint belong to the same Region. Do not paste AWS console credentials or a raw secret access key.
Sending is restricted
Check the sending identity, sandbox status, quotas, and account health in that Region. MailboxWarm cannot lift AWS account restrictions.
Provider resources
Provider menus and account policies can change. Use their official documentation for the latest requirements.
- AWS: obtaining SMTP credentials (opens in a new tab)
- AWS: SMTP encryption and ports (opens in a new tab)
- AWS: SES sandbox restrictions (opens in a new tab)
Settings reviewed September 12, 2026 · Documentation review, not a live connection test.