- Newest
- Most votes
- Most comments
1.- If almost in its entirety you should use all the parameters and SSL (I would recommend it).
2.- Yes, you have to fill in all the SMPT, host port and SSL data (AWS provides you with this information in the console). There are no queues for mass submissions, the API supports a large number of calls. What if AWS manages two types of sandbox and production, sandbox is like a test environment that allows you to send emails not so massively, instead production yes.
https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html
3.- It would be good if you activate the SES suppression list.
I'll tell you quickly, after sending an email you could find that it bounces or that they place it as SPAM.
By having these results, the use of the SES service and your entire account may be affected because when sending emails you will have a reputation and when you pass 5%, they can delete your entire AWS account. So, when you use the SES service, in the configuration you can also choose the "configuration set" that are a configuration when sending the emails, that configuration you can indicate if you want the logs (all the states that your email goes through whether it is sent, received, opened, bounced, spam, etc) to register with cloudwatch. You could also configure the suppression list, you have the option of rebounding and/or spam. This means that when you send an email, and this email falls into one of these states, AWS SES automatically registers that email in a suppression list, which in the next sending, you will send the email but AWS SES will not resend it to the destination mail servers (so as not to increase a bad reputation).
Relevant content
- asked a year ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago