Rated 5 out of 5 stars

Super Plugin. Es tut was es soll. Eigentlich muss Thunderbird diese Option von sich aus bringen. Aber so get es auch.

Ein kleiner Verbesserungswunsch, eine Option um eine Warnung zu bekommen wenn eine Email an einen Empfänger unverschlüsselt raus geht. Das wäre sinniger als eine Meldung wenn einer der nachrichten verschlüsselt rausgeht.

Aber trotzdem super Plugin: 5 Sterne!

Vielen Dank für Eure Arbeit

Snowyrain

Rated 5 out of 5 stars

Sehr sinnvolle Erweiterung. Installiert, getestet und mich sofort gefragt, wie es bisher ohne ging. Danke!

Zusätzlich zur Option "Nachfragen, bevor automatische Verschlüsselung aktiviert wird." würde ich sicherlich noch folgende Option nutzen, wenn es sie gäbe:

"Nachfragen, bevor eine E-Mail unverschlüsselt versendet wird."

Diese Option könnte ggf. unterteilt sein für E-Mails an Empfängergruppen bei denen man von "einigen der Empfänger" Zertifikate hat und solche in denen man von "keinem der Empfänger" Zertifikate hat.

Tut genau das, was es soll Rated 5 out of 5 stars

Es rüstet eine kleine Funktion nach, die eigentlich schon eingebaut sein sollte.
Da die "Verschlüsselung erforderlich" Einstellung bei jeder Adresse nervt, zu der man kein Zertifikat hat, ist diese quasi nutzlos. "Immer unverschlüsselt" ist auch Quatsch, wenn es doch oft genug möglich wäre. Jeder der das genauso sieht, sollte diese Erweiterung einsetzen.

Rated 5 out of 5 stars

Unverzichtbare Erweiterung für Benutzer von S/MIME. Diese Funktionalität sollte von Haus aus in Thunderbird vorhanden sein. Herzlichen Dank an den scharfsinnigen Autor, und schöne Grüße nach Österreich!

And now for my English friends:
This add-on is a must have for S/MIME users. Its functionality should be implemented in Thunderbird per default. A warm thank-you to the smart author, and many greetings to Austria!

Wirklich nötig? Ja! Rated 5 out of 5 stars

Ist dieses Addon wirklich nötig? In TB 17.0.7 gibt es doch bereits unter Konten-Einstellungen>S/MIME-Sicherheit>Verschlüsselung die Option "Notwendig (Senden nur möglich, wenn alle Empfänger ein Zertifikat besitzen"! Was ist der Unterschied, was bietet dieses Addon für Vorteile? Die 3Stern-Bewertung ist vorläufig! LG

Danke für die Antwort: das dachte ich mir schon! Ich habe das Addon nun ausprobiert und es läuft wie gewünscht.
Ein Tipp: Falls einer der Empfänger kein Zertifikat hat, die anderen aber schon, dann die Mail einmal nur an diesen einen senden (was dann natürlich unverschlüsselt geschieht) und dann nochmal nur an die anderen, was dann verschlüsselt geht.
>> 5 Sterne

ja, weil man mit der Standard-Option sonst ohne Zertifikat gar nicht senden _kann_. Das Add-On setzt die Verschlüsselung, wenn _möglich_, erzwingt sie aber nicht.

("possible" != "required")

perfekt Rated 5 out of 5 stars

funktioniert super! Vielen Dank!

Eine kleine Anregung habe ich aber noch, Thunderbird zeigt ja unten rechts im Fenster für neue Nachrichten immer an, ob sie verschlüsselt oder signiert sind. Vielleicht könnte man das Verschlüsseln schon vor dem Absenden/Speichern aktivieren, z.B. wenn eine neue Adresse hinzugefügt wurde (ich weiß nicht welche events es da in Thunderbird gibt ... aber vielleicht geht das ja ;) )

einfach die Mail dazwischen abspeichern (Shortcut Strg-S), dann wird das Icon rechts unten angezeigt.

Absolutely awesome! Rated 5 out of 5 stars

This extension is absolutely awesome! For months, I've been lamenting how the i-platforms can auto-encrypt when certs are present. With Thunderbird, encryption has always been kind of difficult, with always/never being the only options.This extension finally bridges the middle ground, allowing the option to encrypt messages by default, but only when certs are present. Additionally, configuration settings are kept to a minimum, making this extension very simple to use.Many thanks, GWu!

AWESOME EXTENSION! Rated 5 out of 5 stars

Works exactly as specified! Great tool, allows me to easily insure all the people I have public certs for get encrypted messages.

does what it says Rated 5 out of 5 stars

Works as designed, I guess - I had to change the default encryption setting when sending messages in my account settings from "Required" to "Never (do not use encryption)".

If I don't have a certificate the mail is sent without the nasty "no certificate - yadda yadda" error message. If I choose a recipient for whom I DO have a certificate, the plugin shows a dialogue with the title "Certificates found" and asks "Activate message encryption [Yes] [No]". This can be disabled in the add-on settings. Then messages to recipients for whom you do have a certificate would be encrypted transparently (almost, usually you'd have to enter your passphrase first).

Many thanks, waited ages for this - for anyone who's wondering why, see https://bugzilla.mozilla.org/show_bug.cgi?id=135636

This review is for a previous version of the add-on (0.1). 

Works like a charm! Rated 5 out of 5 stars

*[EDIT]
This plugin exactly does what it's meant to :) My former issues from below have been fixed in three days so five stars not not only for the plugin but also for the good support by GWu!




Hi GWu I just installed this addon in anticipation in TB 16.x because I was looking for something like that for years now!


But unfortunately it does not work right out of the box.* Do I have to activate it somehow? It is listed as active in the Add-Ons. Then I tried the following two from which non of them worked for me:


1. The security settings for my mail account are sing by default and never encrypt. Click "write", added mail address as "To" from which I have the certificate installed (It is listed in the certificate manager under "Your Certificates") when I open "S/MIME > View Security Info" recipient is listed with valid certificate. But when I send the mail I neither get an information from the plugin nor does it activate encryption for this mail.


2. The security settings for my mail account are sing by default and always require encryption. Click "write", added mail address as "To" from which I have no certificate. When I open "S/MIME > View Security Info" recipient is listed with Not found certificate. But when I send the mail I neither get an information from the plugin nor does it deactivate encryption for this mail. Only message I get is that from TB telling me the mail can't be sent because recipient certificate is not available.



What did I do wrong or is there something else I am required to do?



Four Stars because I really like the idea and I really like this to work ;)



[EDIT]

I tried as you suggested and I get the following output in the console:

pref - debug: true

pref - auto_encrypt_ask: true

from: webmaster@tkuhn.de

webmaster@tkuhn.de: null

no certificate for webmaster@tkuhn.de




Which is kind of odd because:

1. I have a valid certificate for webmaster@tkuhn.de listed in Your Certificates

2. I have selected this certificate in the mail account settings I am writing from for signing and encryption (I guess this is the setting the add-on should get the certificate to use from)

3. When I manually activate signing and or encrpyption everything works perfect



Any other Idea? If you need more information feel free to contact me using the email address given above, since this here is a little bi unfitting for support, but I could not find any other way on this site to contact you.

This review is for a previous version of the add-on (0.1). 

You don't have to activate it explicitly, if it's installed, it's active.
Change the default security/encryption setting in your account settings from "Required" to "Never (do not use encryption)" to benefit from the add-on.

Hard to tell what's the issue in your case, maybe TB doesn't find either your own and/or all of the recipients' certificates (the email addresses have to match exactly, obviously).

You can enable debug message for the plugin: Tools -> Options -> Advanced -> General -> Config Editor: set "extensions.encryptifpossible.debug" to true.

Then open Tools -> Error Console , click "Clear" or scroll to bottom.

Compose a new message, add a recipient of which you are sure you have a certificate and save it as draft (Ctrl-S), now the add-on should ask if you'd like to activate encryption.

If not, check the Error Console:

If certificates are found, you can see messages like "alice@bob.com: [xpconnect wrapped nsIX509Cert]", for the sender as well as for all of the recipients.

If for some of the recipients the certificate is not found, there is a message like "alice@bob.com: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIX509CertDB.findCertByEmailAddress]" ... data: no].

Certificates must be found for the sender and for _all_ of the recipients, otherwise encryption will (and can) not be activated.

And thanks for giving 4 stars nevertheless :)