Skip to content
This repository has been archived by the owner on Jul 22, 2019. It is now read-only.

UNSEEN response data not parsed #2

Closed
jonhoo opened this issue Nov 3, 2017 · 1 comment
Closed

UNSEEN response data not parsed #2

jonhoo opened this issue Nov 3, 2017 · 1 comment

Comments

@jonhoo
Copy link

jonhoo commented Nov 3, 2017

As documented in RFC3501 §6.3.1, another valid response to SELECT and EXAMINE is

OK [UNSEEN <n>]

However, this ResponseCode does not yet seem to be supported in resp_text_code.
@djc djc closed this as completed in 16873f9 Nov 11, 2017
@djc
Copy link
Owner

djc commented Nov 11, 2017

Should be better with master!

mattnenterprise pushed a commit to mattnenterprise/rust-imap that referenced this issue Feb 9, 2018
@jonhoo @mattnenterprise
Add structured results for all values using imap-proto (#58)
590b80e 
* First stab at structured types (#28)

Tests currently fail due to djc/imap-proto#2.

LSUB is also broken due to djc/imap-proto#4 (but we don't have tests for
that atm).

* Also parse out RFC822 fetch responses

* Make all the things zero-copy

* Also delegate IntoIterator for ZeroCopy ref

* Fix UNSEEN and LSUB

All tests now pass

* Address @sanmai-NL comments

* Correctly handle incomplete parser responses

* No need for git dep anymore
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@djc @jonhoo