Amazon SES Blog https://aws.amazon.com/blogs/ses/ Thu, 07 Dec 2017 01:28:11 +0000 en-US hourly 1 About the Amazon Trust Services Migration https://aws.amazon.com/blogs/ses/669-2/ Thu, 07 Dec 2017 01:19:12 +0000 05307f203f69feab89b8c8272d33328011d7f981 Amazon Web Services is moving the certificates for our services—including Amazon SES—to use our own certificate authority, Amazon Trust Services. We have carefully planned this change to minimize the impact it will have on your workflow. Most customers will not have to take any action during this migration. About the Certificates The Amazon Trust Services […] <p>Amazon Web Services is moving the certificates for our services—including Amazon SES—to use our own certificate authority, Amazon Trust Services. We have carefully planned this change to minimize the impact it will have on your workflow. Most customers will not have to take any action during this migration.</p> <h2>About the Certificates</h2> <p>The Amazon Trust Services Certificate Authority (CA) uses the Starfield Services CA, which has been valid since 2005. The Amazon Trust Services certificates are available in most major operating systems released in the past 10 years, and are also trusted by all modern web browsers.</p> <p>If you send email through the Amazon SES SMTP interface using a mail server that you operate, we recommend that you confirm that the appropriate certificates are installed. You can test whether your server trusts the Amazon Trust Services CAs by visiting the following URLs (for example, by using cURL):</p> <ul> <li><a href="https://good.sca0a.amazontrust.com/">https://good.sca0a.amazontrust.com/</a></li> <li><a href="https://good.sca1a.amazontrust.com/">https://good.sca1a.amazontrust.com/</a></li> <li><a href="https://good.sca2a.amazontrust.com/">https://good.sca2a.amazontrust.com/</a></li> <li><a href="https://good.sca3a.amazontrust.com/">https://good.sca3a.amazontrust.com/</a></li> <li><a href="https://good.sca4a.amazontrust.com/">https://good.sca4a.amazontrust.com/</a></li> </ul> <p>If you see a message stating that the certificate issuer is not recognized, then you should install the appropriate root certificate. You can download individual certificates from <a href="https://www.amazontrust.com/repository">https://www.amazontrust.com/repository</a>. The process of adding a trusted certificate to your server varies depending on the operating system you use. For more information, see “Adding New Certificates,” below.</p> <h2>AWS SDKs and CLI</h2> <p>Recent versions of the AWS SDKs and the AWS CLI are not impacted by this change. If you use an AWS SDK or a version of the AWS CLI released prior to February 5, 2015, you should upgrade to the latest version.</p> <h2>Potential Issues</h2> <p>If your system is configured to use a very restricted list of root CAs (for example, if you use certificate pinning), you may be impacted by this migration. In this situation, you must update your pinned certificates to include the Amazon Trust Services CAs.</p> <h2>Adding New Root Certificates</h2> <p>The following sections list the steps you can take to install the Amazon Root CA certificates on your systems if they are not already present.</p> <h3>macOS</h3> <p>To install a new certificate on a macOS server</p> <ol> <li>Download the .pem file for the certificate you want to install from <a href="https://www.amazontrust.com/repository">https://www.amazontrust.com/repository</a>.</li> <li>Change the file extension for the file you downloaded from .pem to .crt.</li> <li>At the command prompt, type the following command to install the certificate: <code>sudo security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keychain /path/to/certificatename.crt</code>, replacing <code>/path/to/certificatename.crt</code> with the full path to the certificate file.</li> </ol> <h3>Windows Server</h3> <p>To install a new certificate on a Windows server</p> <ol> <li>Download the .pem file for the certificate you want to install from <a href="https://www.amazontrust.com/repository">https://www.amazontrust.com/repository</a>.</li> <li>Change the file extension for the file you downloaded from .pem to .crt.</li> <li>At the command prompt, type the following command to install the certificate: <code>certutil -addstore -f &quot;ROOT&quot; c:\path\to\certificatename.crt</code>, replacing <code>c:\path\to\certificatename.crt</code> with the full path to the certificate file.</li> </ol> <h3>Ubuntu</h3> <p>To install a new certificate on an Ubuntu (or similar) server</p> <ol> <li>Download the .pem file for the certificate you want to install from <a href="https://www.amazontrust.com/repository">https://www.amazontrust.com/repository</a>.</li> <li>Change the file extension for the file you downloaded from .pem to .crt.</li> <li>Copy the certificate file to the directory /usr/local/share/ca-certificates/</li> <li>At the command prompt, type the following command to update the certificate authority store: <code>sudo update-ca-certificates</code></li> </ol> <h3>Red Hat Enterprise Linux/Fedora/CentOS</h3> <p>To install a new certificate on a Red Hat Enterprise Linux (or similar) server</p> <ol> <li>Download the .pem file for the certificate you want to install from <a href="https://www.amazontrust.com/repository">https://www.amazontrust.com/repository</a>.</li> <li>Change the file extension for the file you downloaded from .pem to .crt.</li> <li>Copy the certificate file to the directory /etc/pki/ca-trust/source/anchors/</li> <li>At the command line, type the following command to enable dynamic certificate authority configuration: <code>sudo update-ca-trust force-enable</code></li> <li>At the command line, type the following command to update the certificate authority store: <code>sudo update-ca-trust extract</code></li> </ol> <p>To learn more about this migration, see <a href="https://aws.amazon.com/blogs/security/how-to-prepare-for-aws-move-to-its-own-certificate-authority/">How to Prepare for AWS’s Move to Its Own Certificate Authority</a> on the AWS Security Blog.</p> Protect your Reputation with Email Pausing and Configuration Set Reputation Metrics https://aws.amazon.com/blogs/ses/protect-your-reputation-with-email-pausing-and-configuration-set-metrics/ Wed, 15 Nov 2017 18:02:05 +0000 cb38a922bfa0069ec18563db0e5136b419785100 In August, we launched the reputation dashboard, which helps you track important metrics that could impact your ability to send emails. By monitoring the metrics in this dashboard, you can protect your sender reputation, which can increase the likelihood that the emails you send will reach your customers’ inboxes. Today, we’re launching two features that […] <p>In August, we launched the reputation dashboard, which helps you track important metrics that could impact your ability to send emails. By monitoring the metrics in this dashboard, you can protect your sender reputation, which can increase the likelihood that the emails you send will reach your customers’ inboxes.</p> <p>Today, we’re launching two features that build upon the capabilities of the reputation dashboard. The first is the ability to temporarily pause email sending, either at the configuration set level, or across your entire Amazon SES account. The second is the ability to export reputation metrics for individual configuration sets.</p> <h3>Email Pausing</h3> <p>Today’s update includes new API operations that can temporarily pause your ability to send email using Amazon SES. To disable email sending across your entire Amazon SES account, you can use the <code>UpdateAccountSendingEnabled</code> operation. To pause sending only for emails sent using a specific configuration set, you can use the <code>UpdateConfigurationSetSendingEnabled</code> operation.</p> <p>Email pausing is helpful because Amazon SES uses automatic enforcement policies. If the bounce or complaint rates for your account are too high, your account is automatically placed on probation. If the bounce or complaint issues continue after the probation period has ended, your account may be suspended.</p> <p>With email pausing, you can temporarily halt your ability to send email before your account is placed on probation. While your ability to send email is paused, you can identify the issues that were causing your account to register high bounce or complaint rates. You can then resume sending after the issues are resolved.</p> <p>Email pausing helps ensure that your ability to send email using Amazon SES is not interrupted because of enforcement issues. It helps ensure that your sender reputation won’t be damaged by mistakes or unforeseen issues.</p> <p>You can learn more about the <a href="https://docs.aws.amazon.com/ses/latest/APIReference/API_UpdateAccountSendingEnabled.html">UpdateAccountSendingEnabled</a> and <a href="https://docs.aws.amazon.com/ses/latest/APIReference/API_UpdateConfigurationSetSendingEnabled.html">UpdateConfigurationSetSendingEnabled</a> operations in the <em>Amazon Simple Email Service API Reference</em>.</p> <h3>Configuration Set Reputation Metrics</h3> <p>Amazon SES automatically publishes the bounce and complaint rates for your account to Amazon CloudWatch. In CloudWatch, you can monitor these metrics over time, and create alarms that notify you when your reputation metrics cross certain thresholds.</p> <p>With today’s update, you can also publish reputation metrics for individual configuration sets to CloudWatch. This feature gives you additional information about the messages you send using Amazon SES. For example, if you send all of your marketing emails using one configuration set, and your transactional emails using a different configuration set, you can view distinct reputation metrics for each type of email.</p> <p>Because we anticipate that this feature will lead to the creation of many new configuration sets, we’re increasing the maximum number of configuration sets you can create from 50 to 10,000.</p> <p>For more information about exporting reputation metrics for configuration sets, see&nbsp;<a href="https://docs.aws.amazon.com/ses/latest/DeveloperGuide/configuration-sets-export-metrics.html">Exporting Reputation Metrics for a Configuration Set to CloudWatch</a> in the <em>Amazon Simple Email Service Developer Guide</em>.</p> <h3>Automating These Features</h3> <p>You can use AWS services—including Amazon SNS, AWS Lambda, and Amazon CloudWatch—to create a solution that automatically pauses email sending for your account when your overall reputation metrics cross a certain threshold. Or, to minimize disruption to your email sending program, you can pause email sending for a specific configuration set when the metrics for that configuration set cross a threshold. The following image illustrates the processes that occur when you implement these solutions.</p> <p><a href="https://d2908q01vomqb2.cloudfront.net/632667547e7cd3e0466547863e1207a8c0c0c549/2017/11/15/Email-Pausing-Diagram-BG.png"><img class="alignnone wp-image-650 size-large" src="https://d2908q01vomqb2.cloudfront.net/632667547e7cd3e0466547863e1207a8c0c0c549/2017/11/15/Email-Pausing-Diagram-BG-1024x512.png" alt="A flow diagram that illustrates a solution for automatically pausing Amazon SES email sending. Amazon SES provides reputation metrics to CloudWatch. If those metrics exceed a threshold, a CloudWatch alarm is triggered, which triggers an SNS topic. The SNS topic sends notifications (email, SMS), and executes a Lambda function, which pauses email sending in SES." width="1024" height="512" /></a></p> <p>For more information on both of these solutions, see <a href="https://docs.aws.amazon.com/ses/latest/DeveloperGuide/monitoring-sender-reputation-pausing.html">Automatically Pausing Email Sending</a> in the <em>Amazon Simple Email Service Developer Guide</em>.</p> <p>We’re always looking for ways to help safeguard the reputation you’ve worked hard to build. If you have suggestions, questions, or comments, we’d love to hear from you in the comments below, or in the <a href="https://forums.aws.amazon.com/forum.jspa?forumID=90">Amazon SES Forum</a>.</p> <p>These features are now available in the following AWS Regions: US West (Oregon), US East (N. Virginia), and EU (Ireland).</p> Amazon SES Now Supports DMARC Validation and Reporting for Incoming Email https://aws.amazon.com/blogs/ses/amazon-ses-now-supports-dmarc-validation-and-reporting-for-incoming-email/ Fri, 27 Oct 2017 18:18:06 +0000 57c54f1fcd93fe84bfc877db404d8e1395c19055 Amazon SES now adds DMARC verdicts to incoming emails, and publishes aggregate DMARC reports to domain owners. These two new features will help combat email spoofing and phishing, making the email ecosystem a safer and more secure place. What is DMARC? DMARC stands for Domain-based Message Authentication, Reporting, and Conformance. The DMARC standard was designed […] <p>Amazon SES now adds DMARC verdicts to incoming emails, and publishes aggregate DMARC reports to domain owners. These two new features will help combat email spoofing and phishing, making the email ecosystem a safer and more secure place.</p> <h2>What is DMARC?</h2> <p>DMARC stands for Domain-based Message Authentication, Reporting, and Conformance. The DMARC standard was designed to prevent malicious actors from sending messages that appear to be from legitimate senders. Domain owners can tell email receivers how to handle unauthenticated messages that appear to be from their domains. The DMARC standard also specifies certain reports that email senders and receivers send to each other. The cooperative nature of this reporting process helps improve the email authentication infrastructure.</p> <h2>How does Amazon SES Implement DMARC?</h2> <p>When you receive an email message through Amazon SES, the headers of that message will include a DMARC policy verdict alongside the DKIM and SPF verdicts (both of which are already present). This additional information helps you verify the authenticity of all email messages you receive.</p> <p>Messages you receive through Amazon SES will contain one of the following DMARC verdicts:</p> <ul> <li><strong>PASS</strong>&nbsp;– The message passed DMARC authentication.</li> <li><strong>FAIL</strong>&nbsp;– The message failed DMARC authentication.</li> <li><strong>GRAY</strong>&nbsp;– The sending domain does not have a DMARC policy.</li> <li><strong>PROCESSING_FAILED</strong>&nbsp;– An issue occurred that prevented Amazon SES from providing a DMARC verdict.</li> </ul> <p>If the DMARC verdict is <code>FAIL</code>, Amazon SES will also provide information about the sending domain’s DMARC settings. In this situation, you will see one of the following verdicts:</p> <ul> <li><strong>NONE&nbsp;</strong>– The owner of the sending domain requests that no specific action be taken on messages that fail DMARC authentication.</li> <li><strong>QUARANTINE&nbsp;</strong>– The owner of the sending domain requests that messages that fail DMARC authentication be treated by receivers as suspicious.</li> <li><strong>REJECT&nbsp;</strong>– The owner of the sending domain requests that messages that fail DMARC authentication be rejected.</li> </ul> <p>In addition to publishing the DMARC verdict on each incoming message, Amazon SES now sends DMARC aggregate reports to domain owners. These reports help domain owners identify systemic authentication failures, and avoid potential domain spoofing attacks.</p> <p><strong>Note</strong>: Domain owners only receive aggregate information about emails that do not pass DMARC authentication. These reports, known as RUA reports, only include information about the IP addresses that send unauthenticated emails to you. These reports do not include information about legitimate email senders.</p> <h2>How do I configure DMARC?</h2> <p>As is the case with SPF and DKIM, domain owners must publish their DMARC policies as DNS records for their domains. For more information about setting up DMARC, see <a href="http://docs.aws.amazon.com/ses/latest/DeveloperGuide/dmarc.html">Complying with DMARC Using Amazon SES</a> in the <em>Amazon SES Developer Guide</em>.</p> <p>DMARC reporting is now available in the following AWS Regions: US West (Oregon), US East (N. Virginia), and EU (Ireland). You can find more information about the <a href="http://docs.aws.amazon.com/ses/latest/DeveloperGuide/receiving-email-notifications-contents.html#receiving-email-notifications-contents-dmarcverdict-object">dmarcVerdict</a> and <a href="http://docs.aws.amazon.com/ses/latest/DeveloperGuide/receiving-email-notifications-contents.html#receiving-email-notifications-contents-dmarcrequestedreceiverpolicy-object">dmarcPolicy</a> objects in the <em>Amazon SES Developer Guide</em>. The Developer Guide also includes <a href="http://docs.aws.amazon.com/ses/latest/DeveloperGuide/receiving-email-action-lambda-example-functions.html#receiving-email-action-lambda-example-functions-4">a sample Lambda function</a> that you can use to bounce incoming emails that fail DMARC authentication.</p> Introducing Email Templates and Bulk Sending https://aws.amazon.com/blogs/ses/introducing-email-templates-and-bulk-sending/ Wed, 11 Oct 2017 22:26:08 +0000 5ce8bec432a8df77c2b649204aa1b68971ff98b3 (Edited October 11, 2017)—Corrected the structure of the template JSON file and the maximum template file size. The Amazon SES team is excited to announce our latest update, which includes two related features that help you send personalized emails to large groups of customers. This post discusses these features, and provides examples that you can […] <p><em>(Edited October 11, 2017)—Corrected the structure of the template JSON file and the maximum template file size.</em></p> <p>The Amazon SES team is excited to announce our latest update, which includes two related features that help you send personalized emails to large groups of customers. This post discusses these features, and provides examples that you can follow to start using these features right away.</p> <h2>Email templates</h2> <p>You can use email templates to create the structure of an email that you plan to send to multiple recipients, or that you will use again in the future. Each template contains a subject line, a text part, and an HTML part. Both the subject and the email body can contain variables that are automatically replaced with values specific to each recipient. For example, you can include a <code>{{name}}</code> variable in the body of your email. When you send the email, you specify the value of <code>{{name}}</code> for each recipient. Amazon SES then automatically replaces the <code>{{name}}</code> variable with the recipient’s first name.</p> <h3>Creating a template</h3> <p>To create a template, you use the <code>CreateTemplate</code> API operation. To use this operation, pass a JSON object with four properties: a template name (<code>TemplateName</code>), a subject line (<code>SubjectPart</code>), a plain text version of the email body (<code>TextPart</code>), and an HTML version of the email body (<code>HtmlPart</code>). You can include variables in the subject line or message body by enclosing the variable names in two sets of curly braces. The following example shows the structure of this JSON object.</p> <pre>{ &quot;Template&quot;: { &quot;TemplateName&quot;: &quot;MyTemplate&quot;, &quot;SubjectPart&quot;: &quot;Greetings, {{name}}!&quot;, &quot;TextPart&quot;: &quot;Dear {{name}},\r\nYour favorite animal is {{favoriteanimal}}.&quot;, &quot;HtmlPart&quot;: &quot;&lt;h1&gt;Hello {{name}}&lt;/h1&gt;&lt;p&gt;Your favorite animal is {{favoriteanimal}}.&lt;/p&gt;&quot; } }</pre> <p>Use this example to create your own template, and save the resulting file as <em>mytemplate.json</em>. You can then use the <a href="https://aws.amazon.com/cli/">AWS Command Line Interface</a> (AWS CLI) to create your template by running the following command: <code>aws ses create-template --cli-input-json file://mytemplate.json</code></p> <h3>Sending an email created with a template</h3> <p>Now that you have created a template, you’re ready to send email that uses the template. You can use the <code>SendTemplatedEmail</code> API operation to send email to a single&nbsp;destination&nbsp;using a template. Like the <code>CreateTemplate</code> operation, this operation accepts a JSON object with four properties. For this operation, the properties are the sender’s email address (<code>Source</code>), the name of an existing template (<code>Template</code>), an object called <code>Destination</code> that contains the&nbsp;recipient addresses&nbsp;(and, optionally, any CC or BCC addresses) that will receive the email, and a property that refers to the values that will be replaced in the email (<code>TemplateData</code>). The following example shows the structure of the JSON object used by the <code>SendTemplatedEmail</code> operation.</p> <pre>{ &quot;Source&quot;: &quot;sender@example.com&quot;, &quot;Template&quot;: &quot;MyTemplate&quot;, &quot;Destination&quot;: { &quot;ToAddresses&quot;: [ &quot;alejandro.rosalez@example.com&quot; ] }, &quot;TemplateData&quot;: &quot;{ \&quot;name\&quot;:\&quot;Alejandro\&quot;, \&quot;favoriteanimal\&quot;: \&quot;zebra\&quot; }&quot; }</pre> <p>Customize this example to fit your needs, and then save the resulting file as <em>myemail.json</em>. One important note: in the <code>TemplateData</code> property, you must use a blackslash (\) character to escape the quotes within this object, as shown in the preceding example.</p> <p>When you’re ready to send the email, run the following command: <code>aws ses send-templated-email --cli-input-json file://myemail.json</code></p> <h2>Bulk email sending</h2> <p>In most cases, you should use email templates to send personalized emails to several customers at the same time. The SendBulkTemplatedEmail API operation helps you do that. This operation also accepts a JSON object. At a minimum, you must supply a sender email address (<code>Source</code>), a reference to an existing template (<code>Template</code>), a list of recipients in an array called <code>Destinations</code> (within which you specify the recipient’s email address, and the variable values for that recipient), and a list of fallback values for the variables in the template (<code>DefaultTemplateData</code>). The following example shows the structure of this JSON object.</p> <pre>{ &quot;Source&quot;:&quot;sender@example.com&quot;, &quot;ConfigurationSetName&quot;:&quot;ConfigSet&quot;, &quot;Template&quot;:&quot;MyTemplate&quot;, &quot;Destinations&quot;:[ { &quot;Destination&quot;:{ &quot;ToAddresses&quot;:[ &quot;anaya.iyengar@example.com&quot; ] }, &quot;ReplacementTemplateData&quot;:&quot;{ \&quot;name\&quot;:\&quot;Anaya\&quot;, \&quot;favoriteanimal\&quot;:\&quot;yak\&quot; }&quot; }, { &quot;Destination&quot;:{ &quot;ToAddresses&quot;:[ &quot;liu.jie@example.com&quot; ] }, &quot;ReplacementTemplateData&quot;:&quot;{ \&quot;name\&quot;:\&quot;Liu\&quot;, \&quot;favoriteanimal\&quot;:\&quot;water buffalo\&quot; }&quot; }, { &quot;Destination&quot;:{ &quot;ToAddresses&quot;:[ &quot;shirley.rodriguez@example.com&quot; ] }, &quot;ReplacementTemplateData&quot;:&quot;{ \&quot;name\&quot;:\&quot;Shirley\&quot;, \&quot;favoriteanimal\&quot;:\&quot;vulture\&quot; }&quot; }, { &quot;Destination&quot;:{ &quot;ToAddresses&quot;:[ &quot;richard.roe@example.com&quot; ] }, &quot;ReplacementTemplateData&quot;:&quot;{}&quot; } ], &quot;DefaultTemplateData&quot;:&quot;{ \&quot;name\&quot;:\&quot;friend\&quot;, \&quot;favoriteanimal\&quot;:\&quot;unknown\&quot; }&quot; }</pre> <p>This example sends unique emails to Anaya (anaya.iyengar@example.com), Liu (liu.jie@example.com), Shirley (shirley.rodriguez@example.com), and a fourth recipient (richard.roe@example.com), whose name and favorite animal we didn’t specify. Anaya, Liu, and Shirley will see their names in place of the <code>{{name}}</code> tag in the template (which, in this example, is present in both the subject line and message body), as well as their favorite animals in place of the <code>{{favoriteanimal}}</code> tag in the message body. The <code>DefaultTemplateData</code> property determines what happens if you do not specify the <code>ReplacementTemplateData</code> property for a recipient. In this case, the fourth recipient will see the word “friend” in place of the <code>{{name}}</code> tag, and “unknown” in place of the <code>{{favoriteanimal}}</code> tag.</p> <p>Use the example to create your own list of recipients, and save the resulting file as <em>mybulkemail.json</em>. When you’re ready to send the email, run the following command: <code>aws ses send-bulk-templated-email --cli-input-json file://mybulkemail.json</code></p> <h2>Other considerations</h2> <p>There are a few limits and other considerations when using these features:</p> <ul> <li>You can create up to 10,000 email templates per Amazon SES account.</li> <li>Each template can be up to&nbsp;500KB in size, including both the text and HTML parts.</li> <li>You can include an unlimited number of replacement variables in each template.</li> <li>You can send email to up to 50 destinations in each call to the <code>SendBulkTemplatedEmail</code> operation. A destination includes a list of recipients, as well as CC and BCC recipients. Note that the number of destinations you can contact in a single call to the API may be limited by your account’s maximum sending rate. For more information, see <a href="http://docs.aws.amazon.com/ses/latest/DeveloperGuide/manage-sending-limits.html">Managing Your Amazon SES Sending Limits</a>&nbsp;in the <em>Amazon SES Developer Guide</em>.</li> </ul> <p>We look forward to seeing the amazing things you create with these new features. If you have any questions, please leave a comment on this post, or let us know in the <a href="http://forums.aws.amazon.com/forum.jspa?forumID=90">Amazon SES forum</a>.</p> Announcing the Reputation Dashboard https://aws.amazon.com/blogs/ses/announcing-the-reputation-dashboard/ Thu, 24 Aug 2017 17:40:29 +0000 678b73ecd485e179d49f97563b58587518c4b7a6 The Amazon SES team is pleased to announce the addition of a reputation dashboard to the Amazon SES console. This new feature helps you track issues that could impact the sender reputation of your Amazon SES account. What information does the reputation dashboard provide? Amazon SES users must maintain bounce and complaint rates below a […] <p>The Amazon SES team is pleased to announce the addition of a reputation dashboard to the Amazon SES console. This new feature helps you track issues that could impact the sender reputation of your Amazon SES account.</p> <h2>What information does the reputation dashboard provide?</h2> <p>Amazon SES users must maintain bounce and complaint rates below a certain threshold. We put these rules in place to protect the sender reputations of all Amazon SES users, and to prevent Amazon SES from being used to deliver spam or malicious content. Users with very high rates of bounces or complaints may be put on probation. If the bounce or complaint rates are not within acceptable limits by the end of the probation period, these accounts may be shut down completely.</p> <p>Previous versions of Amazon SES provided basic sending metrics, including information about bounces and complaints. However, the bounce and complaint metrics in this dashboard only included information for the past few days of email sent from your account, as opposed to an overall rate.</p> <p>The new reputation dashboard provides overall bounce and complaint rates for your entire account. This enables you to more closely monitor the health of your account and adjust your email sending practices as needed.</p> <h2>Can’t I just calculate these values myself?</h2> <p>Because each Amazon SES account sends different volumes of email at different rates, we do not calculate bounce and complaint rates based on a fixed time period. Instead, we use a representative volume of email. This representative volume is the basis for the bounce and complaint rate calculations.</p> <p>Why do we use representative volume in our calculations? Let’s imagine that you sent 1,000 emails one week, and 5 of them bounced. If we only considered a week of email sending, your metrics look good. Now imagine that the next week you only sent 5 emails, and one of them bounced. Suddenly, your bounce rate jumps from half a percent to 20%, and your account is automatically placed on probation. This example may be an extreme case, but it illustrates the reason that we don’t use fixed time periods when calculating bounce and complaint rates.</p> <p>When you open the new reputation dashboard, you will see bounce and complaint rates calculated using the representative volume for your account. We automatically recalculate these rates every time you send email through Amazon SES.</p> <h2>What else can I do with these metrics?</h2> <p>The Bounce and Complaint Rate metrics in the reputation dashboard are automatically sent to <a href="https://aws.amazon.com/cloudwatch/">Amazon CloudWatch</a>. You can use CloudWatch to create dashboards that track your bounce and complaint rates over time, and to create alarms that send you notifications&nbsp;when these metrics cross certain thresholds. To learn more, see <a href="http://docs.aws.amazon.com/ses/latest/DeveloperGuide/reputationdashboard-cloudwatch-alarm.html">Creating Reputation Monitoring Alarms Using CloudWatch</a> in the <a href="https://docs.aws.amazon.com/ses/latest/DeveloperGuide/Welcome.html"><em>Amazon SES Developer Guide</em></a>.</p> <h2>How can I see the reputation dashboard?</h2> <p>The reputation dashboard is now available to all Amazon SES users. To view the reputation dashboard, sign in to the <a href="https://console.aws.amazon.com/ses/home">Amazon SES console</a>. On the left navigation menu, choose <strong>Reputation Dashboard</strong>. For more information, see <a href="http://docs.aws.amazon.com/ses/latest/DeveloperGuide/monitor-sender-reputation.html">Monitoring Your Sender Reputation</a> in the <em>Amazon SES Developer Guide</em>.</p> <p>We hope you find the information in the reputation dashboard to be useful in managing your email sending programs and campaigns. If you have any questions or comments, please leave a comment on this post, or let us know in the <a href="https://forums.aws.amazon.com/forum.jspa?forumID=90">Amazon SES forum</a>.</p> Announcing Dedicated IP Pools https://aws.amazon.com/blogs/ses/announcing-dedicated-ip-pools/ Thu, 17 Aug 2017 20:00:31 +0000 455853da0c8bfe9f78d470ec67f9a95fae1af770 The Amazon SES team is pleased to announce that you can now create groups of dedicated IP addresses, called dedicated IP pools,&nbsp;for your email sending activities. Prior to the availability of this feature, if you leased several dedicated IP addresses to use with Amazon SES, there was no way to specify which dedicated IP address […] <p>The Amazon SES team is pleased to announce that you can now create groups of dedicated IP addresses, called <em>dedicated IP pools</em>,&nbsp;for your email sending activities.</p> <p>Prior to the availability of this feature, if you leased several dedicated IP addresses to use with Amazon SES, there was no way to specify which dedicated IP address to use for a specific email. Dedicated IP pools solve this problem by allowing you to send emails from specific IP addresses.</p> <p>This post includes information and procedures related to dedicated IP pools.</p> <h2>What are dedicated IP pools?</h2> <p>In order to understand dedicated IP pools, you should first be familiar with the concept of dedicated IP addresses. Customers who send large volumes of email will typically lease one or more dedicated IP addresses to use when sending mail from Amazon SES. To learn more, see <a href="https://aws.amazon.com/blogs/ses/amazon-ses-now-offers-dedicated-ip-addresses/">our blog post about dedicated IP addresses</a>.</p> <p>If you lease several dedicated IP addresses for use with Amazon SES, you can organize these addresses into groups, called pools. You can then associate each pool with a configuration set. When you send an email that specifies a configuration set, that email will be sent from the IP addresses in the associated pool.</p> <h2>When should I use dedicated IP pools?</h2> <p>Dedicated IP pools are especially useful for customers who send several different types of email using Amazon SES. For example, if you use Amazon SES to send both marketing emails and transactional emails, you can create a pool for marketing emails and another for transactional emails.</p> <p>By using dedicated IP pools, you can isolate the sender reputations for each of these types of communications. Using dedicated IP pools gives you complete control over the sender reputations of the dedicated IP addresses you lease from Amazon SES.</p> <h2>How do I create and use dedicated IP pools?</h2> <p>There are two basic steps for creating and using dedicated IP pools. First, create a dedicated IP pool in the Amazon SES console and associate it with a configuration set. Next, when you send email, be sure to specify the configuration set associated with the IP pool you want to use.</p> <p>For step-by-step procedures, see <a href="http://docs.aws.amazon.com/ses/latest/DeveloperGuide/dedicated-ip-pools.html">Creating Dedicated IP Pools</a> in the <em>Amazon SES Developer Guide</em>.</p> <h2>Will my email sending process change?</h2> <p>If you do not use dedicated IP addresses with Amazon SES, then your email sending process will not change.</p> <p>If you use dedicated IP pools, your email sending process may change slightly. In most cases, you will need to specify a configuration set in the emails you send. To learn more about using configuration sets, see <a href="http://docs.aws.amazon.com/ses/latest/DeveloperGuide/using-configuration-sets-in-email.html">Specifying a Configuration Set When You Send Email</a>&nbsp;in the <em>Amazon SES Developer Guide</em>.</p> <p>Any dedicated IP addresses that you lease that are not part of a dedicated IP pool will automatically be added to a default pool. If you send email without specifying a configuration set that is associated with a pool, then that email will be sent from one of the addresses in the default pool.</p> <p>Dedicated IP pools are now available in the following AWS Regions: us-west-2 (Oregon), us-east-1 (Virginia), and eu-west-1 (Ireland).</p> <p>We hope you enjoy this feature. If you have any questions or comments, please leave a comment on this post, or let us know in the <a href="http://forums.aws.amazon.com/forum.jspa?forumID=90">Amazon SES Forum</a>.</p> Open and Click Tracking Have Arrived https://aws.amazon.com/blogs/ses/open-and-click-tracking-have-arrived/ Tue, 01 Aug 2017 21:10:11 +0000 1b9524272e5ee600f9170b10d0de8d634b72d4d9 We’re pleased to announce the addition of open and click tracking metrics to Amazon SES. These metrics will help you measure the effectiveness of the email campaigns you send using Amazon SES. We’re also adding the ability to publish email sending metrics to Amazon Simple Notification Service (Amazon SNS) using event publishing. This feature gives […] <p>We’re pleased to announce the addition of open and click tracking metrics to Amazon SES. These metrics will help you measure the effectiveness of the email campaigns you send using Amazon SES.</p> <p>We’re also adding the ability to publish email sending metrics to Amazon Simple Notification Service (<a href="https://aws.amazon.com/sns/">Amazon SNS</a>) using event publishing. This feature gives you greater control over the sending notifications you receive through Amazon SNS.</p> <h2>What’s new in this release?</h2> <p>When you send an email using Amazon SES, we now collect metrics related to opens and clicks. <em>Opens</em>, in this sense, refers to the number of users who successfully received your email and opened it in their email clients; <em>clicks</em> refers to the number of users who received an email and clicked one or more links in it.</p> <p>Additionally, you can now use event publishing to push email sending notifications—including open and click notifications—using Amazon SNS. Previously, you could send account-level notifications through Amazon SNS. These notifications were pretty limited: you could only receive notifications about bounces, complaints, and deliveries, and you would receive notifications about all of these events across your entire Amazon SES account. Now you can use event publishing to send notifications about deliveries, opens, clicks, bounces, and complaints. Furthermore, you can set up event publishing so that you only receive notifications about emails sent using the configuration sets you specify in those emails.</p> <h2>Why should I use open and click tracking?</h2> <p>Whether you are sending marketing emails, transactional emails, or notifications, you need to know how effective your communications are. The email sending metrics feature of Amazon SES gives you data about entire email response funnel—the total number of emails that were sent, bounced, viewed, and clicked. You can then transform those insights into action.</p> <p>For example, the open and click tracking feature can help you identify the customers who are most interested in receiving the messages you send. By narrowing down your list of recipients and focusing on your most engaged customers, you can save money (by sending fewer messages), improve the response rates of your marketing campaigns (by targeting only the customers who are most interested in what you have to say), and protect your sender reputation (by reducing the number of bounces and complaints against your sending domain).</p> <h2>How do I enable open and click tracking?</h2> <p>If you’ve set up Sending Metrics in the past, then you can easily add open and click tracking to your existing configuration sets. On the <a href="https://us-west-2.console.aws.amazon.com/ses/home?#configuration-set-list:">Configuration Sets page</a>, choose the configuration set that contains your sending event destination; edit the event destination, check the boxes for <strong>Open</strong>&nbsp;and <strong>Click</strong>&nbsp;(as shown in the image below), and then choose <strong>Save</strong>.</p> <p><img class="aligncenter wp-image-535 size-full" src="https://d2908q01vomqb2.cloudfront.net/632667547e7cd3e0466547863e1207a8c0c0c549/2017/07/31/OpenClick-Screenshot.png" alt="" width="766" height="381" /></p> <h2>How does open and click tracking work?</h2> <p>Amazon SES makes very minor changes to your emails in order to make open and click tracking work. At the bottom of each message, we insert a 1 pixel by 1 pixel transparent GIF image. Each email includes a unique link to this image file; when the image is opened, we can tell exactly which message was opened and by whom.</p> <p>To track clicks, we set up a redirect for each link in the message. When a recipient clicks a link, they are sent to an Amazon SES server, and are immediately forwarded to the destination address. As with open tracking, each of these redirect links is unique, allowing us to easily determine which recipient clicked the link, when they clicked it, and the email from which they arrived at the link.</p> <h2>Can I disable click tracking?</h2> <p>You can disable click tracking by adding a special tag to the anchor tags in your HTML. For example, if you were linking to the AWS home page, a normal anchor link would look something like this:</p> <pre>&lt;a href=&quot;https://aws.amazon.com/&quot;&gt;Amazon Web Services&lt;/a&gt;</pre> <p>To disable click tracking for that same link, you would modify to look like this:</p> <pre>&lt;a <strong>ses:no-track</strong> href=&quot;https://aws.amazon.com/&quot;&gt;Amazon Web Services&lt;/a&gt;</pre> <p>Because the <code>ses:no-track</code> attribute is non-standard HTML, we automatically remove it from the version of the email that arrives in your recipients’ inboxes.</p> <h2>How do I use event publishing with Amazon SNS?</h2> <p>If you’ve set up event destinations in the past, then the process of setting up an Amazon SNS event destination will be very familiar. You can add an Amazon SNS destination to an existing configuration set, or create a new configuration set that uses Amazon SNS as its event destination. To learn more, see “<a href="http://docs.aws.amazon.com/ses/latest/DeveloperGuide/event-publishing-add-event-destination-sns.html">Set Up an Amazon SNS Event Destination for Amazon SES Event Publishing</a>” in our Developer Guide.</p> <p>We’re excited about this release. Let us know what you think of these new features in the <a href="https://forums.aws.amazon.com/forum.jspa?forumID=90">SES Forum</a>, or in the comments for this post.</p> Guest post: How EmailOctopus built an email marketing platform using Amazon SES https://aws.amazon.com/blogs/ses/guest-post-how-emailoctopus-built-an-email-marketing-platform-using-amazon-ses/ Wed, 12 Jul 2017 18:25:01 +0000 0066ad69704ee0913c05ffb5107fe6ecbd28e7e1 The following guest post was written by Tom Evans, COO of EmailOctopus. Our product, EmailOctopus, grew from a personal need. We were working on another business venture, and as our email subscriber base grew, the costs of using the larger email service providers became prohibitively expensive for an early-stage startup. At this point we were […] <p><em>The following guest post was written by Tom Evans, COO of EmailOctopus.</em></p> <hr style="border: .25px solid #eee;width: 25%;margin: 2em auto" /> <p>Our product, EmailOctopus, grew from a personal need. We were working on another business venture, and as our email subscriber base grew, the costs of using the larger email service providers became prohibitively expensive for an early-stage startup.</p> <p>At this point we were already using Amazon SES to send sign up confirmations to our users. We loved Amazon SES’ low pricing and high deliverability, but being a transactional email service, we missed some tracking features offered by our marketing provider. We decided to develop a simple interface to make it easier for us to build and track the performance of marketing emails on top of the Amazon SES platform.</p> <p>After sharing our accomplishments with other founders, and with no other SaaS solutions on the market that met the same need, we began to turn our basic script into a polished email marketing application. We named our application EmailOctopus. Over 4 years later, and with over 1.5 billion emails delivered through Amazon SES, our mission remains the same: to make contacting your customers as easy and inexpensive as possible.</p> <p>EmailOctopus is now a fully fledged platform, with thousands of users sending marketing campaigns every day. Our platform integrates directly with our customers’ AWS accounts and provides them with an easy-to-use front end on top of the SES platform. EmailOctopus users&nbsp;can upload or register subscribers who have opted into their correspondence (through an import or one of our many integrations), then send a one-off campaign or an automated marketing series, all while closely tracking the performance of those emails and allowing the recipients to opt-out.</p> <h2>Scaling EmailOctopus to handle millions of emails per day</h2> <p>Building an email marketing platform from scratch has presented a number of challenges, both technical and operational. EmailOctopus has quickly grown from a side project to a mature business that has sent over 1.5 billion emails through Amazon SES.</p> <p>One of the biggest challenges of our growth has been dealing with a rapidly expanding database. Email marketing generates a huge amount of data. We log every view, bounce, click, spam report, open and unsubscribe for every email sent through our platform. A single campaign can easily generate over 1 million of these events.</p> <p>Our event processing system sits on a number of microservices spread over <a href="https://aws.amazon.com/ec2/">EC2</a> and <a href="https://aws.amazon.com/lambda/">Lambda</a>, which allows us to selectively scale our services based on demand. Figure 1, below,&nbsp;demonstrates just how irregular this demand is. We save over $500 a month using an on-demand serverless model.</p> <div id="attachment_518" style="width: 650px" class="wp-caption aligncenter"> <img class="wp-image-518 size-large" src="https://d2908q01vomqb2.cloudfront.net/632667547e7cd3e0466547863e1207a8c0c0c549/2017/07/12/EmailOctopus-peaks-1024x368.png" alt="" width="640" height="230" /> <p class="wp-caption-text"><span style="border-top: 1px solid black;padding-top: .5em;font-size: small;font-family: monospace">Figure 1. Number of events processed over time.</span></p> </div> <p>This model helps us manage our costs and ensures we only pay for the computing power we need. &nbsp;We rely heavily on <a href="https://aws.amazon.com/cloudformation/">CloudFormation</a> scripts to edit that infrastructure; these scripts allow every change to be version-controlled and propagated across all of our environments. In preparing for this blog post, we took a look at how that template had changed over the years—we’d forgotten just how much it had evolved. As our user base grew from 1 customer to 10,000, a single EC2 instance writing to a MySQL database just didn’t cut it.&nbsp;We now rely on a large portion of the AWS suite to reliably consume our event data, as illustrated in Figure 2, below.</p> <div id="attachment_519" style="width: 650px" class="wp-caption aligncenter"> <img class="wp-image-519 size-large" src="https://d2908q01vomqb2.cloudfront.net/632667547e7cd3e0466547863e1207a8c0c0c549/2017/07/12/EmailOctopus-diagram-1024x587.png" alt="" width="640" height="367" /> <p class="wp-caption-text"><span style="border-top: 1px solid black;padding-top: .5em;font-size: small;font-family: monospace">Figure 2. Our current event processing infrastructure.</span></p> </div> <p>Operationally, our business has needed to make changes to scale too. Processes that worked fine with a handful of clients do not work so well with 10,000 users. We pride ourselves on providing our customers with a superior and personal service; to maintain that commitment, we dedicate 10% of our development time to improving our internal tools. One of these projects resulted in a dashboard which quickly provides us with detailed information on each user and their journey through the platform. The days of asking our support team to assemble database queries are long gone!</p> <h2>What makes EmailOctopus + SES different from the competition?</h2> <p>Amazon SES uses proprietary content filtering technologies and monitors the status of its services rigorously. This means that you’re likely to see increased deliverability on your communication, while saving up to 10x on your current email marketing costs. EmailOctopus pricing plans range from $0 to $109 per month (depending on the number of recipients you need to store), and the cost of sending email through Amazon SES is also very low: you pay nothing for the first 62,000 emails you send through Amazon SES each&nbsp;month, and&nbsp;$0.10 per 1,000 emails after that. Need to send a million emails in a month? You can do it for less than $100 with EmailOctopus + Amazon SES.</p> <p>Our easy-to-use interface and integrations make it easy to add new subscribers, and our email templates help you create trackable, beautiful, responsive emails. We even offer trigger-based automated email delivery—perfect for onboarding new customers.</p> <h2>I’m ready to get started!</h2> <p>Great! We’ve made it easy to start using EmailOctopus with Amazon SES. First, if you don’t already have one, <a href="https://console.aws.amazon.com/console/home">create an Amazon Web Services account</a>. Once you’ve done that, head over to our website and <a href="https://emailoctopus.com/account/sign-up">create an EmailOctopus account</a>. From there, we’ll walk you through the quick and easy process of linking the two services together.</p> <p>If you’ve never used Amazon SES before, you will also need to provide some information about the types of communication you plan to send. This important step in the process ensures that all new Amazon SES users are reputable, and that they will not have a negative impact on other users who send email through Amazon SES. Once you’ve finished that step, you’ll be ready to start sending emails using EmailOctopus and Amazon SES.</p> <p>To learn more about what EmailOctopus can do for your business, visit our website at <a href="https://emailoctopus.com">https://emailoctopus.com</a>.</p> <p>&nbsp;</p> Creating a Daily Dashboard to Track Bounces and Complaints https://aws.amazon.com/blogs/ses/creating-a-daily-dashboard-to-track-bounces-and-complaints/ Tue, 04 Jul 2017 16:03:52 +0000 210ac6472a05494683554e48c3cbfaa81eadc4c6 (Edited July 11, 2017)—We added a link to a CloudFormation stack in the “Building a Daily Dashboard” section. You can use the CloudFormation stack to create the daily dashboard in a few simple steps. Bounce and complaint rates can have a negative impact on your sender reputation, and a bad sender&nbsp;reputation makes it less likely […] <p><em>(Edited July 11, 2017)—We added a link to a CloudFormation stack in the “<a href="#building-a-daily-dashboard">Building a Daily Dashboard</a>” section. You can use the CloudFormation stack to create the daily dashboard in a few simple steps.</em></p> <p>Bounce and complaint rates can have a negative impact on your sender reputation, and a bad sender&nbsp;reputation makes it less likely that the emails you send will reach your recipients’ inboxes. Further, if your bounce or complaint rate is too high, we may have to suspend your Amazon SES account to protect other users. For these reasons, it is very important that you have a process in place to remove email addresses that have bounced or complained from your recipient list.</p> <p>This article includes background information about bounces and complaints. It also discusses a sample solution that you can use to keep track of the bounce and complaint notifications that you receive.</p> <h2>What is a Bounce?</h2> <p>A bounce occurs when a message cannot be delivered to the intended recipient. There are two types of bounces:</p> <ul> <li>A<em> hard bounce</em>&nbsp;occurs when a persistent issue prevents the message from being delivered. Hard bounces can occur when the recipient’s email address does not exist or the receiving domain does not exist. When an email hard bounces, it means that the recipient did not receive the message, and Amazon SES will no longer attempt to deliver the message.</li> <li>A<em> soft bounce</em>&nbsp;occurs when a temporary issue prevents a message from being delivered. Soft bounces can occur when the recipient’s mailbox is full, when the connection to the receiving email server times out, or when there are too many simultaneous connections to the receiving mail server. When an email soft bounces, Amazon will attempt to redeliver it. If the issue persists, Amazon SES will stop trying to deliver the message, and the soft bounce will be converted&nbsp;to a hard bounce.</li> </ul> <p>To learn more about bounces, see the <a href="http://docs.aws.amazon.com/ses/latest/DeveloperGuide/e-faq-bn.html">Amazon SES Bounce FAQ</a> in the <em>Amazon SES Developer Guide</em>.</p> <h2>What is a Complaint?</h2> <p>When an email recipient clicks the <strong>Mark as Spam</strong> (or similar) button in his or her email client, the ISP records the event as a complaint. If the emails that you send generate too many of&nbsp;these complaint events, the ISP may&nbsp;conclude that you’re sending spam. Many&nbsp;ISPs provide feedback loops, in which the ISP provides you with information about the message that generated the complaint event.</p> <p>For more information about complaints, see the <a href="http://docs.aws.amazon.com/ses/latest/DeveloperGuide/e-faq-cm.html">Amazon SES Complaint FAQ</a> in the <em>Amazon SES Developer Guide</em>.</p> <h2 id="building-a-daily-dashboard">Building a Daily Dashboard</h2> <p>We recently added a section to the <em>Amazon SES Developer Guide</em> that documents the process of creating a daily bounce and complaint tracking dashboard. You can find the procedures for creating this daily dashboard at <a href="http://docs.aws.amazon.com/ses/latest/DeveloperGuide/bouncecomplaintdashboard.html">http://docs.aws.amazon.com/ses/latest/DeveloperGuide/bouncecomplaintdashboard.html</a>.</p> <p>Alternatively, you can <a href="https://raw.githubusercontent.com/awslabs/aws-support-tools/master/SES/SESReports/ses-reports.yaml" target="_blank" rel="noopener noreferrer">download our CloudFormation stack</a> to implement this solution with just a few clicks. To learn more about deploying CloudFormation stacks, see “<a href="http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/GettingStarted.Walkthrough.html">Get Started</a>” in the <em>AWS CloudFormation User Guide</em>.</p> <p>This solution uses several AWS components—including <a href="https://aws.amazon.com/sns/">Simple Notification Service (SNS)</a>, <a href="https://aws.amazon.com/sqs/">Simple Queue Service (SQS)</a>, <a href="https://aws.amazon.com/iam/">Identity and Access Management (IAM)</a>, <a href="https://aws.amazon.com/s3/">Simple Storage Service (S3)</a>, <a href="https://aws.amazon.com/lambda/">Lambda</a>, and <a href="https://aws.amazon.com/cloudwatch/">CloudWatch</a>—to create a dashboard that is emailed to you every day. The daily&nbsp;dashboard, illustrated&nbsp;in the following image, contains a list of the messages that generated bounces and complaints over the past 24 hours.</p> <p><img class="aligncenter wp-image-494 size-large" src="https://d2908q01vomqb2.cloudfront.net/632667547e7cd3e0466547863e1207a8c0c0c549/2017/06/20/SES-Blog_Bounce-Complaint-Dashboard-1024x481.png" alt="" width="640" height="301" /></p> <p>This solution uses SNS to track bounce and complaint notifications. Those notifications are then collected in an SQS queue. A CloudWatch trigger initiates a Lambda function, which collects the notification events from SQS, processes them, publishes a dashboard to an S3 bucket, and sends you an email when the dashboard is ready to view.&nbsp;The following image illustrates the architecture of this solution.</p> <p><img class="aligncenter wp-image-496 size-large" src="https://d2908q01vomqb2.cloudfront.net/632667547e7cd3e0466547863e1207a8c0c0c549/2017/06/20/SES-Blog_Bounce-Complaint-Dashboard-Architecture-1024x758.png" alt="" width="640" height="474" /></p> <p>When you receive the daily dashboard, you should use it to&nbsp;remove the addresses that hard bounced or complained from your recipient list. This measure will help protect&nbsp;your deliverability and inbox placement rates.</p> <p>This solution is just one method of tracking the bounces and complaints that you receive when sending email using Amazon SES. We hope you find this sample solution useful. If you have any questions about this solution, please leave a comment below, or start a discussion in the <a href="https://forums.aws.amazon.com/forum.jspa?forumID=90">Amazon SES forum</a>.</p> Amazon SES Can Now Automatically Warm Up Your Dedicated IP Addresses https://aws.amazon.com/blogs/ses/amazon-ses-can-now-automatic-warm-up-your-dedicated-ip-addresses/ Thu, 09 Mar 2017 17:02:23 +0000 73ad7d5c86413e25618037f90f0bc6151431d613 Edited November, 2017: Since this article was published, we have made some changes that impact the dedicated IP address feature. The article suggests that you can send up to 50,000 emails from an IP address per day. This limitation has since been removed. Your actual sending limit is determined by your use case and your […] <p><strong>Edited November, 2017</strong>: Since this article was published, we have made some changes that impact the dedicated IP address feature. The article suggests that you can send up to 50,000 emails from an IP address per day. This limitation has since been removed. Your actual sending limit is determined by your use case and your sending practices.</p> <hr style="width: 50%;text-align: center;margin-bottom: 2.5em" /> <p>The SES team is pleased to announce that, starting today, Amazon SES can automatically warm up your new dedicated IP addresses. Before the automatic warm-up feature was available, Amazon SES customers who leased dedicated IPs implemented their own warm-up mechanisms. Customers gradually increased email sending through a new dedicated IP before using the dedicated IP to its full capacity. This blog post explains how Amazon SES warms up your dedicated IPs, and how to enable the warm-up feature.</p> <h3><strong>Why do I have to warm up my dedicated IPs?</strong></h3> <p>You must warm up your dedicated IPs before you send a high volume of emails. Many receiving ISPs do not accept emails from an IP that suddenly sends a large volume of email. ISPs perceive this behavior as an indicator of abuse and a possible source of spam. To avoid emails getting dropped or having your sending severely throttled, warm up your IPs by gradually increasing the volume of emails you send through a new IP address. You can find more guidance about the <a href="http://docs.aws.amazon.com/ses/latest/DeveloperGuide/dedicated-ips.html#dedicated-ip-warming">warm up process</a> in the developer guide.</p> <h3><strong>How does Amazon SES warm up my dedicated IPs?</strong></h3> <p>After you enable automatic warm-up, Amazon SES limits the maximum number of emails that you send daily through your new dedicated IP addresses according to a predefined warm-up plan. This automated warm-up process takes up to 45 days. The process ensures that traffic through the newly leased dedicated IP address is gradually increased to establish a positive reputation with receiving ISPs. The maximum daily amount of mail increases from the first day until a maximum of 50,000 emails can be sent from an IP.</p> <h3><strong>When do I have to enable the automatic warm-up?</strong></h3> <p>By default, automatic warm-up is enabled for your account. All newly leased dedicated IP addresses are placed in the automatic warm-up plan. You can disable the automatic warm-up from the Dedicated IPs page in the <a href="https://console.aws.amazon.com/ses/">Amazon SES console</a>. If you are already using dedicated IPs to send emails, go to the Amazon SES console to turn this feature on to take advantage of automatic warm-up.</p> <p><a href="https://console.aws.amazon.com/ses/" rel="attachment wp-att-477"><img class="aligncenter size-full wp-image-477" src="https://d2908q01vomqb2.cloudfront.net/632667547e7cd3e0466547863e1207a8c0c0c549/2017/03/09/PrintScreen.jpg" alt="PrintScreen" width="1751" height="663" /></a></p> <p>Note: disabling automatic warm-up stops the warm-up process. All of your IP addresses will be considered fully warmed up. Re-enabling automatic warm-up does not start the warm-up for the dedicated IPs already allocated to your Amazon SES account.</p> <h3><strong>What happens with the emails sent beyond the daily maximum limit from the warm-up plan?</strong></h3> <p>If you enabled automatic warm-up and you are leasing dedicated IPs for the first time, then all emails that you send beyond the pre-planned daily warm-up plan are sent through shared IPs instead. This means that during the warm-up period, Amazon SES uses your dedicated and shared IPs from the Amazon SES IP pools to send your emails. After the warm-up is complete, Amazon SES sends emails only through your dedicated IPs, and the maximum number of emails you can send is limited by your daily email sending quota. For more information, see <a href="http://docs.aws.amazon.com/ses/latest/DeveloperGuide/manage-sending-limits.html">Managing Your Amazon SES Sending Limits</a> in the Amazon SES Developer Guide.</p> <p>If you are an existing dedicated IP customer requesting additional dedicated IPs, emails beyond the daily maximum limit per dedicated IP in the warm-up plan are sent only through dedicated IPs already allocated to your account.</p> <h3><strong>Does automatic warm-up incur extra cost?</strong></h3> <p>No. See the <a href="https://aws.amazon.com/ses/pricing/">Amazon SES pricing page</a> for dedicated IP pricing information.</p> <p>We hope you find this feature useful! If you have any questions or comments, let us know in the <a href="https://forums.aws.amazon.com/forum.jspa?forumID=90">SES Forum</a> or in the comment section of the blog.</p>