Comment 6 for bug 1895643

Hi,

If I could give an opinion from users perspective to this backport:
I'm using 20.04 focal. My setup ist Thunderbird 68 + Enigmail + OpenPGP.
With the Thunderbird 78 update users have to change their workflow.

A few examples:
User has disabled encryption per default, as most of it's recipients don't use encryption.
If the keyring contains a key for all recipients, enigmail automatically enables encryption.
This behavior is not possible with TB 78, you either have it enabled by default or not.

Keys inside TB keyring don't have passphrases. To secure them, you have to set a master password for the keyring, which disables you to just look at some mailing lists, newletters, whatsoever without typing the keyring password. (workaround is to use for the private key an external keyring key)

TB 78 doesn't offer the same capabilities (e.g. to alter your private keys to add another identity), as the old setup with TB 68 + Enigmail. If it would be just to port all keys to the internal keyring and everything else would be available as before (function wise, a few optical changes would not be problematic, as long as the functionality would be equal), fine.
But that's not the case.

Therefore I'd ask to take this into consideration updating the main thunderbird package in 20.04 and 18.04, as it surely will force those using encryption yet, to investigate how to replace their old setup.
Maybe an option could be to provide the backport as a new package like thunderbird-78?

Greetings, Lukas