Releases: djc/tokio-imap
Releases · djc/tokio-imap
imap-proto 0.13.0
imap-proto 0.12.0
imap-proto 0.11.0
This release contains numerous internal improvements and some hopefully minor API changes.
imap-proto 0.10.2
tokio-imap 0.5.0
- Upgrade to tokio 0.2 final release
- Remove some unused dependencies
- Upgrade to latest imap-proto
imap-proto 0.10.0
This release contains one incompatible change: all fields of the Address
type as well as some fields of the Envelope
type are now &[u8]
instead of &str
. It turns out that parsing these as UTF-8 was, unfortunately, too restrictive for parsing messages in the wild. Thanks to @link2xt for investigating and fixing this.
- Allow arbitrary bytes for some string fields (#63, thanks to @link2xt)
- Allow invalid continuation responses as seen from Yandex (#68, thanks to @dignifiedquire)
imap-proto 0.9.1
- Added support for the RFC 5464 METADATA extension (#59, thanks to @Sergey-Kitov)
- Fixed a regression in number parsing (introduced in 0.9.0)
- Added a
Clone
impl forRequest
tokio-imap 0.5.0-alpha.1
- Initial support for async/await
- Use rustls as the underlying TLS implementation
- Simplify the
ImapTransport
abstraction
imap-proto 0.9.0
- Corrected parser to allow non-uppercase keywords (thanks to @avitex and @link2xt)
- Upgraded to nom 5 (thanks to @marcusklaas)
imap-proto 0.8.1
- Add support for BODYSTRUCTURE (#48, thanks to @avitex)
- Implement missing response codes (#41, thanks to @Emm54321)
- Parse capabilities into an enum (#47, thanks to @marcelbuesing and @avitex)
- Fix parsing of RFC 3501 test envelope (#39, thanks to @marcelbuesing)
(0.8.0 was skipped due to an error in the crate metadata.)