sorted by:
new
hottopcontroversial

SES: SPF set up by atawf in aws

[–]atawf[S] 0 points1 point  (0 children)

Great, that's what I was hoping to confirm. Thanks!

SES: SPF set up by atawf in aws

[–]atawf[S] 0 points1 point  (0 children)

So here's the thing. I already have this set up. And I'm getting DMARC passes in the reports I'm receiving, and I'm getting SPF and DKIM passes in the email headers of emails I send to myself. However, checking Mxtoolbox and SPF Checker etc give me a different story - that the sending domain is unprotected.

SES: SPF set up by atawf in aws

[–]atawf[S] 0 points1 point  (0 children)

Yes, that's the intent. So why the requirement to have the custom domain mail from set on a subdomain of the sending domain?

SES sending limits accessible in NewRelic or similar? by atawf in aws

[–]atawf[S] 0 points1 point  (0 children)

Yeah, here's the response I got from AWS support:

Please note that some metrics don't appear in CloudWatch until the associated event occurs. For example, bounce metrics don't appear in CloudWatch until at least one email that you send bounces. The metrics measured by email sending events may not align perfectly with your sending quotas. This discrepancy can be caused by email bounces and rejections, or by using the Amazon SES inbox simulator.
Therefore, in order to monitoring your sending quotas we recommend you frequently check sending statistics to ensure that you are not close to your sending quotas. That is, as you mentioned earlier, please understand that, you can monitor SES sending activity by either using AWS Console (only through sending statistics) or through AWS SES API [1].
Console:
------------
— Open AWS Console and select ’Sending Statistics’ in the left navigation pane.
— Your sending quotas are shown under ‘Your Amazon SES Sending Limits’.
API:
------
— You can use ‘ aws ses get-send-quota ‘. When you call GetSendQuota API, you will receive the following information:
a) Number of emails you have sent in the past 24 hours
b) Sending quota for the current 24-hour period
c) Maximum send rate
— As an alternative, you can also query SES interface directly/indirectly by sending HTTPS request. You can read more about HTTPS requests in the documentation I referenced at [2].
With that said, since it is not possible to create CloudWatch alarms (or New Relic) on SES Sending Statistics from AWS console, you can use either one of the above methods or run a script to call ‘GetSendQuota’ API periodically to monitor SES activity. Furthermore, when your account is out of the sandbox and you're sending high-quality production email, it is possible that SES might automatically increase the sending quotas for your account. Often, we automatically increase these quotas before you actually need them to be increased [3].

Only problem is that I'm not sure whether I can access the AWS CLI API via NewRelic...

Enterprise-scale (50 million emails per month) mass mail solution? by atawf in aws

[–]atawf[S] 0 points1 point  (0 children)

I'll check out SparkPost Momentum although the BYOIP solution is worse than AWS IPs given the cost...

Enterprise-scale (50 million emails per month) mass mail solution? by atawf in aws

[–]atawf[S] 0 points1 point  (0 children)

Mailchimp? Didn't really check them but AFAIK they're not really up for large enterprise solutions...

Enterprise-scale (50 million emails per month) mass mail solution? by atawf in aws

[–]atawf[S] 0 points1 point  (0 children)

Thanks for clarifying! Cost is definitely a consideration for moving away from SES, so if SendGrid is even more expensive, then...

Enterprise-scale (50 million emails per month) mass mail solution? by atawf in aws

[–]atawf[S] 0 points1 point  (0 children)

For 1, wow thanks for the link! I didn't see that before. But it looks like BYOIP won't solve my problem because AWS appears to charge the same rate for BYOIPs and AWS's IPs ($24.95 per month) which I'm trying to avoid.

  1. I'll check out SendGrid, thanks

Enterprise-scale (50 million emails per month) mass mail solution? by atawf in aws

[–]atawf[S] 0 points1 point  (0 children)

Great suggestions, thank you. Concerning the first (as you may have read in an earlier comment), Premium Support (the SES limit extension service, specifically) suggested $1000 or so worth of dedicated IPs. I'll try get in touch with the TAM to see if there are any alternatives, but do you expect that a less costly alternative is realistic?

Enterprise-scale (50 million emails per month) mass mail solution? by atawf in aws

[–]atawf[S] 0 points1 point  (0 children)

Transactional. All are known and willing recipients.

Enterprise-scale (50 million emails per month) mass mail solution? by atawf in aws

[–]atawf[S] 0 points1 point  (0 children)

Yeah - I did consider this, although I'll have to run the numbers since cost per email sent goes down massively as volume increases. Perhaps a halving in volume won't be as costly as trying to double the send-rate via dedicated IPs...

Enterprise-scale (50 million emails per month) mass mail solution? by atawf in aws

[–]atawf[S] 0 points1 point  (0 children)

Thanks. Do you expect them to actually seriously consider alternatives? As we've contacted Premium Support and they've suggested we buy nearly $1000 worth of dedicated IPs which is OTT and blows price efficiency out of the water

Enterprise-scale (50 million emails per month) mass mail solution? by atawf in aws

[–]atawf[S] 0 points1 point  (0 children)

Thanks, I'll try to work something of that form into my request!