Tokio-based IMAP implementation
APACHE-2.0 License
Bot releases are hidden (Show)
Cow
is used in many places to avoid unnecessary allocations (#115, thanks to @jonhoo)BodyStructure
type (#111, thanks to @yageek and @mmirate)Published by djc almost 4 years ago
imap-proto 0.12.0 is a minor feature release, which essentially adds support for one new IMAP extension response:
Published by djc about 4 years ago
This release contains numerous internal improvements and some hopefully minor API changes.
HEADER.FIELDS
(#72, thanks to @link2xt)Published by djc over 4 years ago
This is a small maintenance release (I erroneously published 0.10.1 incompletely).
HEADER.FIELDS
(fixed in #72, thanks to @link2xt)Published by djc almost 5 years ago
Published by djc almost 5 years ago
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.
Published by djc almost 5 years ago
ImapTransport
abstractionPublished by djc almost 5 years ago
Clone
impl for Request
Published by djc about 5 years ago
Published by djc about 5 years ago
(0.8.0 was skipped due to an error in the crate metadata.)
Published by djc almost 6 years ago
LIST
/LSUB
delimiters optional (fixes #33)RFC822.TEXT
(fixes #32)LSUB
and LIST
response types (thanks to @jonhoo)Published by djc almost 6 years ago
tokio-imap hasn't gotten a lot of attention, but here is a release with accumulated small improvements and fixes. The motivating issue for this release was a fix to remove unsafe API:
transmute
(fixes #30, thanks to @ExpHP for reviewing). tokio-imap has one instance of unsafe
to build an efficient and ergonomic response type. Unfortunately this code exposed a field as public that shouldn't have been, making it possible to cause invalid data. Normal usage of the API should still be safe, but everyone is advised to upgrade to this release.Other changes:
Published by djc almost 6 years ago
Unfortunately the new StatusAttribute::HighestModSeq
value type was wrong in the 0.5.0 release, so here's a follow-up release with a higher minor version number to prevent any confusion. Sorry for the inconvenience!
HighestModSeq
type to u64
(thanks to @dario23 for #29)Published by djc almost 6 years ago
This is a new minor release version due to an added enum variant in StatusAttribute
and the upgrade to nom 4 (which affects error types for parsing). Otherwise, the API is unchanged from before.
HIGHESTMODSEQ
status attributes to improve compatibility with Dovecot server (#28, thanks to @dario23)INBOX
folder namesPublished by djc almost 6 years ago
RFC822.HEADER
(see #11)Published by djc over 6 years ago
The imap-proto crate has been merged into the tokio-imap repository (again). To be precise, tokio-imap commit 4a024f3d7a59550179f74c2737ddf1272c04f188 merges the imap-proto code as of 522f84d. The later commit 4ecd2f5fabbcd0e4d8e262832cf0b96d4003d62c was merged in 09848b9121cdcbbb64e1313b502094239c2fca44.