Lyndon Nerenberg wrote: > > On Friday, July 11, 2003, at 03:14 PM, Alexey Melnikov wrote: > > > > Lyndon Nerenberg wrote: > > > >> $Work, $Personal: > >> > >> Is there a need to standardize these? It seems to me that the > >> reason for $* flags is to ensure functional compatibility > >> between clients. I cannot think of any functionality that > >> would > >> be triggered by these flags. > > > None. The same is even true for $Junk/$NotJunk. > > Not at all. $NotJunk triggers some very specific functionality (in > the case of the Darwin Mail client): it tells the client's junkmail > filter to not flag the message as junkmail. $Junk also triggers > specific functionality: it allows the client to modify its behaviour > - - e.g., to not display the message in the default folder view. It is > for this very reason that we are defining these flags. > > > $* flags are not necessarily about automatic processing, they are > > about special client behavior or special handling by the server. > > Well, you just contradicted yourself.
No, I just wasn't precise enough when I used the term "automatic processing". I was referring to anything but grouping/hiding messages. (This is not exact definition either, but I hope you understand what I mean now). > Maybe you need to think about > the framework some more, and decide what specific problem it is that > you are trying to address. I would like to group (or mark with color) messages. > ... > > $Important > > > > This section attempts to define both the Priority and > > X-Priority > > RFC 2822 headers. This is completely out of scope for this > > document > > > > I don't mind reference an existing document. > > I don't understand this. What document are you referring to? draft-palme-mailext-headers-08.txt > > (and simply cannot be done in the case of X-Priority). > > Most things can be done :-). > > Are you suggesting that we start standardizing X- mail headers? > > > > This flag is supposed to be automatically settable by the server > > (delivery agent or IMAP), so it has to document which headers are to be > used. > > No it does not, and it cannot. We can define what it means when the > flag is set, but just as with $Adult, no two people will ever share > the exact same definition of what makes a message $Important to begin > with. $Important is similar to $AutoJunk as described by Chris Newman. Its is fine if the server auto-sets it on mail injection, but the end user can always change the value after. > (And speaking personally, I would *NEVER* implement a mechanism > that would let someone else set this flag for me.) Alexey
