frodovdr/node-red-nodes
1
0
Fork 0
mirror of https://github.com/node-red/node-red-nodes.git synced 2023-10-10 13:36:58 +02:00
Code Issues Releases Wiki Activity

Updated Email (markdown)

Neil Kolban 2016-03-07 23:52:12 -06:00
parent 2a676bf95b
commit 141de561dd
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Email.md

@ -32,6 +32,8 @@ Consider an email message that is sitting on an email server. It appears that a
__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?
__Answer__: NK 2016-03-07 - After testing, the answer is yes. Whether the email is received in parts via IMAP or as a complete entity using POP3, the result in both cases is identical and can be fed into `mailparser` for processing.
__Question__: For POP3 clients, is it acceptable to delete/destroy a message once received and processed?
__Question__: For attachments, how should the attachment be stored in the attachments array?
@ -123,3 +125,5 @@ An example attachment includes:
```
* `mailparser` works against POP3 retrieved messages, can it work against IMAP?
Yes. Testing has shown that using the IMAP library, if we request both HEADER and TEXT parts and then invoke `mailparser.write(message)` for each message part received, we can then call `mailparser.end()` and the parsing occurs as desired. This means that both POP3 and IMAP can both leverage `mailparser`.