GNOME Bugzilla – Bug 216327
message priority not recognized or settable
Last modified: 2005-04-10 08:16:36 UTC
Description of Problem: Messages with X-Priority set in the header should have some visual indication of relative priority. Also, it would be nice to be able to set this property when composing messages. Steps to reproduce the problem: 1. Send message from another mail client which sets X-Priority header with priority set to "high" or "highest" 2. Receive message with Evolution Actual Results: Message is indistinguishable from other messages of lower priority. Expected Results: I would expect the message to have some visual clue about its priority. How often does this happen? Always Additional Information:
*sigh*...the problem with "priority" is that there is no standard for it. some mail clients support it, others don't. for the ones that do support it, they might use a different format. I think Mozilla uses X-Priority while MS Outlook uses X-MSPriority or something - what does Lotus Notes use? What does Novell GroupWise use? There are plenty of other popular mail clients too - what do they use if anything? And that's only comparing the header fields... I have *no* idea what the values are defined to be. The only way I can think of to find out is to go out and buy all of the popular mail clients and do some trial and error action. there could be an infinite array of possible ways of doing "priority". I personally feel we shouldn't waste our time, priority is pretty meaningless anyway. What gives someone else the right to flag something as important when sending email to me? Shouldn't *I* be the one to decide if it's important or not? The biggest problem I see with priority (the pain I experienced at my last job) was that people start flagging damn near everything as important and the next thing you know, priority has lost it's intended usefullness. marking as future for now -we can decide whether to implement this at some later date.
What Exchange does is this: X-Priority: 1 Priority: Urgent Importance: high
*** bug 205812 has been marked as a duplicate of this bug. ***
this is a duplicate.
Could you please let me know if there was some progress for this feature? After updating from Evolution 1.x to 2.0.2 this seems to be the only real feature missing for me.