On Thursday, August 5, 2021, 07:57:24, Stuart Pye via TBBETA wrote: >>8/5/2021, 01:39:25: FETCH - Certificate S/N: 6A72CB, algorithm: RSA (512 >>bits), issued from 8/3/2021 5:34:18 AM to 7/29/2041 5:34:18 AM, for 1 >>host(s): mx.spamdropper.com.
> I've always run Microsoft TLS crypto on TB, no issues. > My mail server now uses Lets Encrypt for SSL certs for the various domain > mail it handles. > TB connection logging showed that the LE cert changed at a certain time, from > a cert good for > six months, or 90 days, I forget which, to a cert good for 20 years. When > that happened, TB stopped TLS-ing > with the M'soft default. Switching to TB option, all is good now. > Just thought the developers might want to know this Lets Encrypt behavior in > regards to TB. The line I quoted above, and the fact that the certificate says it's valid for 20 years means that something's intercepting your connection, and The Bat was right to refuse to connect (512-bit RSA hasn't been secure in the last 15 years, and Let's Encrypt always issues certificates valid for 90 days). You should verify what's happening (I'm guessing some anti-spam program). -- < Jernej Simončič ><><><><>< https://eternallybored.org/ > Never buy a car that has a wick. -- Ford Pinto Rule TheBat! Version 9.4.2.12 (64-bit), Windows 10.0.19043 ________________________________________________________ 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
