Does your web application need to receive inbound email? In order to automate email to an application or service, a developer has to write code that constantly checks a POP3 or IMAP email account in the background. This process is painful to set up, rife with potential errors and requires a lot of background coding that is dissimilar from conventional web development.
Instead of doing that, use Email Post. Email Post automatically manages the work of checking email accounts, scaling up as needed to meet demand. When email is found, we archive it, post it to your web application and provide API end points for you to do other things to it. All you need to do is create a URL that accepts the posted data.
Do you maintain a dialogue (forums, discussions, ticketing) with your customers?
Do you send emails from a "noreply@" email address and wish that you could read replies?
Want to associate the emails that your customers send to you to their account in your application?
Want to collect newsletter or list-serve emails as part of a service or application?
There are many uses for inbound email, but most developers don't bother trying to collect or use it because it's difficult to do. Email Post changes all that so that you don't to spend resources collecting or watching email accounts and, instead, focus on what you want to do with the information.
Emails tend to be long and heavy and formatted in way (MIME) that is not easy to understand. When we post the email data to your application, we send clean text values that are easy to understand. The long body and attachment content is stored online for you to retrieve and delete at your leisure. Our API allows you to retrieve and delete with ease.
At the moment, we're still working on building and testing everything. To join our mailing list, send an email to interested@getemailpost.com and we'll send you updates.