parsemail
parsemail copied to clipboard
DusanKasan
Simple email parsing for Golang
I'm writing an application where the code using the Email object needs to be able to extract extension headers; an example is "X-Thread-ID".May I have a GetHeader method, please?
* [multipart.Reader.NextPart()](https://pkg.go.dev/mime/multipart#Reader.NextPart) hides the Content-Transfer encoding. Therefor I switched to `NextRawPart()` and needed to add the decoding to the `decodeContent(..)` func. * I also could have changed the detection of...
According to "Content-Transfer-Encoding" section of RFC 1341: > The values "8bit", "7bit", and "binary" all imply that NO encoding has been performed... CHANGE LOG: - Add 8bit support for content...
Embedded files store their filename as a parameter of the content-type and content-disposition. It would be handy if the parsemail package supported extracting them conveniently. It's not particularly difficult to...
There are emails with no text in the body that contain only a binary attachment. Mail clients handle those as proper attachments yet parsemail doesn't recognize them.
I got the error when parsing an inbound email ``` Unknown top level mime type: multipart/related ```
As indicated in the https://tools.ietf.org/html/rfc2045#section-6.1 Content-Transfer-Encoding may be *binary*. I'm added suport this encoding.
``` ----boundary_23799_9387ca5c-694c-4010-b46e-3154585edde8 Content-Type: application/octet-stream; name="filename.pdf" Content-Transfer-Encoding: base64 Content-Disposition: attachment ... ``` Hi Thanks for a great lib! I am using this to parse a lot of emails and found this...
Hey, great little library, saved me a bunch of time. I've run into some minor issues with third parties sending emails with "Content-Transfer-Encoding" set to "Base64" rather than "base64". This...
