Closed Bug 140810 Opened 23 years ago Closed 19 years ago

IMAP assumes lack of permanentflags means read-only

Categories

(MailNews Core :: Networking: IMAP, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: brer, Assigned: mscott)

Details

Ran into this problem trying to delete messages on the IMAP mail server implemented for our home. Recently, it was changed so that in response to a SELECT command it doesn't send PERMANENTFLAGS to save bandwidth. Mozilla seems to assume that a lack of a PERMANENTFLAGS response means that all flags are read-only. This is not the way the IMAPv4 spec says that the flags should be interpreted. From RFC2060, section 6.3.1 SELECT Command: "If the client can not change the permanent state of one or more of the flags listed in the FLAGS untagged response, the server SHOULD send a PERMANENTFLAGS response code in an OK untagged response, listing the flags that the client can change permanently." This implies that if all flags are modifiable, then no PERMANENTFLAGS response is necessary.
This could also be part of the problem seen in bug 61816.
My symptom was that deleted messages would disappear, but would reappear after certain operations, like get new messages. I should add that Apple's Mail, MS Entourage v.X, and Outlook Express on Windows work just fine in such a setup.
OS: MacOS X → All
Hardware: Macintosh → All
QA Contact: huang → gchan
Product: MailNews → Core
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.