install.rdf

<?xml version="1.0"?>
<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:em="http://www.mozilla.org/2004/em-rdf#">
  <Description about="urn:mozilla:install-manifest">
    <em:id>sensitivity_header_management@ff_bob.bob</em:id>
    <em:name>Sensitivity Header</em:name>
    <em:description>Implement the "Sensitivity" header for outgoing messages (described in RFC 4021 section 2.1.55).</em:description>
    <em:version>0.2</em:version>
    <em:type>2</em:type>
    <em:creator>Andrew H</em:creator>
    <em:developer>Andrew H</em:developer>
    <em:iconURL>chrome://sensitivity_header_management/content/identity.png</em:iconURL>

    <em:targetApplication>
      <Description>
        <em:id>{3550f703-e582-4d05-9a08-453d09bdfdc6}</em:id> <!-- Thunderbird -->
        <em:minVersion>37.0</em:minVersion>
        <em:maxVersion>43.0</em:maxVersion>
      </Description>
    </em:targetApplication>

    <em:targetApplication>
      <Description>
        <em:id>{92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}</em:id> <!-- Seamonkey -->
        <em:minVersion>2.33</em:minVersion>
        <em:maxVersion>2.39</em:maxVersion>
      </Description>
    </em:targetApplication>

<!--
Description for addons.mozilla.org
==================================

This simple addon currently allows the user to add a sensitivity indicator ('Personal/Private/Company-Confidential') to an outgoing message via an option in the tools menu, or from an optional drop-down toolbar menu (similar to message priority).
While adding this header does not directly add any security to the message, the header can be interpreted by some MTA/MUAs such that the message is treated differently while in transit, or when viewed by the recipient:
<ul><li>e.g. MS Outlook/Exchange: Can be set so that confidential/personal messages are unable to be read by the recipient's delegated users; A warning can be displayed before the message is forwareded; Displays an advisory message above content.
<li>e.g. Some versions of Symantec PGP in corporate set-ups can automatically encrypt the outgoing message if leaving the corporate network, or redirect it to a secure corporate webmail page (with an automated notification email to the recipient to collect it there).</ul>
Please note that other MTA/MUA software (e.g. Popular webmail systems, Thunderbird without this add-on) may <i>completely ignore</i> the header as it is not commonly used outside of corporate environments.  Therefore, please do not solely rely on it for ensuring your message is treated as intended.
<strong>Known Issues</strong>
When re-opening a draft message where a sensitivity was set, the previous value is not currently retained.  Similarly, when forwarding or replying to a message, the sensitivity value from the original message is not currently retained.  As such, please make sure to select the correct sensitivity before sending your messages - if you add the toolbar item, this is always visible when composing.  I hope to find a fix for these issues in a future version.
This addon does not currently show an indicator for received messages yet - In future versions of this addon, I may add some kind of (optional) banner above the message when the header is set to Personal/Private/Confidential.  In the meantime, if the header has been set on any message, it will be visible if 'View Menu -> Headers -> All' is ticked.
If you're familiar with Thunderbird addon development or can help with translations, and would like to help out, please get in touch (ahumph yahoo com).


Development Plan
================
TODO: When editing a draft, or replying to a message with this header, make the header in the new message the same.
TODO: Add the toolbar item automatically on install.
TODO: Display an (optional) banner above received message (if header is set to priv/pers/conf).
TODO: Automatically add the header to the searchable headers list. (and remove it on uninstall).
    //user_pref("mailnews.customHeaders", "Sensitivity"); // ADD it to list of searchable message fields.
TODO: Keep UI strings localised where possible.
TODO: When the selected sensitivity is 'normal' when composing, remove the custom header completely.
-->

    <!--<em:icon64URL>chrome://sensitivityheadermanagement/content/identity.png</em:icon64URL>-->

    <!--
    <em:localized>
      <Description>
        <em:locale>en-GB</em:locale>
        <em:translator>Bob</em:translator>
        <em:name>Sensitivity Header</em:name>
        <em:description>Partially implements the "Sensitivity" header described in RFC 4021.</em:description>
      </Description>
    </em:localized>
    <em:contributor>Bob</em:contributor>      
    <em:optionsURL>chrome://myext/content/options.xul</em:optionsURL>
    <em:multiprocessCompatible>false</em:multiprocessCompatible>
    <em:unpack>false</em:unpack>      
    -->
  </Description>
</RDF>