Refactor IMAP code into a distinct crate #140
Labels
No Label
IMAP
JMAP
Maildir
Retired
User Experience
User Interface
bsd
bug
contacts
currently worked on
documentation
duplicate
easy
enhancement
help wanted
invalid
linux-gnu
macos
mbox
notmuch
question
security
wishlist
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: meli/meli#140
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
This one's probably way more complicated, but let's refactor the IMAP client code into sub-crates, possibly even moving it to another repo so that they could be reused elsewhere conveninently.
Current options for IMAP client libs:
tokio
)async_std
)/cc @epilys
Closing this, unless someone wants to pick it up.