-
Notifications
You must be signed in to change notification settings - Fork 606
The Email node provides both input and output of emails. The node is available on NPM at:
As of 2016-03-06, the node has dependencies on:
The current implementation uses the IMAP protocol to interact with a back-end IMAP provider. The very last email seen is received and the message added to an emitted event. If the email body is plain text, it is added to msg.payload. If the email body is HTML, it is added to msg.html. The subject line of the email is propagated in msg.topic.
There are a number of potential enhancements available to the email node that can be addressed. These include:
- Support of IMAP that is not over SSL/TLS.
- Support for self-certified SSL certificates.
- Support for attachment processing. Attachments should appear as an array in
msg.attachments. - Support for POP3 as well as IMAP.
- Support for more than just last message processing.
Consider an email message that is sitting on an email server. It appears that an email is transmitted over SMTP and received by the email server and stored. It also appears that the email is saved in a certain format. That email can then be retrieved by a client application using IMAP and/or POP3.
Question: Is the email message retrieved via IMAP and POP3 the same format/content? If I retrieve the "blob-o-data" that represents my email, do I get the same think with both IMAP and POP3 retrievers?
- Forum: Retrieving email attachments using the email input node
- Issue: #641 - Email input issue / special EOL characters?
- Issue: #182 - Email-in: duplicate not sent / Error: read ECONNRESET
- Issue: #123 - extending e-mail node's usage of nodemailer createTransport
- Issue: #132 - social/email-in module cannot get mail
- mailparser - Parse an email message.
- nodemailer - Send an SMTP email.
- imap - Receive a message via IMAP.
- poplib - POP3 client.
- How do we retrieve an email using POP3?