This preference controls whether "text attachments" (e.g. CSV, HTML or even plain text) should **also** be directly rendered in message body.
> see #35
This commit is a follow-up for d8d79d6c, where we re-introduced this
preference, during a (partial) revert, to workaround the lack of strict
ETP support.
> closes#33
By disabling this preference, we prevented Thunderbird from even asking
whether passwords of new setup mail accounts should be saved or not.
This could be pretty confusing and not handy for daily usage.
Users with _specific_ needs can still unconditionally disable passwords
saving by uncommenting `5003`.
> closes#30
Co-Authored-By: atomGit <atomGit@users.noreply.github.com>
In #24, we wrongly assumed that ETP Strict Mode was available in TB 102 (as it was for FF 102).
This patch aims to workaround this (security) issue by :
* Re-enabling FPI ;
* Re-enabling DNT header ;
* Restoring `network.cookie.cookieBehavior` tweak ;
* Re-enabling ETP with custom settings (including query parameter stripping) ;
* Re-dealing with persistent storage-related preferences (`2700`).
This increases divergence with Arkenfox upstream template.
> see #27
Thunderbird 101 replaced legacy `mail.default_html_action` and
`mailnews.sendformat.auto_downgrade` by `mail.default_send_format` new
preference to choose email sending format.
Whereas a proper "migration" is performed on first start, we stick to
plaintext email enforcement in this template, as done before.
See <https://bugzilla.mozilla.org/show_bug.cgi?id=1727493>.
> see #21
* Adds `mail.compose.warn_public_recipients.threshold` with its default value
* Enables `mail.compose.warn_public_recipients.aggressive` to show an alert if previous setting warning has not be addressed (v93+)
* Replaces `NOTE` tag by a proper `SETUP-CHROME` as it affects Thunderbird runtime behavior
* Mentions that reading from disk gets disabled too
* Mentions that "remote mail content" permissions are also affected
> see #23
