Hacker News Reader

Mailgun has a great inbound api [1]. You can set up routing rules to let them post the email as json (or just forward it) to a specified url. The json also includes fields for the extracted quoted parts and signature. The latter is based on some machine learning, which other providers don't have afaik.

[1] https://documentation.mailgun.com/quickstart-receiving.html

View on HN

I would second Mailgun for inbound email. Granted, my use-case is very low-volume, but it works great and the email parsing seems to be pretty good.

I've previously used Mandrill for inbound, which has a lot of problems that I'd rather not enumerate. But that was at a much higher scale, so many of those problems I wouldn't have seen yet even if Mailgun has them.

Ooooh, that would be pretty handy. I've been relying on good old "please reply above this line" to parse inbound emails, precisely because I didn't want to muck around with ML to infer user intent (I reeeeally wish quotes, the reply-date separator, and signature blocks were standardized somehow). If there's a reliable improvement to this functionality provided by my email service, that's 100% a feature I'm willing to pay for. Thanks.

Reply on news.ycombinator.com