3 ms·

Mailgun is (was) great for setting up a quick regex to process incoming mail. Maybe I'm misusing it, but I point all my non-email domains there and let this re

Mailgun is (was) great for setting up a quick regex to process incoming mail. Maybe I'm misusing it, but I point all my non-email domains there and let this regex forward everything to my main domain: ^(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!

veeralpatel979 7y ago
I've posted this elsewhere in this discussion but have you tried out Sendgrid Inbound Parse? Does it meet your requirements? https://sendgrid.com/docs/for-developers/parsing-email/setting-up-the-inbound-parse-webhook/ https://sendgrid.com/docs/for-developers/parsing-email/setti...
- donmcronald 7y ago
  Technically, yes. Practically, no. Mailgun has a checkbox to forward matched messages to another address, so the appeal was having something extremely easy, fast to configure, and reliable. 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.
OJFord 7y ago
Ditto, I only just got the email about this today; so now I have <1 month to figure out something else. The email doesn't even mention that 'email receiving' is switched off as a result of moving me to this plan! Pretty poor, IMO.

veeralpatel979 7y ago

I've posted this elsewhere in this discussion but have you tried out Sendgrid Inbound Parse? Does it meet your requirements? https://sendgrid.com/docs/for-developers/parsing-email/setting-up-the-inbound-parse-webhook/ https://sendgrid.com/docs/for-developers/parsing-email/setti...

donmcronald 7y ago
Technically, yes. Practically, no. Mailgun has a checkbox to forward matched messages to another address, so the appeal was having something extremely easy, fast to configure, and reliable. 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.

OJFord 7y ago

Ditto, I only just got the email about this today; so now I have <1 month to figure out something else. The email doesn't even mention that 'email receiving' is switched off as a result of moving me to this plan! Pretty poor, IMO.