Bug 3378

Summary:	Ability to import and use non-PGP digital signature
Product:	Claws Mail (Windows)	Reporter:	daniel <daniel.hrbac>
Component:	default	Assignee:	users
Status:	RESOLVED INVALID
Severity:	enhancement	CC:	daniel.hrbac
Priority:	P3
Version:	3.12.0
Hardware:	PC
OS:	Windows 8

Description daniel 2015-02-02 21:51:24 UTC

It would be great if the Claws Mail would be able to work also with other digital signatures types than PGP generated. I mean .pfx files. Where I live these are used for legally binding correspondence. 

Background: I have been looking for Thunderbird alternative and Claws mail (windows build) works very nice. I have been able to locate nearly everything I need. There are some minor issues, but not blockers.

Comment 1 Andrej Kacian 2015-06-28 21:15:43 UTC

Have you tried the S/MIME plugin? As far as I know, .pfx are standard x509 signatures.

Comment 2 daniel 2015-07-04 17:04:35 UTC

I did now. In account settings I specify path to file with my_postsignum_certificate.pfx When sending mail I select in settings > security > s/mime and settings > sign. The result now is "S/MIME: Cannot sign, General error (1)" 

I looked at http://www.claws-mail.org/faq/index.php/S/MIME_howto and it looks like that on windows it needs some background engine, so tried to install gnupg for windows. even then kleopatra cannot find this certificate and sending signed mail ends with same error.

Comment 3 daniel 2015-07-20 20:34:39 UTC

I am not sure if the new version (13.2.) helped, but probably mistake was somewhere else. Claws can handle X.509 certificates via gpg4win software and S/MIME plugin. Importing into Kleopatra helped + setting up root certificates in a way described in gpg4win HOWTO-SMIME document.