Skip to content

Conversation

@nevans
Copy link
Collaborator

@nevans nevans commented Nov 7, 2020

This fixes e.g.:

RUBY0004 OK [READ-WRITE] [Gmail]/Sent Mail selected. (Success)

Specifically, "text" is allowed to begin with "[" or "=". Excluding those was a an older RFC 2060 restriction.

(RFC 2060 was written in 1996. RFC 3501 in 2003) 🙂

@nevans nevans changed the title Fix text response and resp text rfc3501 Fix text_response and resp-text Nov 8, 2020
@nevans nevans force-pushed the fix-text_response_and_resp_text-RFC3501 branch from 208670b to 9e36561 Compare December 7, 2020 08:53
This could lead to unexpected bugs if `@next_token` was filled using one
parser and lookahead is called with an incompatible parser, so I've made
that an error.  All matches that set lex_state should be immediately
preceded by a "match" or "shift_token".

Probably better would be to push/pop on a `lex_state` stack.
These are mostly useful when violating the RFCs, in order to workaround
servers that violate the RFCs.
This encapsulates the `@lex_state` change.
Specifically, "text" is allowed to begin with "[" or "=". Disallowing
that was an older RFC2060 restriction.

(RFC 2060 was written in 1996. RFC 3501 in 2003)  :)
@nevans nevans force-pushed the fix-text_response_and_resp_text-RFC3501 branch from 9e36561 to d3566cb Compare December 10, 2020 23:21
@shugo
Copy link
Member

shugo commented Mar 9, 2021

@nevans I've merged it manually. Thank you!

@shugo shugo closed this Mar 9, 2021
@nevans nevans deleted the fix-text_response_and_resp_text-RFC3501 branch March 10, 2021 18:18
@nevans nevans added the IMAP4rev1 Requirement for IMAP4rev1, RFC3501 label Feb 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

IMAP4rev1 Requirement for IMAP4rev1, RFC3501

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants