-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Melissa Reese [MR] wrote: ... MR> Thanks - that's what I had to do (duh). It now works either way MR> (TB internal S/MIME or MS CryptoAPI). However - one final MR> question...
Good to see you worked things out. MR> Why are the two implementations not compatible? The same message MR> will show as "valid" if one is enabled, and will show as "invalid" MR> if I have the other implementation enabled. It does seem to depend MR> on which implementation was used during the signing; but if they MR> both claim to be "S/MIME", why are they not compatible? Is there MR> nothing like an "OpenS/MIME" standard? I really don't know. I don't think it's an incompatibility. More a bug in this TB! version. - -- -=Allie C Martin=- List Moderator | TB! v1.60i | Windows XP Pro PGP/GPG Public Key: mailto:[EMAIL PROTECTED]?Subject=2B0717E2 _________________________________________________________________ -----BEGIN PGP SIGNATURE----- iD8DBQE80eqWV8nrYCsHF+IRAhRpAJ0YevodnWqImlL8onPOa8JcDIlOOQCfcnxa +xJEqS2ufjVuAulNK+aesj4= =xUrT -----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]
