Project

General

Profile

Actions

Bug #10112

closed

NET::IMAP fails to parse uid_search/search response with MODSEQ search criteria

Added by plehoux (Philippe-Antoine Lehoux) over 10 years ago. Updated about 10 years ago.

Status:
Closed
Target version:
ruby -v:
ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-darwin13.0]
[ruby-core:64203]

Description

 imap.examine('INBOX')
 imap.uid_search(['MODSEQ', 12345])

NET::IMAP fails to parse uid_search/search response with MODSEQ search criteria (example above), here is the debug output I get from running it on GMAIL.

C: RUBY0002 EXAMINE INBOX
S: * FLAGS (\Answered \Flagged \Draft \Deleted \Seen $Phishing $Forwarded Seen $has_cal $NotJunk receipt-handled NotJunk $NotPhishing $Junk Junk)
S: * OK [PERMANENTFLAGS ()] Flags permitted.
S: * OK [UIDVALIDITY 2] UIDs valid.
S: * 3 EXISTS
S: * 0 RECENT
S: * OK [UIDNEXT 87222] Predicted next UID.
S: * OK [HIGHESTMODSEQ 7667593]
S: RUBY0002 OK [READ-ONLY] INBOX selected. (Success)
C: RUBY0003 UID SEARCH MODSEQ 7666341
S: * OK [HIGHESTMODSEQ 7667593]
S: * SEARCH 87216 87221 (MODSEQ 7667567)
@str: "* SEARCH 87216 87221 (MODSEQ 7667567)\r\n"
@pos: 22
@lex_state: EXPR_BEG
@token.symbol: LPAR
@token.value: "("
Actions

Also available in: Atom PDF

Like0
Like0Like0Like0