170247 - Labeling results in error message: UID STORE failed: Unknown flag $LABEL

Status: RESOLVED EXPIRED

(MailNews Core :: Networking: IMAP, defect)

Description

[Ben Ruppel]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20020921
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20020921

Hi, I'm using an IMAP connection to my school email.  When I try to label a
message, I get the following error:
"The current command did not succeed.  The mail server responded: UID STORE
failed: Unknown flag: $LABEL3."

This has been happening alost since Labels were first implemented.  I ignored it
hoping it would go away, but it is still here and there are no dupes that I've
found.

Reproducible: Always

Steps to Reproduce:
1.open IMAP inbox
2.assign a label to a message
Actual Results:  
error result happens (label is still assigned as far as I can tell)

Expected Results:  
no error message.  Or a way to turn off the error message.  I'm not sure if
something should be happening that isn't... I suppose MailNews is trying to tell
the server about the label and the server is rejecting the data.  In this case,
I don't think I should get the error for every single label I ever assign.

Comment 1

[laurel]

*** This bug has been marked as a duplicate of 125736 ***

Comment 2

[laurel]

Reporter states in bug 125736 that the problem still occurs, different error.
I'm not sure if the other bug was meant to cover varied server types.  Reopening
as I clumped it together with the other bug.

Maybe the best thing to do is attach a protocol log of the error:
http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap

Comment 3

[Ben Ruppel]

Attachment: Log showing failure I am now getting

Okay, so with today's build I am getting "path not found" instead of the error
I had posted in the summary of this bug.

Comment 4

[Ben Ruppel]

Attachment: Imap log file with both kinds of errors

Sorry, that previous attachment had an error message generated by running a
filter to label messages.  It resulted in a different error than what I had
reported.

When I manually labeled a message, I got the error as reported in the bug
summary.  The attached log file contains both errors: the first one from using
a filter, the second from manually assigning a label.

Comment 5

[David :Bienvenu]

from what I can see, your sun imap server is lying to us - it says it supports
user-defined keywords (it returns \* in permanent flags), then it complains when
we try to set a user-defined keyword.

I'm not sure about the bad path - that seems like a problem on our end, and I
suspect, as you say, a filter is triggering it, but I'm not sure it's a label
filter. We're trying to select the empty string as a folder name, and that won't
work. I'm not sure why we think we need to select an empty folder name.

Comment 6

[Ben Ruppel]

Hmm, okay, I'll try to talk to the email administrator.

Comment 7

[Ben Ruppel]

Talked to the tech support people.  They said they tried it and got the same
results, and that they'd look into it.  Hate to say it, but I'm not holding my
breath.  

Is there a way, in the meantime, that I could change a setting so that I don't
get a popup warning everytime a filter picks something up?  (I'm addicted to the
junkmail filter)

Comment 8

[Mike Cowperthwaite]

xref bug 142703

Comment 9

[Gervase Markham [:gerv]]

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/

Comment 10

[Gervase Markham [:gerv]]

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.