Handle Incoming Emails like a Pro (Mailgun API 2.0)
blog.mailgun.net
blog.mailgun.net
I'm hoping to open source our IMAP client wrapper soon, as it is a lot simpler than the standard library in Python.
It makes sense though. This allows several third parties to develop different interfaces that can iterate faster than something in the standard library can by providing them with a stable base.
You can extract and search anything from an IMAP account. Your app do not need to receive/parse the message.
and used MailGun to handle incoming email attachments (mainly a temporary stop-gap until I build an iOS app). Couldn't have been easier.
Fun times. Giving Mailgun a shot.
Long story short, Mailgun does have a spam filtering system: if you enable it for your domain, we'll put all your traffic through a cloud of SpamAsassin machines. Those machines themselves need to be re-trained every once in a while and we do that ourselves without providing any APIs to control that process because, frankly, we believe we can do it better. The spam score along with "Mailgun spam verdict" is POSTed into your route handler - I will update the blog post to include this: thank you for reminding!
Though one company's spam is another company's ham, so I wonder if this would work well enough across all your clients?
We do have a few customers who're using per-mailbox spam training via our "Beta API access" program, but we have not made the decision to launch it as a product yet. If this is something you may be interested in, reach me via email in my profile.
Thanks.
I've been looking for something like this and MailGun looks awesome, but we need to be able for (sub)domain owners to require DKIM for security reasons.
The other nice thing is that with sendgrid's pricing changes, you can't start to play with the parse API unless you're willing to shell out $80/month. Mailgun lets you use it on the free plan and it's only $20/month for custom domains.
I could add a few other things which were not mentioned in the blog post:
* Mailgun can forward cleaned up messages in MIME format to you as well, if you prefer to do your own parsing of some sort. By "cleaned up" I mean they're all UTF-8 and can be processed by your typical weak MIME parser (like Ruby's or even Python's)
* Mailgun can also store all incoming mail for you for debugging/archival purposes and you can query it later via POP3/IMAP
* Mailgun can also route messages to different email addresses, i.e. Mailgun routes aren't "parsing API" at all - they act as a proper mail processing engine and people are getting quite creative with their rules, parsing is just something they have to do. For example you can have multiple destinations for a route, i.e. by creating a route "sales@myapp.com -> [array of emails for your sales team]" you're essentially creating a mailing list without any coding on your end.
If you're interested in writing webhook handlers (for events or/and incoming messages) there is nothing new to learn: use http://postbin.org for debugging and from there it's mostly about the PHP itself and its frameworks.
If you're interested in using our HTTP API, we can send you some samples and perhaps collect some feedback. Please contact me: ev@mailgun.net