search

duesee / imap-codec

Rock-solid and complete codec for IMAP
Apache License 2.0
37 stars 14 forks source link

misuse: Resolve `Code` ambiguity (again). #301

Closed duesee closed 1 year ago

duesee commented 1 year ago

The workaround we used before produces parsing errors. We could add a guard for Arbitrary that prevents code: None, text: "[CODE] ..." and add a note in the documentation.

Related: #184

duesee commented 1 year ago

Closed by #300 for now.

duesee commented 10 months ago

From the (now offline) imap-protocol mailing list:

I'm working on some IMAP client code, and hit the following portion of ABNF grammer in RFC 3501:

resp-text = ["[" resp-text-code "]" SP] text

Should the following lines be considered protocol errors?

  • NO [UNSEEN]
  • NO [TRYCREATE
  • NO [FOO(BAR)]

The resp-text rule says "[" must have a matching "]" and the resp-text-code rule says UNSEEN must be followed by a nz-number and the the first word after the [ must be an atom, so they would appear to be errors.

However, the first part of resp-text is optional, so should these just be considered to have text ("[UNSEEN]", "[TRYCREATE", and "[FOO(BAR)]" and no response code?

Thanks. Peter

On Fri, 27 Jul 2007, Peter Bowen wrote:

However, the first part of resp-text is optional, so should these just be considered to have text ("[UNSEEN]", "[TRYCREATE", and "[FOO(BAR)]" and no response code?

Yes.

-- Mark --

http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum.