mail-parser icon indicating copy to clipboard operation
mail-parser copied to clipboard

Fast and robust e-mail parsing library for Rust

Results 15 mail-parser issues
Sort by recently updated
recently updated
newest added

First of all, thanks a lot for this library and the great amount of work that went into it🙏🏻 As far as i can tell images that are appended as...

enhancement

Hey @mdecimus! First of all, thank you for all your work on the AMAZING email crates you've contributed to the rust ecosystem. I rely on them so frequently! While sending...

enhancement

provide default for `DateTime` For ergonomic reasons an implementation of `Default` for `DateTime` is useful. All zero's and false values are fine, though some specific other value may be more...

The iterator returned by text_bodies returns an object that is not necessarily a text element. But can become a text element. Perhaps it might be better to have an iterator...

…hould be InlineBinary Fixes #70 This PR is independent of #68 but I can rebase on top of those changes if you want.

The inline images in this email are `PartType::Binary` instead of `PartType::InlineBinary`, is this intended behavior? ``` From: X To: Y Date: Mon, 13 Feb 2018 12:00:00 -0400 Subject: Example inline...

When parsing the example `legacy/034.eml` the returned parts are ``` html_body: [3, 4, 5], text_body: [2, 4, 5], attachments: [4, 5] ``` This seems at odds with [RFC8621](https://datatracker.ietf.org/doc/html/rfc8621#section-4.1.4) o attachments:...

Related issue: #38 The methods in `PartType` and `MessagePart` should utilize `raw_message()` instead of the field element to avoid returning incorrect values for nested messages.

Hey, I believe ludicrous mode to be a bit superfluous, as bounds checking appears to get optimised out by the compiler for u8 with 256 len arrays, judging by these...