Marck D Pearlstone <[EMAIL PROTECTED]> wrote on 12.09.2002, 03:49:43: > > 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. >
There had to be a simple explanation did'nt there!!!! Thank you mark for clearing that one up. Once again we all bow to you :) ________________________________________________ Current version is 1.61 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
