After ENABLE, IMAP4rev2 human-readable response text can include non-ASCII encoded in UTF-8. #109

New issue

Copy link

New issue

Copy link

Closed

#111

Closed

After ENABLE, IMAP4rev2 human-readable response text can include non-ASCII encoded in UTF-8.#109

#111

Copy link

Description

nevans

opened on Feb 12, 2023

Issue body actions

The issue title comes from IMAP4rev2, Appendix E, 24.
See RFC9051 Section 9, for the formal syntax.

Reactions are currently unavailable

Activity

1. nevans

   closed this as completedin #111on Feb 12, 2023
2. nevans

   added a parent issue on Oct 16, 2025

   • Support for IMAP4rev2 and modern extensions #12
3. nevans

   removed a parent issue on Oct 16, 2025

   • Support for IMAP4rev2 and modern extensions #12
4. nevans

   added a parent issue on Oct 16, 2025

   • RFC6855 (2013): UTF8=ACCEPT (recommended by IMAP4rev2 for backward compatibility) #38

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

Labels

No labels

No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

• Open in GitHub Copilot app