Skip to content

cache capabilities and add #capability?(name) #31

Closed

Description

@nevans

The client should keep track of server CAPABILITY responses and response codes. And it should invalidate previously cached values at the appropriate times (e.g. after STARTTLS).

The base spec requires this: (e.g. #32 LOGINDISABLED, #48 AUTH=). And many other extensions require the client to keep track (e.g. #37 LITERAL-). And the parser will also need to be able to "enable" different behavior for some extensions (e.g.
BINARY, UTF8=ACCEPT, IMAPrev2).

Activity

  1. changed the title [-]cache and add[/-] [+]cache capabilities and add capability?(name)[/+] on Nov 23, 2021
  2. added 16 commits that reference this issue on Jul 16, 2023
    e7ca896
    4d26793
    75043c8
    474fdbe
    1497b24
    76a3d87
    c183d7c
    383761f
    10420eb
    27554f6
    d611853
    452f10f
    ecc6bd1
    7ed848d
    d4ea5d8
    b0f8b9e
  3. changed the title [-]cache capabilities and add capability?(name)[/-] [+]cache capabilities and add `#capability?(name)`[/+] on Oct 16, 2025
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

    IMAP4rev1Requirement for IMAP4rev1, RFC3501

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions