Opened 9 years ago

Last modified 9 years ago

#3951 enhancement new

IMAP4Server: Add support for PERMANENTFLAGS response from SELECT and EXAMINE

Reported by: Ilpo Nyyssönen Owned by:
Priority: normal Milestone:
Component: mail Keywords:
Cc: Jean-Paul Calderone Branch:
Author:

Description

SELECT: http://tools.ietf.org/html/rfc3501#section-6.3.1 EXAMINE: http://tools.ietf.org/html/rfc3501#section-6.3.2

http://tools.ietf.org/html/rfc3501#section-7.1

PERMANENTFLAGS

Followed by a parenthesized list of flags, indicates which of the known flags the client can change permanently. Any flags that are in the FLAGS untagged response, but not the PERMANENTFLAGS list, can not be set permanently. If the client attempts to STORE a flag that is not in the PERMANENTFLAGS list, the server will either ignore the change or store the state change for the remainder of the current session only. The PERMANENTFLAGS list can also include the special flag \*, which indicates that it is possible to create new keywords by attempting to store those flags in the mailbox.

Change History (3)

comment:1 Changed 9 years ago by Jean-Paul Calderone

Cc: Jean-Paul Calderone added
Owner: changed from Jean-Paul Calderone to Ilpo Nyyssönen

Okay. That's a good description of what PERMANENTFLAGS is. What is this ticket for, though? The more descriptive you can be, the more likely it is that someone won't close it as invalid. Providing a failing unit test which exactly demonstrates the behavior you're looking for would be idea.

comment:2 Changed 9 years ago by Ilpo Nyyssönen

Owner: changed from Ilpo Nyyssönen to Jean-Paul Calderone

The problem is that my client (Gnus) does not store flags to the server without that and uses a local storage instead.

comment:3 Changed 7 years ago by <automation>

Owner: Jean-Paul Calderone deleted
Note: See TracTickets for help on using tickets.