-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, May 02, 2002, at 3:54:48 AM PST, Allie C Martin wrote:
> Have you imported your S/MIME certificate into TB!? Hello Allie, Thanks - that's what I had to do (duh). It now works either way (TB internal S/MIME or MS CryptoAPI). However - one final question... Why are the two implementations not compatible? The same message will show as "valid" if one is enabled, and will show as "invalid" if I have the other implementation enabled. It does seem to depend on which implementation was used during the signing; but if they both claim to be "S/MIME", why are they not compatible? Is there nothing like an "OpenS/MIME" standard? Melissa - -- PGP public keys: mailto:[EMAIL PROTECTED]?subject=0xFB04F2E9&Body=Please%20send%20keys -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAjzRZW4ACgkQjVbXUvsE8ulOggCgwUcWu9HI6mn0F7qVrFFqhEbk 70QAoJEoG70chFGHzC/MJ048CCKu3Rvu =wCLB -----END PGP SIGNATURE----- ________________________________________________________ Current Ver: 1.60h FAQ : http://faq.thebat.dutaint.com Unsubscribe: mailto:[EMAIL PROTECTED] Archives : http://tbudl.thebat.dutaint.com Moderators : mailto:[EMAIL PROTECTED] TBTech List: mailto:[EMAIL PROTECTED]
