^(abuse@|hostmaster@|postmaster@|webmaster@).*
I'd gladly pay $.0008 per message x2 to cover both sides of that event because I have very little usage. By putting email receiving into a tier that costs over $400 per year they've priced me out of the service.
It's disappointing the way these companies are happy to have enthusiasts, hobbyists, and side projects light-housing their products for them at the start, but eventually switch to paid tiers that alienate those same types of early adopters. It feels like it happens with every single service I use.
Boo!
https://sendgrid.com/docs/for-developers/parsing-email/setti...
Building some type of custom endpoint for it is too much work for what it does. I already pay for email where I can set up unlimited domain aliases, so I'll just wait for my Mailgun email and switch back to aliases.
The incoming mail filtering was the only reason I decided to try Mailgun instead of Twilio or SES. I already have SES set up for transactional mail and my usage is so low they don't even bill me for it.
The email doesn't even mention that 'email receiving' is switched off as a result of moving me to this plan! Pretty poor, IMO.
I've just blocked SES's ip ranges on my servers.
I'm not sure this is valid. Some users will consider anything spam, including password reset emails they asked for.
But SES is super basic. It's just an API, no fancy analytics.
So of course, I built a small web app that "wraps around" SES, and gives you some insight into what you're sending, some pretty graphs, and other stuff.
If anyone is feeling adventurous, it's https://messageray.com
You give it an AWS access key with permissions for SES, and you can send 60k free emails a month. It's just a side project atm, and completely free.