parsemail
parsemail copied to clipboard
REPO UNMAINTAINED
Sadly, this repo has not been updated in more than 3 years and it doesn't look like it will ever be. The library is pretty nice, it just misses some important functionality regarding content-transfer-encoding which was provided by PRs but never merged.
So I decided to create the new fork with CI and integrate all open PRs into it:
- https://github.com/DusanKasan/parsemail/pull/42 MERGED make encoding case-insensitive
- https://github.com/DusanKasan/parsemail/pull/41 MERGED to allow attaching text/html attachments
- https://github.com/DusanKasan/parsemail/pull/39 MERGED (test case only as quoted-printable implemented by another PR) adds quoted-printable
- https://github.com/DusanKasan/parsemail/pull/38 MERGED use NextRawPart instead of NextPart and decode content the same way as the rest of the library
- https://github.com/DusanKasan/parsemail/pull/37 MERGED TODO NEEDS MANUAL FIX TO AVOID RE-ENCODE Add 8bit and binary decoding support
- https://github.com/DusanKasan/parsemail/pull/31 SKIPPED incomplete duplicate of 37
- https://github.com/DusanKasan/parsemail/pull/29 MERGED Parse email with just a binary attachment and no text
- https://github.com/DusanKasan/parsemail/pull/28 SKIPPED duplicate of 42
- https://github.com/DusanKasan/parsemail/pull/26 MERGED Decode content with supported Content-Encoding everywhere
- https://github.com/DusanKasan/parsemail/pull/25 SKIPPED duplicate of 26
- https://github.com/DusanKasan/parsemail/pull/27 TODO: Support to Encapsulated Messages (message/rfc822) inside multipart/mixed
- https://github.com/DusanKasan/parsemail/pull/24 MERGED (test case for base64 encoding only)
Some of them required manual merging but the resulting code should be correct, hopefully.
The fork is a drop-in replacement (just change the import to github.com/k3a/parsemail
). I will attempt to keep the API the same. If you miss some functionality, feel free to contribute to the fork.
I've also made a separate branch with integrated PRs which is directly mergeable into this original repo in case it resurrects but I won't update that branch going forward.
Some of them required manual merging but the resulting code should be correct, hopefully.
Unfortunately your fork seems to throw "unexpected EOF" errors on simple emails with replies, so I unfortunately can't recommend folks use it at this time.
It has the same test suite as this repo, with couple of more cases added. You can create an issue in my fork and provide a test case which fails. Thanks.
@k3a, your fork doesn't have the Issues tab enabled.
ah, strange. Fixed now!