//! The new-tokio-smtp crate provides an extendible SMTP (Simple Mail Transfer Protocol)
//! implementation using tokio.
//!
//! This crate provides _only_ SMTP functionality, this means it does neither
//! provides functionality for creating mails, nor for e.g. retrying sending
//! a mail if the receiver was temporary not available.
//!
//! This crate can be seen from two perspectives:
//!
//! 1. a normal API user, mainly bothering with `ConnectionConfig`, `Connection`
//! and `Cmd` implementations (in the `command` module)
//!
//! 2. a cmd implementation, having to use `Io`, `Socket` etc.
//!
//! # Features
//!
//! ## `send_mail`
//!
//! While still not handling the creation/encoding of mails if this feature is
//! enabled a `send_mail` command is added `Connection` which combines the steps
//! of sending the `MAIL` command, the `RCPT` command and the `DATA` command.
//!
//! ## `mock-support`, `mock-impl`
//!
//! Extend the `Socket` abstraction to include a mock socket additional to `Tcp`, `TcpTls`.
//! Also provides a mock socket implementation for simply testing commands. Custom implementations
//! can be provided too if needed for testing
//!
// I use `{ ...; let fut = ...long multi line; fut }` a lot for better readability.
// it also makes it so much easier to wrap the return value into a `dbg!`, `Box::new` and similar.
extern crate futures;
extern crate base64;
extern crate bytes;
extern crate hostname;
extern crate native_tls;
extern crate rand;
extern crate tokio;
extern crate tokio_tls;
extern crate vec1;
// order of modules is also "order" in dependency-tree
// i.e. module should only import from modules hither
// up in the list
pub use *;
pub use *;
pub use *;
pub use *;
pub use Io;
pub use Response;