Hi all,
I'm having some problems with S/MIME certificates, and wondering if anyone has any
suggestions.
1. Any email I recieve that was sent from Outlook 98 or Outlook Express 6 that
containes an S/MIME signature/certificate causes TB to pop up an error dialog
stating...
"Access violation at address <hex code>. Read of address <same hex code>."
The hex code changes each time the dialog opens, even with the same email. Can't read
the email at all... ever.
2. Any signed email that I *send* to an Outlook 98 user isn't recognized as signed by
Ol98. Ol98 doesn't even recognize that there's an attachment at all, much less what it
is. Signed email sent from Ol98 to Ol98 works fine, just not if it comes from TB. I'm
pretty much writing this one off to poor S/MIME support by Ol98, but thought somebody
here might know more and have a suggestion.
Additional Info...
A. Signed email sent to/from TB and Outlook XP is properly received and authenticated
both ways. This is the only combination that seems to work.
B. Signed email sent from TB *to* Outlook Express 6 works too, just not the other way
around... see #1 above.
C. TB is set to use Microsoft CryptoAPI (if that helps).
#2 I've resigned to just having to live with, but #1 is getting really frustrating.
--
Using The Bat! v2.01.3 on Windows XP 5.1 Build 2600
Service Pack 1
________________________________________________
Current version is 2.01.3 | "Using TBUDL" information:
http://www.silverstones.com/thebat/TBUDLInfo.html
