11–20 of 92 posts
If you are not in the business of selling email delivery, you should be buying email delivery from a company who is in that business. It's extremely hard to get emails delivered and it's even harder for a small company. For your use case you could probably use Postmark and get good delivery with that.
OP is doing just that, Amazon SES = Simple Email Service
Things like this are to be expected with shared IP addresses for mail services. This sounds like something Amazon should figure out more than anything. There's probably something going on with a customer or theirs (misconfiguration, spammer, vulnerability exploited) that's triggering spam detection rules. At least Google reports the issue back to you instead of silently dropping all of your email like many other mail…
Checking out the pricing page, a dedicated IP costs $24.95 per month, which would be more than the actual cost of emails for many small-medium apps (e.g. 100K emails per month would be about $10).
Ooc, do other email providers have the same shared-IP problem? E.g. Mailgun, Postmark, Sendgrid?
This is typically not a big deal, as explained in the message, it is a temporary countermeasure. It'll resolve itself as long as you really aren't spamming. Though Gmail responds citing your IP, Gmail and all other large email services don't use IP filtering. Just about all email service providers use domain reputation, since IPs are ephemeral. If you are sending transactional emails that your customers have agreed t…
If you and I are both using SES to send to the same person, and my message results in a hard bounce, then your messages to that person will start to silently fail.
[1] https://docs.aws.amazon.com/ses/latest/dg/sending-email-glob...
Things like this are to be expected with shared IP addresses for mail services. This sounds like something Amazon should figure out more than anything. There's probably something going on with a customer or theirs (misconfiguration, spammer, vulnerability exploited) that's triggering spam detection rules. At least Google reports the issue back to you instead of silently dropping all of your email like many other mail…
Very useful thread. I recently considered SES for a quick app and didn't discover the purpose of dedicated IPs. They're listed under add ons, but seem somewhat essential if the emails are important. Checking out the pricing page, a dedicated IP costs $24.95 per month, which would be more than the actual cost of emails for many small-medium apps (e.g. 100K emails per month would be about $10). Ooc, do other email prov…
Yes, that is why they let people get a dedicated IP pools and FCrDNS using their corporation name for a price. It is not uncommon for the shared IP pools to get rate limits, temporary blocks, etc... and the corporation specific dedicated IP's are more likely to get through especially if they handle UCE complaints properly.
If you are not in the business of selling email delivery, you should be buying email delivery from a company who is in that business. It's extremely hard to get emails delivered and it's even harder for a small company. For your use case you could probably use Postmark and get good delivery with that.
Using SES is buying email delivery from a company who is in that business.
SES is an email sending infrastructure tool. That's not the same.
IMO equating SES with an email company is like saying home depot is a contractor because they sell hammers and lumber. It gives you the tools to be able to build stuff but it's not the same as a construction company.
Earlier quoted context omitted.
Very useful thread. I recently considered SES for a quick app and didn't discover the purpose of dedicated IPs. They're listed under add ons, but seem somewhat essential if the emails are important. Checking out the pricing page, a dedicated IP costs $24.95 per month, which would be more than the actual cost of emails for many small-medium apps (e.g. 100K emails per month would be about $10). Ooc, do other email prov…
do other email providers have the same shared-IP problem? Yes, that is why they let people get a dedicated IP pools and FCrDNS using their corporation name for a price . It is not uncommon for the shared IP pools to get rate limits, temporary blocks, etc... and the corporation specific dedicated IP's are more likely to get through especially if they handle UCE complaints properly.
I didn't spend a huge amount of time reading the docs (just enough to get up and running), but I didn't notice this about other providers either. Great to be aware of this for future reference.
Things like this are to be expected with shared IP addresses for mail services. This sounds like something Amazon should figure out more than anything. There's probably something going on with a customer or theirs (misconfiguration, spammer, vulnerability exploited) that's triggering spam detection rules. At least Google reports the issue back to you instead of silently dropping all of your email like many other mail…
I finally started sending anything from AWS SES straight to trash because the spam on their platform is persistent and they are non-responsive to spam reports. I was getting 30+ fraudulent/spam emails a day in just one inbox alone.
I had to help multiple customers who had access to SES shut off for valid use cases because they didn't handle events coming back from customers appropriately.