Hello Stefan, Monday, August 2, 2021, 5:02:26 AM, you wrote:
> https://www.ritlabs.com/download/files3/the_bat/beta/tb9.4.2.12-x64-full.7z SP>> Generated TLS errors, could not receive mail, see logs: 8/5/2021, 01:39:25: FETCH - Initiating TLS handshake >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. >8/5/2021, 01:39:25: FETCH - Owner: mx.spamdropper.com. >8/5/2021, 01:39:25: FETCH - Issuer: mx.spamdropper.com. !8/5/2021, 01:39:25: FETCH - TLS handshake failure. Invalid server certificate. The certificate or one of the certificates in the certificate chain does not have a valid signature.. The certificate or certificate chain is based on an untrusted root. SP>> Changed TLS settings under Otions to TB, rather than Microsoft CryptoAPI default: Mail service returned. (Bluemail on my Android phone, never stopped working.) 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. U&R now. Hopefully forever. -- Best regards, Stuart Pye ________________________________________________________ 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
