Amazon SES SMTP能否像Google SMTP一样向未验证地址发邮件？

Hey there! Let me break down how Amazon SES handles sending to unverified addresses, since it operates a bit differently from Google's SMTP service.

First, the Default SES Restriction #

When you first sign up for Amazon SES, your account is placed in the sandbox environment. This is a core security measure to prevent spam, and it enforces two non-negotiable limits:

• You can only send emails to verified email addresses or domains (either your own test addresses or recipients who’ve explicitly opted in and verified their identities)
• You can only send from verified email addresses or domains

This is exactly why you’re unable to send to unverified addresses right now—your account is still in sandbox mode.

How to Send to Any Address with SES #

Yes, SES does support sending to arbitrary, unverified addresses—but you need to get your account out of the sandbox first by requesting Production Access. Here’s the step-by-step process:

1. Verify your sending identity: Before applying, make sure you’ve verified the email address or domain you plan to send from (this is a prerequisite for the request)
2. Submit a production access request: In the Amazon SES console, head to the "Account Dashboard" and look for the option to request production access. You’ll need to provide details like:
   • Your specific use case (e.g., transactional order confirmations, opt-in marketing newsletters, customer support alerts)
   • Estimated monthly sending volume
   • How you’ll handle bounces and complaints (critical for keeping a healthy sender reputation)
   • Your process for managing recipient opt-ins (if sending marketing emails)
3. Wait for approval: Amazon reviews these requests to ensure you’re following email best practices and anti-spam guidelines. Once approved, your account moves to production mode, and you can send to any valid email address (as long as you stay compliant with SES policies).

Quick Comparison to Google SMTP #

Google’s SMTP (like Gmail’s) doesn’t have a sandbox-style restriction on recipient verification by default, but it does have strict sending limits (e.g., 500 emails/day for regular Gmail accounts) and will flag or block your account if it detects spam-like behavior. SES is built for scalable, professional email sending, so its initial sandbox restriction is a way to ensure new users don’t accidentally send spam and damage their own sender reputation (and AWS’s overall email deliverability standing).

Important Notes Post-Approval #

Even in production mode, you still need to:

• Keep bounce and complaint rates low (SES will throttle or suspend your account if these metrics exceed acceptable thresholds)
• Include a clear, functional unsubscribe link in all marketing emails
• Follow global anti-spam laws (like CAN-SPAM or GDPR)

内容的提问来源于stack exchange，提问作者user196711