Hi, 1) I just wanted to know, if this bug is fixed for you:
[-] Fixed a bug of Beta/2 with S/MIME internal implementation. It didn't check correctly the signatures. For me, it isn't. If I change the S/MIME engine to 'Microsoft CryptoAPI' all signed mails are checked correctly. If I change it back to the 'internal implementation' most (not all) of the signatures are marked as invalid. Doubleclicking on such an invalid signatures gives me following error: PKCS#7 object cannot be parsed. Failed to verify the message. No signatures information available. Do you have the same behavior with _this_ email ? Valid with 'Microsoft CAPI', INvalid with 'internal implementation'. Watch out, if you test it, after you have changed the S/MIME engine settings (Options - S/MIME), you have to select an other email and then switch back to this one, to activate the new engine settings. 2) Are you able to sign outgoing mails when S/MIME engine is set to 'Microsoft CAPI' ? I'm not. If I switch to 'internal implementation' it works perfectly well. Maybe I'm wrong, but when 'Microsoft CAPI' is selected, I'm not able to 'Edit personal certificates' - so maybe it is not expected to work using 'Microsoft CAPI' ? Greetings Daniel -- Using The Bat! v1.62/Beta5 on Windows 2000 5.0 Build 2195 Service Pack 2 (I know, this email has _not_ been sent using The Bat!, but to demonstrate my problem I had to sign it using my keys stored on iKey) -- "Yeah! It works! It wo...oops!.."
smime.p7s
Description: application/pkcs7-signature
