För att prova de tusentals tillägg tillgängliga här, ladda ner Mozilla Firefox, ett snabbt och gratis sätt att surfa på webben!
StängVälkommen till Firefox tillägg.
Välj bland tusentals extrafunktioner och stilar för att göra Firefox till ditt.
StängUtvecklarsvar från Patrick Brunschwig
Betygsatt 4 utav 5 stjärnor
I'm using s/mime. Since upgrading to enigmail 2.0 outgoing messages using identities without gpg keys are not s/mime signed by default anymore. I tried to play around with the settings and managed at least to use s/mime as default for identities /with/ gpg keys. Is there a kind of some freaky combination of settings to get identities w/o gpg key to be s/mime signed by default? Thunderbird's own "sign by default" option is getting completely ignored.
edit, after installing enigmail nightly: works better now. But still, if I unset "enable openpgp support (enigmail) for this identity" I expect not to have pgp at all and to exclusively use s/mime. But s/mime signing is not selected (which should be the default according to thunderbird's settings). Instead, the enigmail menu shows "protocol pgp/mime (auto)" selected.
Please try the following build which should fix the issue with the values taken from Thunderbird's own default:
https://enigmail.net/download/nightly/enigmail-nightly-enigmail-2.0-branch-all.xpi
Btw. the menu Enigmail allows you to manually select the algorithm for each message.
För att skapa egna samlingar, måste du ha ett konto för Mozilla tillägg.