-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Michael,
@11-Sep-2002, 18:57 Michael Thompson [MT] in [EMAIL PROTECTED]">mid:[EMAIL PROTECTED] said: MT> Sorry, That was the wrong message. It is this one. ... <snip> MT> How weird is this??? Aha! Not so weird after all. It's S/MIME signed. I'll bet you have MSCryptoAPI selected for S/MIME. The S/MIME signature verification is calling the MSCryptoAPI which in turn is hitting HTTP on port 80. Switch to Internal and it should stop doing so. It may also depend on which MS Web components you have installed. It looks like for some reason there's something about that signature your MSCrypto Install can't cope with, so the OS is trying to install a Crypto update when TB requests signature verification for that message. - -- Cheers -- .\\arck D Pearlstone -- List moderator TB! v1.62/Beta5 on Windows 2000 5.0.2195 Service Pack 2 ' -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.1.91-nr1 (Windows 2000) iD8DBQE9f/K4OeQkq5KdzaARAjRvAJ9PKkxEqlc398A/K2jZB+PqfMbyGACfRXYj aZDlmI0f/FYxfi4d09q45IY= =QUYd -----END PGP SIGNATURE----- ________________________________________________ Current version is 1.61 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
