<!-- SPDX-License-Identifier: EUPL-1.2 OR GPL-3.0-or-later -->
# melib

[![GitHub license](https://img.shields.io/github/license/meli/meli)](https://github.com/meli/meli/blob/master/COPYING) [![Crates.io](https://img.shields.io/crates/v/melib)](https://crates.io/crates/melib) [![docs.rs](https://docs.rs/melib/badge.svg)](https://docs.rs/melib)

Library for handling email for email clients.

## Cargo Compile-time Features

`melib` supports opting in and out of features at compile time with cargo features.

The contents of the `default` feature are:

```toml
default = ["imap", "nntp", "maildir", "mbox-notify", "smtp"]
```

A list of all the features and a description for each follows:

| Feature flag                                          | Dependencies                                     | Notes                                                |
|-------------------------------------------------------|--------------------------------------------------|------------------------------------------------------|
| <a name="maildir-feature">`maildir`</a>               | `notify` crate                                   | Provides the *maildir* backend                       |
| <a name="mbox-notify-feature">`mbox-notify`</a>       | `notify` crate                                   | Provides notification support for the *mbox* backend |
| <a name="notmuch-feature">`notmuch`</a>               | `maildir` feature                                | Provides the *notmuch* backend                       |
| <a name="imap-feature">`imap`</a>                     | `imap-codec` crate, `tls` feature                | Provides the *IMAP* backend                          |
| <a name="jmap-feature">`jmap`</a>                     | `http` feature, `url` crate with `serde` feature | Provides the *JMAP* backend                          |
| <a name="nntp-feature">`nntp`</a>                     | `tls` feature                                    | Provides the *NNTP* (Usenet) backend                 |
| <a name="smtp-feature">`smtp`</a>                     | `tls` feature                                    | Integrated async *SMTP* client                       |
| <a name="sqlite3-feature">`sqlite3`</a>               | `rusqlite` crate with `bundled-full` feature     | Used in caches                                       |
| <a name="sqlite3-static-feature">`sqlite3-static`</a> | `rusqlite` crate with `bundled-full` feature     | Same as `sqlite3` feature but provided for consistency and in case `sqlite3` feature stops bundling libsqlite3 statically in the future.
| <a name="gpgme-feature">`gpgme`</a>                   |                                                  | *GPG* use by dynamically loading `libgpgme.so`       |
| <a name="http-feature">`http`</a>                     | `isahc` crate                                    | Used for *HTTP* client needs, notably JMAP`          |
| <a name="tls-feature">`tls`</a>                       | `native-tls` crate                               |                                                      |
| <a name="http-static-feature">`http-static`</a>       | `isahc` crate with `static-curl` feature         | Links with `curl` statically                         |
| <a name="tls-static-feature">`tls-static`</a>         | `native-tls` crate with `vendored` feature       | Links with `OpenSSL` statically where it's used      |
| <a name="imap-trace-feature">`imap-trace`</a>         | `imap` feature                                   | Connection trace logs on the `trace` logging level   |
| <a name="jmap-trace-feature">`jmap-trace`</a>         | `jmap` feature                                   | Connection trace logs on the `trace` logging level   |
| <a name="nntp-trace-feature">`nntp-trace`</a>         | `nntp` feature                                   | Connection trace logs on the `trace` logging level   |
| <a name="smtp-trace-feature">`smtp-trace`</a>         | `smtp` feature                                   | Connection trace logs on the `trace` logging level   |

Though not a feature, the presence of the environment variable `UNICODE_REGENERATE_TABLES` at compile-time of the `melib` crate will force the regeneration of Unicode tables from the crate's `build.rs` script.
Otherwise the tables are already included with the source code, and there's no real reason to regenerate them unless you intend to modify the code or update to a new Unicode version.

## Example: Parsing bytes into an `Envelope`

An `Envelope` represents the information you can get from an email's headers
and body structure. Addresses in `To`, `From` fields etc are parsed into
`Address` types.

```rust
use melib::{email::attachment_types::Text, Attachment, Envelope};

let raw_mail = r#"From: "some name" <some@example.com>
To: "me" <myself@example.com>
Cc:
Subject: =?utf-8?Q?gratuitously_encoded_subject?=
Message-ID: <h2g7f.z0gy2pgaen5m@example.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; charset="utf-8";
 boundary="bzz_bzz__bzz__"

This is a MIME formatted message with attachments. Use a MIME-compliant client to view it properly.
--bzz_bzz__bzz__

hello world.
--bzz_bzz__bzz__
Content-Type: image/gif; name="test_image.gif"; charset="utf-8"
Content-Disposition: attachment
Content-Transfer-Encoding: base64


ouiijDaaCCGQRgrpH3q4QYYXWDihxBE+7KCDDjnUIEVAADs=
--bzz_bzz__bzz__--"#;

let envelope = Envelope::from_bytes(raw_mail.as_bytes(), None).expect("Could not parse mail");
assert_eq!(envelope.subject().as_ref(), "gratuitously encoded subject");
assert_eq!(envelope.message_id(), "h2g7f.z0gy2pgaen5m@example.com");
assert_eq!(&envelope.message_id().display_brackets().to_string(), "<h2g7f.z0gy2pgaen5m@example.com>");

let body = envelope.body_bytes(raw_mail.as_bytes());
assert_eq!(body.content_type().to_string().as_str(), "multipart/mixed");

let body_text = body.text(Text::Plain);
assert_eq!(body_text.as_str(), "hello world.");

let subattachments: Vec<Attachment> = body.attachments();
assert_eq!(subattachments.len(), 3);
assert_eq!(
    subattachments[2].content_type().name().unwrap(),
    "test_image.gif"
);
```
