Giters
djc
/
tokio-imap
Tokio-based IMAP implementation
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
118
Watchers:
11
Issues:
48
Forks:
42
djc/tokio-imap Issues
Release imap-proto 0.16.4
Closed
2 months ago
Why is Client's public API so restrictive? (i.e hardcoded port, unable to opt out of TLS, etc)
Updated
2 months ago
Comments count
5
RFC 9266: Channel Bindings for TLS 1.3 support
Updated
3 months ago
Comments count
1
SCRAM-SHA-1(-PLUS) + SCRAM-SHA-256(-PLUS) + SCRAM-SHA-512(-PLUS) + SCRAM-SHA3-512(-PLUS) supports
Updated
3 months ago
Comments count
1
Parser subscription is probably missing.
Closed
8 months ago
Comments count
4
support IMAP4 ID extension (rfc2971)
Closed
a year ago
Comments count
3
Implementing a more generic interface
Updated
2 years ago
Comments count
3
Missing references attribute in Envelope struct
Closed
3 years ago
Comments count
9
Shouldn't "Sender" be a single string of the Envelope-Struct?
Closed
3 years ago
Comments count
4
[Question] Difference between Sender and From from Envelope
Closed
3 years ago
Comments count
2
Dependabot can't resolve your Rust dependency files
Closed
3 years ago
[Suggestion] RFC 5256 - SORT command
Closed
3 years ago
Comments count
5
Store borrowed fields using `Cow`
Closed
3 years ago
Comments count
2
Missing ResponseCode: LONGENTRIES from METADATA extension
Closed
3 years ago
Comments count
2
Retrieve the SectionPath of one BodyStructure
Closed
3 years ago
Comments count
8
Support parsing RFC 4315 (UIDPLUS Extension) response codes
Closed
3 years ago
Comments count
1
Make a new release of imap-proto
Closed
4 years ago
Comments count
2
Enforce recursion limits
Updated
4 years ago
Comments count
1
General question about safe string handling.
Closed
4 years ago
Comments count
2
Deal with upstream `StateStream` change
Closed
4 years ago
Comments count
4
`quoted_data` should return `Needed::Unknown` until no unescaped " found
Closed
4 years ago
Comments count
7
Narrowing down rustfmt skip yields unformatted code.
Closed
4 years ago
Comments count
4
atom_char and text_char accept too much
Closed
4 years ago
Comments count
4
Change the public API
Closed
4 years ago
Comments count
5
Modifying ResponseData / Response
Closed
4 years ago
Comments count
5
Check all uses of nstring_utf8 in imap-parser
Closed
4 years ago
Comments count
2
Handle short continuation response
Closed
4 years ago
Comments count
2
IMAP parser does not allow invalid UTF-8 in literal strings
Closed
4 years ago
Comments count
3
Add API docs
Updated
5 years ago
Comments count
5
New release of imap-proto with #54 fix
Closed
5 years ago
Comments count
2
Capability "IMAP4REV1" is not accepted as valid
Closed
5 years ago
Comments count
1
New release of imap-proto
Closed
5 years ago
Comments count
1
Parse `FETCH ... BODYSTRUCTURE` response
Closed
5 years ago
Comments count
3
support IMAP IDLE/NOTIFY
Updated
5 years ago
Comments count
5
invalid parsing of gmail imap responses
Closed
5 years ago
Comments count
8
Grant licenses of one type exclusively?
Closed
5 years ago
Comments count
2
`UID FETCH` parsing issue?
Closed
5 years ago
Comments count
6
Add tests
Closed
5 years ago
Comments count
3
Don't choke on empty SEARCH response
Closed
5 years ago
Comments count
3
Refine and document Envelope fields
Updated
5 years ago
Comments count
4
Express nullability of LIST delimiter response
Closed
5 years ago
Support parsing RFC822.TEXT
Closed
5 years ago
undefined behavior in safe code with public Response<'static> field
Closed
5 years ago
Comments count
3
Place formal syntax in comments
Updated
6 years ago
Comments count
3
Error parsing HIGHESTMODSEQ that doesn't exist in input stream
Closed
6 years ago
Comments count
4
Use `ToSocketAddrs` in `Client::connect`
Closed
6 years ago
Comments count
6
Refactor glob imports to explicit imports
Closed
6 years ago
Comments count
1