email-parser

email-parser copied to clipboard

Fixed a lot of parsing errors

2

Hey! I recently ran `email-parser` on a batch of ~650.000 emails from 2004 - 2021. Initially roughly half of those emails were marked as invalid. I slowly went through the...

terhechte

For given input file in the zip, Email::parse will cause very deep stack issue (to trigger stack-overflow) Input [in.zip](https://github.com/Mubelotix/email-parser/files/6813481/in.zip) Output ``` AddressSanitizer:DEADLYSIGNAL ================================================================= ==4247==ERROR: AddressSanitizer: stack-overflow on address 0x7fff6bf82f58 (pc...

charlesxsh

Some brittleness parsing basic headers

1

When sending a sample of my inbox (selected via an IMAP fetch of "BODY.PEEK[HEADER.FIELDS (MESSAGE-ID DATE SUBJECT FROM)]") through this library, it fails to parse some entries. Exemplars: ``` "Subject:...

mmirate

### Basic email parsing - [x] RFC [5322](https://tools.ietf.org/html/rfc5322): `Working implementation` - [ ] RFC [6854](https://tools.ietf.org/html/rfc6854) ### Mime support - [x] RFC [2045](https://tools.ietf.org/html/rfc2045): `Working implementation` - [x] RFC [2231](https://tools.ietf.org/html/rfc2231): `Working implementation`...

Mubelotix

Switching to automatically-generated code from a [pest](https://pest.rs) grammar using my custom pest backend (for 800% speed boost) Pros: - Slight performance boost - Removes the whole parsing codebase - Safer,...

Mubelotix