Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Assuming you have production access for <a href="http://aws.amazon.com/ses/" rel="nofollow">Amazon SES</a> already (see <a href="http://aws.amazon.com/ses/faqs/#10" rel="nofollow">What should I do after I'm finished testing and evaluating Amazon SES?</a>) and a sufficiently increased <em>Sending Quota</em> to send 200.000 mails/day in the first place (see <a href="http://docs.amazonwebservices.com/ses/latest/DeveloperGuide/ManagingActivity.PlanningAhead.html" rel="nofollow">How Amazon SES Sets Sending Limits</a>), the respective limits are documented for the <a href="http://docs.amazonwebservices.com/ses/latest/APIReference/API_SendEmail.html" rel="nofollow">SendEmail</a> action:</p> <blockquote> <p>The total size of the message cannot exceed 10 MB.</p> <p>Amazon SES has a limit on the total number of recipients per message: <strong>The combined number of To:, CC: and BCC: email addresses cannot exceed 50</strong>. If you need to send an email message to a larger audience, you can divide your recipient list into groups of 50 or fewer, and then call Amazon SES repeatedly to send the message to each group. <em>[emphasis mine]</em></p> </blockquote> <p><strong>Please note</strong>: It is strictly recommended to use <code>Bcc:</code> only for this kind of mass mailing operation, else your users will see their mail addresses exposed to each other and I can guarantee they won't be amused at all!</p> <p>So you <em>could</em> prepare mails with 50 <code>Bcc:</code> recipients at a time, dropping the outbound mail amount for your use case to about 4.000, which is a considerable improvement already. <strong>However</strong>, please note a respective AWS Team response to <a href="https://forums.aws.amazon.com/message.jspa?messageID=275868#275868" rel="nofollow">Increase sending limit, and question on FAQ</a>:</p> <blockquote> <p>if you're sending to multiple ISPs [...], I would recommend sending to one address at a time since <strong>certain ISPs are sensitive about multiple addresses on the BCC: line in large quantities</strong>. <em>[emphasis mine]</em></p> </blockquote> <p>Whether or not this warning applies depends on your use case as usual (e.g. you might be able to shard the mails by ISP etc.).</p> <p>Doing it asynchronously is fine and likely useful, but you need to ensure to stay within your <em>Maximum Send Rate</em> (mails/second) limit as well. These limits are visible in the SES tab of the <a href="http://aws.amazon.com/console/" rel="nofollow">AWS Management Console</a>, but available via the API as well of course (see <a href="http://docs.amazonwebservices.com/ses/latest/DeveloperGuide/ManagingActivity.SendingLimits.html" rel="nofollow">Monitoring Your Sending Limits</a> for details).</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload