duesee / imap-codec

Rock-solid and complete codec for IMAP

Apache License 2.0

35 stars 13 forks source link

feat: Implement `BINARY` #444

Closed duesee closed 4 months ago

duesee commented 4 months ago

See IMAP4 Binary Content Extension, Collected Extensions to IMAP4 ABNF, and IMAP4 Non-synchronizing Literals.

Note: BINARY and LITERAL+ can both be used. ~{123+}\r\n is valid, too.

TODO

[x] Define literal8 (#445) (needed for #432).

literal8 = "~{" number "}" CRLF *OCTET

[x] Extend append (to allow literal8 as well). (#451)

append /= "APPEND" SP mailbox [SP flag-list] [SP date-time] SP literal8

[x] Extend fetch-att.

fetch-att =/ "BINARY" [".PEEK"] section-binary [partial] /
             "BINARY.SIZE" section-binary

section-binary = "[" [section-part] "]"

partial = "<" number "." nz-number ">"

[x] Extend msg-att-static.

msg-att-static =/ "BINARY" section-binary SP (nstring / literal8) /
                  "BINARY.SIZE" section-binary SP number

[x] Extend resp-text-code.

resp-text-code =/ "UNKNOWN-CTE"

[x] Add Capability::Binary (#451)
[x] Remove #[allow(unused)] for literal8.

Notes

BINARY does not "generically" change how literals work. So, ~{123} must only be used during the cases defined above. Not, e.g., in all astrings.