Hacker News Reader

Comment by carbocation | Hacker News Reader

Not exactly what you're asking, but I'd love to see software that:

_ Obtains incoming email

_ Parses it into something like a JSON object

_ Hands it off to a database or some software in configurable fashion

_ Explains how one configures it for a variety of common situations (email hosted mostly on Google Apps; email hosted locally; email hosted on mail server in same local network)

If you're interested in building something like that, I bet you'd find a lot of people who were willing to pay for it.

View on HN

The solution I've been envisioning would require you to pick a domain or sub-domain and allow the service to handle all incoming mail for it. You'd change your DNS settings for that domain/sub-domain to point to something we'd provide.

Then, when new emails come in, they'd be captured and we could do one of a couple of things with it: - post just the headers to a webhook - do something in response to the webhook response - delete the message - post full message to another webhook - put the message in an S3 bucket - put a pointer to the S3 message object in an SQS queue ...etc...

I've worked on other solutions that monitor specific accounts via IMAP, or have monitored Maildir queues, and they can be kind of a pain... that's why I'm looking at the service solution.

What do you think?

That sounds pretty reasonable for a subset of uses. In fact, it's probably possible to route all incoming mail pointed at

someAddress@domain.com

to silently go to

someAddress@sub.domain.com

So your service could, at the end of the day, be more flexible than I first imagined when I saw your reply. This sounds like something pretty amazing, frankly!

For an easy example, consider craigslist temp emails. With your service, I could generate those email addresses and have them end in @sub.domain.com. Your service would see any email sent to those addresses and then forward the reply along to S3/webhook/etc. I could then grab the contents and, if appropriate, forward those along to the actual user. This is just an obvious example that is pretty painful to set up manually, but would be pretty easy for a site to implement if it hooked into your service!

Reply on news.ycombinator.com