|
7 | 7 | [](https://twitter.com/stalwartlabs)
|
8 | 8 |
|
9 | 9 | _mail-parser_ is an **e-mail parsing library** written in Rust that fully conforms to the Internet Message Format standard (_RFC 5322_), the
|
10 |
| -Multipurpose Internet Mail Extensions (MIME; _RFC 2045 - 2049_) as well as other [internet messaging RFCs](#conformed-rfcs). |
| 10 | +Multipurpose Internet Mail Extensions (MIME; _RFC 2045 - 2049_) as well as many other [internet messaging RFCs](#conformed-rfcs). |
11 | 11 |
|
12 | 12 | It also supports decoding messages in [41 different character sets](#supported-character-sets) including obsolete formats such as UTF-7.
|
13 | 13 | All Unicode (UTF-*) and single-byte character sets are handled internally by the library while support for legacy multi-byte encodings of Chinese
|
@@ -72,19 +72,19 @@ Performance and memory safety were two important factors while designing _mail-p
|
72 | 72 | )
|
73 | 73 | .as_bytes();
|
74 | 74 |
|
75 |
| - let message = Message::parse(input); |
| 75 | + let message = Message::parse(input).unwrap(); |
76 | 76 |
|
77 | 77 | // Parses addresses (including comments), lists and groups
|
78 | 78 | assert_eq!(
|
79 | 79 | message.get_from(),
|
80 |
| - &Address::Address(Addr { |
| 80 | + &HeaderValue::Address(Addr { |
81 | 81 | name: Some("Art Vandelay (Vandelay Industries)".into()),
|
82 | 82 | address: Some("art@vandelay.com".into())
|
83 | 83 | })
|
84 | 84 | );
|
85 | 85 | assert_eq!(
|
86 | 86 | message.get_to(),
|
87 |
| - &Address::GroupList(vec
|
220 | 218 | - [RFC 2049 - Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples](https://datatracker.ietf.org/doc/html/rfc2049)
|
221 | 219 | - [RFC 2231 - MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations](https://datatracker.ietf.org/doc/html/rfc2231)
|
| 220 | +- [RFC 2557 - MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)](https://datatracker.ietf.org/doc/html/rfc2557) |
222 | 221 | - [RFC 2183 - Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field](https://datatracker.ietf.org/doc/html/rfc2183)
|
| 222 | +- [RFC 2392 - Content-ID and Message-ID Uniform Resource Locators](https://datatracker.ietf.org/doc/html/rfc2392) |
| 223 | +- [RFC 3282 - Content Language Headers](https://datatracker.ietf.org/doc/html/rfc3282) |
223 | 224 | - [RFC 6532 - Internationalized Email Headers](https://datatracker.ietf.org/doc/html/rfc6532)
|
224 | 225 | - [RFC 2152 - UTF-7 - A Mail-Safe Transformation Format of Unicode](https://datatracker.ietf.org/doc/html/rfc2152)
|
225 | 226 | - [RFC 2369 - The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields](https://datatracker.ietf.org/doc/html/rfc2369)
|
226 | 227 | - [RFC 2919 - List-Id: A Structured Field and Namespace for the Identification of Mailing Lists](https://datatracker.ietf.org/doc/html/rfc2919)
|
| 228 | +- [RFC 3339 - Date and Time on the Internet: Timestamps](https://datatracker.ietf.org/doc/html/rfc3339) |
227 | 229 | - [RFC 8621 - The JSON Meta Application Protocol (JMAP) for Mail (Section 4.1.4)](https://datatracker.ietf.org/doc/html/rfc8621#section-4.1.4)
|
228 | 230 |
|
229 | 231 | ## Supported Character Sets
|
|
0 commit comments