Closed
Bug 187156
Opened 22 years ago
Closed 18 years ago
Default priority for outgoing messages should be Normal, not none
Categories
(MailNews Core :: Composition, defect)
MailNews Core
Composition
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bugzilla, Unassigned)
Details
The default priority for outgoing mail messages should be "Normal", or
"X-Priority: 3". Currently Mozilla and Netscape only apply a priority to
outgoing mail messages if it is changed to something other than Normal. If the
priority is not changed, rather than using Normal priority for the message, no
priority header is used.
Comment 1•22 years ago
|
||
Re Description:
I would think that the current behaviour is fine:
assuming blank/none = default = 'Normal'.
Why do you think that it is needed/important to add 'Normal' Priority explicitly ?
Reporter | ||
Comment 2•22 years ago
|
||
Equivalency to other programs. Outlook, for example, uses Normal priority for
all outgoing messages unless changed. No priority does equal "default" which
is "normal", but normal should be defined. This seems to be standard on most
other programs. The current behavior is not that 'no priority selected' equals
"normal" but instead that there is no message priority.
Updated•20 years ago
|
Product: MailNews → Core
Comment 3•18 years ago
|
||
is there a spec that says how it should work?
does it cause a problem for any email clients?
Assignee: ducarroz → nobody
QA Contact: esther → composition
Comment 4•18 years ago
|
||
X-Priority is a non-standard header, introduced by Eudora. It's mentioned in the proposed update to RFC 2076, draft-palme-mailext-headers-08.txt[1]. The default value is 3/normal, so any mail without that header is supposed to have normal priority. There's no use in explicitly setting this, albeit we have to understand it on incoming mail.
[1] http://www.dsv.su.se/~jpalme/ietf/mail-headers/mail-headers.html
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
Assignee | ||
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
•