With Thunderbird 17.0 and Enigmail 1.4.6, I get a behavior that every time an encrypted mail is received (and processed by mail filter), the OpenPGP password prompt pops out. I had this behavior with some older TB version already, but then it ceased, now it is back. Automatically decrypt/verify messages is off, search indexer and windows search is off, too.
Any idea?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Apparently, after upgrade, some Thunderbird settings are lost in a very funny way (credits here go to Tomas Vasko). The Automatically decrypt/verify was off in the menu but not in the reality. And just checking and unchecking didn't help, Thunderbird restart was needed in between. After I checked it, restarted, unchecked and restarted again, the problem is gone.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Patrick.
With Thunderbird 17.0 and Enigmail 1.4.6, I get a behavior that every time an encrypted mail is received (and processed by mail filter), the OpenPGP password prompt pops out. I had this behavior with some older TB version already, but then it ceased, now it is back. Automatically decrypt/verify messages is off, search indexer and windows search is off, too.
Any idea?
Hi Rasto
I think that's a Thunderbird bug.
See these mails:
https://admin.hostpoint.ch/pipermail/enigmail-users_enigmail.net/2013-January/000426.html
https://admin.hostpoint.ch/pipermail/enigmail-users_enigmail.net/2013-January/000429.html
A new Thunderbird version should be out in a few days; I think this should fix the problem.
Ah, got it already, problem solved.
Apparently, after upgrade, some Thunderbird settings are lost in a very funny way (credits here go to Tomas Vasko). The Automatically decrypt/verify was off in the menu but not in the reality. And just checking and unchecking didn't help, Thunderbird restart was needed in between. After I checked it, restarted, unchecked and restarted again, the problem is gone.
This is usually due to a corrupted localstore.rdf file (in your profile directory).