You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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. #32LOGINDISABLED, #48AUTH=). And many other extensions require the client to keep track (e.g. #37LITERAL-). And the parser will also need to be able to "enable" different behavior for some extensions (e.g. BINARY, UTF8=ACCEPT, IMAPrev2).
Activity
[-]cache and add[/-][+]cache capabilities and add capability?(name)[/+]✨ Add greeting code data to responses
✨ Add greeting code data to responses
✨ Add greeting code data to responses
✨ Add greeting code data to responses
✨ Cache server capabilities; add #capable?(name)
✨ Cache server capabilities; add #capable?(name)
✨ Cache server capabilities; add #capable?(name)
✨ Cache server capabilities; add #capable?(name)
✨ Cache server capabilities; add #capable?(name)
✨ Cache server capabilities; add #capable?(name)
✨ Cache server capabilities; add #capable?(name)
✨ Cache server capabilities; add #capable?(name)
✨ Cache server capabilities; add #capable?(name)
✨ Cache server capabilities; add #capable?(name)
✨ Cache server capabilities; add #capable?(name)
✨ Cache server capabilities; add #capable?(name)
✨ Add cached #capabilities, #capable?(name), etc
✨ Add cached #capabilities, #capable?(name), etc
✨ Add cached #capabilities, #capable?(name), etc
✨ Add cached #capabilities, #capable?(name), etc
[-]cache capabilities and add capability?(name)[/-][+]cache capabilities and add `#capability?(name)`[/+]