I, too, have been trying S/MIME since reading the recent posts, and now have some questions for the list.
I've been swapping around with 1.60c and 1.60h (and now 1.60i), and I'm not sure whether I've tried everything below with each version. 1. I think I am correctly signing emails, using CryptoAPI. They certainly appear signed in TB!, but when I sent a message to my work email and checked it at work (where I am forced to use Outlook 98), the text was present with no signature. It's possible that the company firewall stripped the signature as a disallowed attachment. So, is this email properly signed? 2. I got a certificate for my work email and sent a signed message home. No problem. I right-clicked on the signature icon and imported it. That appeared to work, and I could view the signature in the "Other people" tab in the Internet options. But when I tried to send an encrypted message to my work address, the certificate couldn't be found. I started up Outlook Express, and got the same problem. I went back to the signed message, and saved the certificate to the desktop, opened up Internet Options and imported it. Now I can encrypt with that certificate. Is this a bug in the import process, or did I do something wrong? 3. Now I've succeeded in sending an encrypted message, but I can't read it myself. I thought the relevant setting was "Always encrypt to sender's certificate". I have this set (and had it set when I sent the encrypted message). Is this a bug or did I do something wrong? -- Tim [EMAIL PROTECTED] The Bat 1.60i Windows XP 5.1
smime.p7s
Description: S/MIME Cryptographic Signature
