[donmcronald]

Do you literally block (aka drop) mail from SES IPs? That's awful for your users.

If you really distrust mail from those IPs so much, why not just filter it straight to SPAM? At least you'd be delivering it and your users could whitelist senders (or domains) they trust.

[cpncrunch]

My users are: me. I get 100% spam from that ip range. This prevents me wasting my time on this spam.

[sethammons]

I also work in this space. We have many customers who leave email platforms on Amazon because the IP space is polluted. Many inbox providers are extra cautious with email from those IPs because spamming is easy. Even if your IP is not used for spamming, someone else in the same /24 space could be.

[donmcronald]

I feel like they could solve that by making people buy-in to shared IP pools where the low volume pricing is a relatively high one time fee.

For example, if you want a quota of 100 messages per day, you have to pay a one time fee of $.10 per message to get into the pool, so $10. If you want a quota of 50k messages per day you have to pay a one time fee of $.005 per message, so $250.

[webbie917]

I don't love the pricing examples (cost prohibitive for many), but I like an idea of IP pool clusters where you pay to be on a certain tier level.

[CodeWriter23]

> Do you literally block (aka drop) mail from SES IPs? That's awful for your users.

My good friend has worked on the email system for a mid-range consumer ISP for about the past 10 or so years. He told me 93% of all email they receive is spam. And they have a 60PB NAS for their mail store. So for every 1PB of storage they had to discard ~14PB of junk. And that’s just the stuff they summarily dismiss. Then some of the remaining 7% they accept makes it to your Junk folder.