Problems with version 2.0.4 - some encrypted mails cannot be decrypted Peringkat 5 dari 5 bintang
Still 2.0.3 no problems. But with 2.0.4 I cannot decrypt mails, send from my bank account.
Installation with current nightly (2.1a1pre) works.
Awesome and getting better and better Peringkat 5 dari 5 bintang
Works like a charm. Integrates cleanly into Thunderbird and the UX is getting better and better. No more excuses to not encrypt or sign your mails!Ulasan ini dibuat untuk versi pengaya (2.0.3) sebelumnya.
S/MIME works again Peringkat 5 dari 5 bintang
With version 2.0.1, the S/MIME bug has been corrected. Great!Ulasan ini dibuat untuk versi pengaya (2.0.1) sebelumnya. Pengguna ini memiliki 1 ulasan terdahulu untuk pengaya ini.
Great until 2.0, then completly non-functional Peringkat 4 dari 5 bintang
In general, I can't say enough good things about Enigmail.
It's sad that PGP has to be implemented as an add-on while S/MIME gets first class treatment as a built-in feature. Given that this is the situation we find ourselves in, Enigmail is up to the task. After the initial setup, it makes encryption easy! All my emails are automatically signed and encrypted, incoming emails are automatically decrypted and signatures verified. The messages are clear about when a message is signed, whether the person who signed it is trusted and so on. If it's unable to encrypt an email, it warns me (and this warning is optional for those who don't really care if they send unencrypted emails).
Unfortunately, when Thunderbird automatically updated me to version 2.0 of Enigmail, I could no longer read encrypted emails. There was no error message, just a blank email. I echoed the email and piped it to my gpg client on the command line and it worked fine. I used the same command which is found on the Basic tab of Enigmail's settings, so I'm confident this is a problem with Enigmail, not with gpg. Furthermore, uninstalling Enigmail and installing version 1.99 (which can be obtained from Enigmail's website if you modify the download URL) caused everything to work perfectly again.
This brings me to my only real complaint about Enigmail, which is a lack of ability to debug things when something goes wrong. It's rare that there are issues, but in these rare cases, it would be fantastic to be able to troubleshoot what's going wrong. Showing a blank email and no error messages when something goes awry is not reasonable. For a while I sat around waiting for the message to load. The only test I could run (piping the email to the pgp program on the command line) didn't reproduce the error, so I was stuck (short of digging into the source code of Enigmail).
Aside from having a custom wrapper around the gpg command (which shouldn't matter to Enigmail since it should just be running whatever gpg command is specified in the Basic preferences), I have a standard setup, so I'm not sure why it failed (again, back to the lack of error messages and debugging capabilities). I'm not sure how (or if) new versions are tested before being released, but given the number of reviews citing problems with version 2.0, it does raise questions about this process as well. Hopefully they get it sorted out, and if not, I can just stay on version 1.99 forever.
Dont work properly anymore Peringkat 1 dari 5 bintang
Since last Update to 2.0 S/MIME dont work properly anymore. So I have to deinstall Enigmail as S/MIME is essential for my purposes.
I fear i wouldn't use/install Enigmail anymore.
Badly as i really appreciate PGP for some selected communication partners, but we will have to find now another solution for that.
2.0 broken Peringkat 1 dari 5 bintang
The version 2.0 really breaks interaction of S/MIME and PGP. In earlier version it was possible to individually set how to sign and encrypt mails. Now you can only turn signing and encryption on or off and "Enigmail will chose between S/MIME or OpenPGP depending on whether the keys for all recipients are available for the respective standard", whatever that means. And unfortunately, it doesn't work properly and is completely intransparent. This is a problem if you have both SMIME and PGP set up for one account. You cannot choose which keys to use for signing or encrypting. I also found, that SMIME is not used anymore if you also have PGP setup. Even if both sender and recipient also have SMIME available. So it's unclear how it actually works. Also, if Enigmail does not find a recipient's key, it will also not sign the mail, even if sigining is enabled.
Anyway, you can't set what method to use, you can't see, what Enigmail will actually use, you can't even be sure, that any signing or encryption ist performed at all prior to sending. That makes the whole thing practically unusable. Thats especially annoying since this extension seems to be the only one to bring PGP to thunderbird.
Until this behavior is fixed, you need to find an alternative mail client for encryption, which is extremely unfortunate.
Please try the following build which should fix the issue with the default values:
You can see what Enigmail does by checking the "Sign" and "Encrypt" icons in the toolbar. If S/MIME is used, then the status bar displays the S/MIME signing/encryption icons.
In addition, the Enigmail menu tells you which algorithm will be selected and allows you to manually pick the algorithm you want.
S/MIME and PGP Peringkat 2 dari 5 bintang
The update is not mature. I can confirm the reported issue "enigmail 2.0 breaks s/mime". I am no longer able to sign with s/mime by default for non-pgp e-mails. Is this no longer possible? The new settings for signing and/or encryption look quite confusing even for experts.
For all non-pgp receivers I normally sign with s/mime and add my public pgp key as attachment. So every receiver has the chance to trust my e-mail and also to reply encrypted.
Please try the following build which should fix the issue:
enigmail 2.0 breaks s/mime Peringkat 4 dari 5 bintang
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:
Btw. the menu Enigmail allows you to manually select the algorithm for each message.
Working like advertised for as long as I can remember Peringkat 5 dari 5 bintang
Works with the most recent version of Seamonkey.
Has all the functions I need. Been happily using this for years now.
Peringkat 5 dari 5 bintang
Gute PGP IntegrationUlasan ini dibuat untuk versi pengaya (1.9.9) sebelumnya.
Mükemmel bir eklennti Peringkat 4 dari 5 bintang
Kullandım herkese tavsiye ederim. Sorunsuz çalışıyorUlasan ini dibuat untuk versi pengaya (1.9.9) sebelumnya.
Awesome Peringkat 5 dari 5 bintang
Does what it says on the tin. Makes it easy to use encryption.Ulasan ini dibuat untuk versi pengaya (1.9.9) sebelumnya.
Peringkat 5 dari 5 bintang
Really great encryption add-on! Allows easy management of keys and automatic encryption and signing. All one needs.Ulasan ini dibuat untuk versi pengaya (188.8.131.52) sebelumnya. Pengguna ini memiliki 1 ulasan terdahulu untuk pengaya ini.
I use this great add-on Peringkat 5 dari 5 bintang
I am a true fan of GnuPG when sending e-mail's. Enigmail makes is so easy to manage keys and to send encrypted e-mail's!Ulasan ini dibuat untuk versi pengaya (184.108.40.206) sebelumnya.
it works Peringkat 5 dari 5 bintang
hi.. this addon was perfect but it does not work with default settings under debian after update to 220.127.116.11 unless you create custom wrap launcher with unset GPG_AGENT_INFO which works for me.
Problem: GnuPG reported an error in the communication with gpg-agent (a component of GnuPG).
- using debian 8 64bit - thunderbird latest and this extension latest.
Please report your issue to Debian
I'm working closely with the Debian package maintainers to avoid such issues. The problem you are describing is not common to all Debian users; I would strongly recommend that you report it to the Debian bug tracker, such that knowledgeable people can look into it and either help you fix it, or fix the issue in Debian.
No longer useable Peringkat 1 dari 5 bintang
Enigmail used to work like a charm, but broke about a year ago. Thunderbird hangs on sending emails 4 out of 5 times, and constantly requires you to kill gpg2 in order to keep working.
It's really disappointing, as it seemed to be the first extension that actually got email encryption right and used to be extremely useful.
Do you use the latest version of Enigmail? It should not make Thunderbird hang any longer. Otherwise, please report your issue at the Enigmail Mailing List and we will try to fix your problem.
enigmail 18.104.22.168 Peringkat 1 dari 5 bintang
Korrektur downgraden auf 1.9.7Ulasan ini dibuat untuk versi pengaya (22.214.171.124) sebelumnya. Pengguna ini memiliki 1 ulasan terdahulu untuk pengaya ini.
unbrauchbares update, bin total frustriert Peringkat 1 dari 5 bintang
Seit dem letzten update von thunderbird geht enigmail nicht mehr. Vor allem aber sind meine gespeicherten Entwürfe nicht mehr lesbar! Ich hatte keine Möglichkeit, sie unverschlüsselt zu speichern (auch blöd!), und jetzt sind sie weg.Ulasan ini dibuat untuk versi pengaya (1.9.7) sebelumnya.
Keyserver up/downloads unusable. Peringkat 4 dari 5 bintang
This version( 126.96.36.199) is incompatible with Thunderbird 52 that makes keyserver up/downloads unusable.
Download version 1.9.7
No warning when uploading keys Peringkat 1 dari 5 bintang
This addon does not provide sufficient warning when you click upload public keys. (Sufficient warning = a popup explaining that uploaded public keys can't be removed from the key servers once uploaded)
This can lead to leaking of private email addresses that you wish to keep hidden from the public.