Updated Email (markdown)

Email.md

@@ -36,6 +36,8 @@ __Question__: For POP3 clients, is it acceptable to delete/destroy a message onc
 
 __Question__: For attachments, how should the attachment be stored in the attachments array?
 
+__Answer__: NK 2016-03-06 -  I vote for the direct output of a record from the `mailparser` package.  It seems rich and un-opinionated.  In addition, we should always assume a more specific package has more appreciation for their domain that we do.  As such, if they added a property they had a reason to do so (we should assume) and it should not be for us to question why or, unless we have a good reason to think otherwise, exclude it from our exposure of data.
+
 ---
 
 ### Related forum posts and issues:
@@ -95,4 +97,27 @@ The event for `list` contains status, msgCount, msgNumber and data.  Of these, e
 
 * What does the response from a POP3 `retr` request look like?
 
-The event for `retr` contains status, msgNumber and data.  The data is the body of the email ... this is truly the whole body and includes headers and payload.
+The event for `retr` contains status, msgNumber and data.  The data is the body of the email ... this is truly the whole body and includes headers and payload.
+
+* What does a mailparser parsed attachment look like?
+
+An example attachment includes:
+
+```
+{
+  contentType: "text/plain",
+  charset: "utf-8",
+  fileName: "application.ini",
+  transferEncoding: "base64",
+  contentDisposition: "attachment",
+  generatedFileName: "application.ini",
+  contentId: "1ba3477561756fe5833025518a94ac1c@mailparser",
+  checksum: "ac03f68312dcd4b5633a7e399dcf911b",
+  length: 611,
+  content:
+  {
+    type: "Buffer",
+    data: [59,32,52, ..., 52,53,10]
+  }
+}
+```