197401 - labels are unnecessarily limitted

Status: RESOLVED DUPLICATE of bug 114656

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[K. Richard Pixley]

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

In other mailers, (eg, emacs, etc), I can apply arbitrary labels to a message. 
IMAP also supports this in the mailbox.  And yet, in mozilla, I'm stuck with 5,
randomly colored, predefined labels.  And setting a label in my mailbox does not
produce that same label in other instances of mozilla.  (ie, labels set from
winxp do not show on macosx as they were set).


Reproducible: Always

Steps to Reproduce:
1. open an IMAP account
2. redefine your message labels to be something other than the defaults
3. label a message
4. on a different machine, open that same IMAP account and look for the label on
that message.

Actual Results:  
On the second machine, the message is labelled, but the labels have default names.

Expected Results:  
Mozilla should use the IMAP \flag feature to store labels for IMAP boxes and
should allow an arbitrary number and mixture of flags.  Color display of message
headers should be a separate feature, perhaps set manually, perhaps set via filters.

Comment 1

[Jo Hermans]

Maybe with bug 161482 ?

Comment 2

[K. Richard Pixley]

X-Labels are a different issue.  My interpretation of the IMAP protocol is that
flags are out-of-band data.  There isn't necessarily an association between IMAP
\Flags and "X-Labels" or "X-Keywords" (used by the washington IMAP server) or
the babyl format labels or anything else.  The storage format inside the
messasge is, (and IMO should remain), the business of the server, not the client.

This bug reports the fact that I cannot set the 11th user label on a message and
that I cannot flag the message in my IMAP box as both \Work and also \Important.
 The best I can do with mozilla right now is to flag it "$Label1".

Comment 3

[Daniel Wang]

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