-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Peter,

On Fri, 30 Apr 2004 19:22:19 +0200 (1:22 PM here), Peter Meyns [PM]
wrote in <mid:[EMAIL PROTECTED]>:

PM> I don't really know. It seems to work as usual here. I'd
PM> scrutinize the settings in Account � Properties � General � Edit
PM> personal certificates. Your issuer's certificate should be listed
PM> there along with your own.

I've ironed out my problems but not without some difficulty. I had 7
accounts with Thawte certificates, none expired. 2 accounts seemed
functional but nothing I did could massage the other 5 back to life.
Exporting again from Windows and re-importing into The Bat! didn't
work. Then I tried re-downloading from the Thawte site. Unfortunately,
I would get errors when trying import a copy of the certificates back
into IE from the Thawte site. I'm not sure what that was about, as the
message was not very descriptive. I'm assuming it was an error on the
Thawte site.

Rather than wait for a tech support answer, I went to CACert and
requested certificates for my 7 email addresses. Everything worked
fine and I imported into IE and eventually into my accounts in The
Bat! without any difficulties.

I did find something curious when examining each account's personal
certificates. 2 accounts had both mine and the issuers certificate as
you suggested. The other 5 only showed my certificate. I sent test
messages using all the accounts and everything seems to work. I just
am curious why all the accounts don't have or seem to need the issuers
certificate in the edit window. Perhaps it finds what it needs in the
Intermediate CA or Trusted Root CA address book. I'm also wondering
why all of this stopped working in the first place. As I've always
used The Bat's internal s/mime implementation, all the Cert
information should be independent of the Windows Cert store so any
problems shouldn't be Windows related. I've never changed the account
properties for the Certs since the last time when they were working.

Oh well, everything is working now. Let's hope it stays that way. Its
no wonder why I stick to PGP. :)

- --
Kevin Coates
Dewitt, NY USA

Using TB! v2.10.03 under Windows XP 5.1.2600 SP1
________________________________________________________________
(see kludges for my pgp key)
-----BEGIN PGP SIGNATURE-----

iD8DBQFAk6aPvZSrVDqOXK0RAn7gAJ9LvRQbts6uNZ4ZyRWh9Z5297rKIQCfWbOn
Idj3aHP5POJy4G8/NFIXLvU=
=h423
-----END PGP SIGNATURE-----

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

________________________________________________
Current version is 2.10.03 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html

Reply via email to