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.
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.