TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Show HN: mailparser.io - extract data from inbound emails

73 点作者 krakaukiosk将近 12 年前

14 条评论

bryanh将近 12 年前
Hey guys!<p>I built something like this to scratch an itch at Zapier (both personally and for a few of our customers). I&#x27;ve mulled over releasing it someday for fun. This is a real need because (frighteningly?) a majority of the business world runs on:<p><pre><code> * Generated emails * Spreadsheets </code></pre> First of all, I realize this stuff can get complex. But I have one major critique: your extractor UI is <i>way way way</i> too complex. It should be outrageously simple. As in, here are your emails, highlight the data you want to extract. It&#x27;s hard to build, I know, but I have doubts that your average user will sit through this: <a href="http://i.imgur.com/5xjy4dS.png" rel="nofollow">http:&#x2F;&#x2F;i.imgur.com&#x2F;5xjy4dS.png</a>.<p>The concept is great though. The landing page is wonderful. Simple, to the point, decent use cases, inside the app has a nice onboarding and great options around exporting, etc... I really dig it.<p>Best of luck guys!
评论 #6039664 未加载
评论 #6039693 未加载
beefsack将近 12 年前
I just recently decided that I wanted an in-house solution to inbound email handling (the user can send emails into the server containing commands to run) as I didn&#x27;t like the expense or having to rely on an external service to do it for me. In the space of about half a day I had a working test bed:<p>* Vanilla Postfix<p>* A user with a .forward file, calling curl to post the email to my receiver route on my app<p>* A receiver in my Go app using the inbuilt mail package<p>* Logic to recursively parse multipart emails to extract plain text where possible, or strip tags from HTML when there is no text&#x2F;plain version<p>I&#x27;ve been amazed at the performance and the reliability of it even in staging. It automatically emails back a confirmation of the commands and the confirmation comes back lightning quick, back through the Postfix server.<p>Anyone considering creating their own inbound email handler shouldn&#x27;t be scared to have a crack, I was amazed at how simple and rewarding it was.
评论 #6040551 未加载
jtheory将近 12 年前
There&#x27;s no mention of security, or the trust involved in outsourcing email workflow handling to you.<p>The interest for attackers isn&#x27;t as high as something like LastPass, but <i>at a bare minimum</i> a successful hack will come back with a big list of valid email addresses and companies they have relationships with -- which would be very valuable to someone interested in spoofing, for example.<p>And that&#x27;s assuming that the people&#x2F;person behind mailparser.io are honest.<p>It depends on what kind of data your clients might want to handle in email workflow, but I imagine most businesses will be wary of passing off potentially sensitive material to an outside party that they don&#x27;t trust. Things like &quot;first month free&quot; don&#x27;t address this -- the fear isn&#x27;t &quot;we&#x27;ll try this service and it won&#x27;t work for us, and our money will be wasted&quot;, it&#x27;s &quot;we&#x27;ll try this service, and an employee or hacker will sell our data to competitors, spam&#x2F;upsell our customers, sell our contact lists...&quot;.<p>Obviously these aren&#x27;t the most likely scenarios, but it&#x27;s a bit like hiring a new employee who will be working <i>completely without oversight</i> with your company data... You&#x27;d want to put serious time into interviews, checking references, etc..<p>The site as-is: as far as I can tell, there are no human beings behind the site, or any established company. There&#x27;s no phone number or address. It&#x27;s not even clear what country (and hence legal jurisdiction) the business is operating in.<p>I don&#x27;t mean to come off as too negative -- there are still companies that will not have a problem with the risks (and&#x2F;or for whom the risks will be minimal), but you&#x27;ll cast a wider net with a more solid presence.
rgrieselhuber将近 12 年前
I have a need for something like this and had been planning to use Mailgun. Perhaps some additional information on your site explaining how you guys are different would help people decide.
评论 #6039332 未加载
LogicX将近 12 年前
We (<a href="http://metascribe.com" rel="nofollow">http:&#x2F;&#x2F;metascribe.com</a>) use mandrill from mailchimp for our inbound mail which appears for now to be free - works great for our purposes. Everyone thinks of them as only outbound and inbound is not a function they highlight, so figured I&#x27;d mention it.<p><a href="http://Mandrill.com" rel="nofollow">http:&#x2F;&#x2F;Mandrill.com</a>
评论 #6039481 未加载
tmchow将近 12 年前
Kudos on having a &quot;use cases&quot; section on your site. More services need to include this type of info.
jrabone将近 12 年前
&quot;All you need to do is to send emails to us.&quot; - no thanks. If you&#x27;ve built something more sophisticated than I can implement with Perl and Exim&#x27;s system filter functionality, I might be interested in giving you money to save me my time. Maybe a per-domain license?
tegansnyder将近 12 年前
Thanks for sharing. I have been a similar service called Cloudmailin.com to extract tracking numbers from third party drop shipping suppliers. They have a decent API, might have to check out your service next time I need to set one up.
gdilla将近 12 年前
I haven&#x27;t fully automated this, but I&#x27;ve been using BBedit&#x27;s batch regex to parse emails. Since these are emails coming from our iPhone app, they&#x27;re all pretty generic in terms of payload (a few sentences). I just throw a months worth of emails into a folder, regex it, word cloud it, and then I see what people are yammering about the most.
jf22将近 12 年前
I was just about to click your call to action but the carousel switched.<p><a href="http://shouldiuseacarousel.com/" rel="nofollow">http:&#x2F;&#x2F;shouldiuseacarousel.com&#x2F;</a><p>Carousels are bad. Stop using them.
prakster将近 12 年前
Signed up; how do I parse the text in the Body of the email? Is there a tutorial?
ismaelc将近 12 年前
Cool service! How can I secure the result dispatcher though? It seems to generate random character combinations at the end of the base URL. But someone might &#x27;randomly&#x27; get my mailparser emails
pallandt将近 12 年前
Interesting :) I was about to ask what are the typical use cases for this, but then I noticed the quite prominent &#x27;Use Cases&#x27; menu link.
chezmo将近 12 年前
this could actually be interesting for event organizers. one could forward their rsvp@event.com email address to mailparser.io and get a csv file back with all the attendee names in it.