This thread was closed and archived. Please ask a new question if you need help.
DO NOT UPGRADE to version 78
Upgrades and changes are fine. BUT, version 78 MAKES CHANGES to THE DATABASE, so you can't go back. Please whoever came up with this idea is an idiot, please take him outside and shoot him. Thank you.
All Replies (2)
p.s. version 78.1.0 is out with many fixes https://www.thunderbird.net/en-US/thunderbird/78.1.0/releasenotes/
I cannot tell you how ticked off I am TOO about this change / version 78.0. On MacOSX, I use MacUpdater such that I can relatively automate for changes not covered by Apple's update procedures - means, MacUpdate collects all updates from all non-Apple SW in a database and scans my/your installed versions against this db. And guess what - it proposed to install Thunderbird 78.0 - and which I did, because new SW is always nice. And of course without reading the warnings. The new Thunderbird would not let me send unencrypted eMails, although I have opted for sending unencrypted. It always acts as if I would like to send encrypted and asks for passwords for keys that either don't exist or were not imported from Enigmail properly. Trying to reinstall old 68.xx would also not work straight away. NICE. Now I am in deep shit and need to figure out how to make it all work again. As if I had nothing else to do...
Peter if you post at https://thunderbird.topicbox.com/groups/e2ee someone will be able to assist.
From the developer "The only scenario I'm aware of, in which sending unencrypted wasn't possible, was the issue described in the pinned post in the e2ee list. But we fixed that before 78.0 . Are we certain that MacUpdater tool the user had used didn't give them something older? If the user really has 78.0, not anything older, then I don't know why sending unencrypted wouldn't work. Well. Maybe the user had a previous configuration setting, which was migrated to the new "require encryption" setting? But in that case, the user should be able to disable encryption in an individual message. I don't understand the claim about getting prompts for key passwords. It's not clear if the user went through the Enigmail migration procedure. The Enigmail migration tool should have removed the passwords from all migrated keys, and switched them to our automatic protection. (Which doesn't prompt for any password when using OpenPGP, unless the user has a master password configured.)"