1741519 - RFE: confidentiality classification (msip_labels)

Status: UNCONFIRMED

(Thunderbird :: Message Compose Window, enhancement)

Description

[Valerio Messina]

Attachment: Outlook_confidentiality_classification.png

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 SeaMonkey/2.53.9.1

Steps to reproduce:

Thunderbird 91 on Win10 64-bit

Companies started to require a confidentiality classification for all emails.
This is generated by the O365 Outlook icon in compose email, see attached image.
As now in our company we use three levels: Public, Internal, and Confidential.
In terms of standard email protocol, Outlook add e new header line as so:

msip_labels:
MSIP_Label_<hash00>_ActionId=<hash01>;MSIP_Label_<hash00>_ContentBits=0;MSIP_Label_<hash00>_Enabled=true;MSIP_Label_<hash00>_Method=Privileged;MSIP_Label_<hash00>_Name=<NAME>;MSIP_Label_<hash00>_SetDate=2021-11-16T09:18:33Z;MSIP_Label_<hash00>_SiteId=<hash02>;

where:

<hash00> is same for all email of a kind, eg. every Confidential email has the same hash.
<hash01> is different for each email
<hash02> is always the same for every company plant
<NAME> is the selected level
and the ISO8601dateTtimeZ is set on email sent time

so this is not a difficult hack

Actual results:

The Thunderbird Security Icons add the ability of sign and encrypt emails, but no classification.

Expected results:

Thunderbird compose email, in Security menù, should has the option to classify the emails, that add the header described above.
Maybe a dialog box to enter the <hash02> and a configurable list of couples "name","<hash00>" to be general. A default level should be selectable

Comment 1

[Valerio Messina]

all hashes are in the form: 'hhhhhhhh-hhhh-hhhh-hhhh-hhhhhhhhhhhh'

Comment 2

[chrizilla]

could be dupe of Bug 353800

Comment 3

[Magnus Melin [:mkmelin]]

This one is about the MS version. I don't know if that's using the standard.

Comment 4

[chrizilla]

message composition

If I understand correctly, according to the reporter Outlook uses non-standard* header fields (MSIP labels) for confidentiality classification – not the standard Sensitivity header field, for which bug 353800 requests support.
*I didn't find MSIP labels in RFC 4021 nor in its updates.

Under "expected results" reporter requests to "add the header described above" (i.e. the non-standard MSIP labels) for message composition. The bug title says as much. However I would assume that if Thunderbird implements an email confidentiality classification, it will use the standard header field requested in bug 353800 rather than the non-standard approach requested here. (Or should TB add both headers simultaneously ?)

message display

On the other hand, as far as only message display is concerned, it could be nice-to-have (for enterprises) if TB were able to understand and display the Outlook confidentiality classification.
This is not explicitly what comment #0 requests, but the bug could be adapted towards that end?

Comment 5

[Valerio Messina]

If we want TB substitute outlook in enterprise confidentiality become a must.
Can you please add "parity-Outlook" tag?