- 최신
- 최다 투표
- 가장 많은 댓글
As per the documentation, there are SES service quotas that you need to look at:
If you're in using SES Sandbox environment, then you only get to send 200 emails per 24 hours period plus you can add maximum of 50 recipients per message. (Note: Recipients number is not adjustable). Please refer link {1 & 2}
Note: A recipient is any "To", "CC", or "BCC" address.
If you are using Sandbox environment then you need to upgrade to the production and can always initiate "request for production access" from SES console.
How to move from Sandbox to Production, please refer link {3}
There is another option of "Bulk email sending" where in programmatically you can send an email to several customers at the same time. (Note: Recipients number is not adjustable)
To know more:
{1} https://docs.aws.amazon.com/ses/latest/dg/quotas.html#quotas-email-sending
{2} https://docs.aws.amazon.com/ses/latest/dg/manage-sending-quotas.html
{3} https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html
Let me know If this helps.
Hi, Actually we have upgrade our limit to 100k daily. And even if AWS limit our sending to 200 daily, why did our sending only 136 emails per day? I mean our campaign only send out to 45 emails after 8 hours for 3 stages/daily. And its repeated for 6 days until all 800 emails finish sent out.
Example : 1am - send to 45 emails,
9am - send to another 45 emails,
5pm - send to another 45 emails
관련 콘텐츠
AWS 공식업데이트됨 2년 전- AWS 공식업데이트됨 8달 전
Hello, I want to make a response to this claim in reference to an issue I am dealing with:
"If you are using Sandbox environment then you need to upgrade to the production and can always initiate "request for production access" from SES console."
This isn't necessarily true as I have made multiple request production cases in the past and now I am no longer able to request production access due to dealing with the difficulty of the AWS team.
"Amazon SES has denied your request for production access. You may no longer request access from the Amazon SES console. For details about why your request was denied or to file an appeal, see case ID 9790969121 in the AWS Support Center."