Closed
Bug 125736
Opened 23 years ago
Closed 23 years ago
Setting labels on IMAP servers that don't support user keywords generates invalid protocol
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: Bienvenu, Assigned: Bienvenu)
References
Details
(Keywords: imap-interop, regression)
Attachments
(1 file)
771 bytes,
patch
|
naving
:
review+
sspitzer
:
superreview+
|
Details | Diff | Splinter Review |
Assignee | ||
Comment 1•23 years ago
|
||
spun off from comment added to http://bugzilla.mozilla.org/show_bug.cgi?id=114379
This fix has introduced a new problem. I get an alert everytime I label a
message that says
'The current command did not succeed. The mail server responded: "Specified set
of flags is not valid"'
Using Microsoft Exchange as IMAP server.
Fix upcoming - the problem was that we were checking if the server supported
user flags, but if it didn't, labeling would result in sending a store command
with no flags. cc'ing Navin for review of upcoming patch.
Status: NEW → ASSIGNED
Keywords: interop,
regression
Summary: IM → Setting labels on IMAP servers that don't support user keywords generates invalid protocol
Assignee | ||
Comment 2•23 years ago
|
||
Comment 3•23 years ago
|
||
Comment on attachment 69681 [details] [diff] [review]
proposed fix
sr=sspitzer
Attachment #69681 -
Flags: superreview+
Comment 4•23 years ago
|
||
Comment on attachment 69681 [details] [diff] [review]
proposed fix
r=naving
Attachment #69681 -
Flags: review+
Assignee | ||
Comment 5•23 years ago
|
||
fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 6•23 years ago
|
||
*** Bug 126028 has been marked as a duplicate of this bug. ***
Updated•23 years ago
|
QA Contact: huang → meehansqa
Comment 7•23 years ago
|
||
Tested on the Microsoft Exchange IMAP server on 5/20/02, using the 5/15 branch
build. Working correctly, I am able to label and unlable messages with no errors.
Status: RESOLVED → VERIFIED
Keywords: verified1.0.0
*** Bug 170247 has been marked as a duplicate of this bug. ***
Comment 9•23 years ago
|
||
Could someone please look at the comments in bug 170247? The error I get is
slightly different, and I just tried this last week and it is not fixed (while
this bug was fixed in 2002). Does anyone know how I can tell what type of
server my mail server is (I doubt it is exchange).
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•