Closed
Bug 100261
Opened 24 years ago
Closed 1 year ago
Enhancement: Use of Outlook-like mail properties like Confidential etc.
Categories
(MailNews Core :: Backend, enhancement)
MailNews Core
Backend
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 353800
Future
People
(Reporter: daniel.koller, Unassigned)
References
(Blocks 1 open bug)
Details
The idea is to support the outlook mail properties, such as personal, private,
confidential; they are usable (in Outlook) like Important, Very Important etc.
As far as I know, these properties are 'proprietary' and they are named with
'X-...'.
I could see no problem to support it, because mail clients, which don't know the
property, are - as far as I know from similar protocols - told to ignore it.
The other side of this is the processing of incoming mails, but perhaps this is
solvable through simple displaying the property; an additional process support
like prohibited printing etc. is not needed - and perhaps outside the focus of
Mozilla.
Kind regards,
Daniel
Updated•24 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•24 years ago
|
Target Milestone: --- → Future
Comment 1•23 years ago
|
||
There is a (limited) way to use additional headers:
Put
user_pref("mail.compose.other.header", "X-someheader");
into your user.js.
Then you can select and fill this header in the message composition window.
Comment 2•21 years ago
|
||
i'd like to put a vote for having these set in the prefs, or at least as a file so that the X- headers are
automatically added. PowerMail and Outlook Express (at least the mac version) both have this
option.
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Assignee: mscott → nobody
QA Contact: esther → backend
| Assignee | ||
Updated•17 years ago
|
Product: Core → MailNews Core
Updated•3 years ago
|
Severity: normal → S3
Updated•1 year ago
|
Blocks: Outlook-Parity
This seems to be a duplicate of bug 353800.
Bug 100261 is the older one of the two but suggests using X-headers, whereas bug 353800's implementation approach is the correct one (proposes to use the dedicated sensitivity header field), so maybe keep the latter and mark the older one as duplicate exceptionally ?
@Wayne Mery: Is it ok to ping you in cases like this (verification of uncertain duplicates) ?
Flags: needinfo?(vseerror)
Comment 4•1 year ago
|
||
Thanks for helping. OK to ping me.
x-headers are on their way out anyway AIUI, so I agree with your assessment.
Flags: needinfo?(vseerror)
@Wayne Mery: Thanks for your supervision. Please tell me if it is solicited too often.
You need to log in
before you can comment on or make changes to this bug.
Description
•