On 5/16/02 at 8:34 PM MTayler wrote: >Hi, > >I noticed a change in the way how an tls session is loged. in 1.60c >there was far more information if a tls session failed. >Now if a tls session fails because of an invalid certificate there is >no obvious visual hint why. Even worse it makes you believe everything >is alright which is not the case. > > 2002-05-16, 20:30:26: FETCH - receiving mail messages > 2002-05-16, 20:30:27: FETCH - Initiating TLS handshake > 2002-05-16, 20:30:27: FETCH - connection finished - 0 messages received > > is the output in the log and it is really hard to see that the tls > connection failed. > Is this just me missing something obvious or what's going on? =============
I noticed the same thing when I eval'd TB! a couple of days ago. I was perplexed until I ssh'd into my server and read the maillog. Then I found out about the invalid certificate problem. But you are correct in that the TB! log shows little, if anything, to indicate a TLS error. Maybe I am missing an obvious way to make the looging more verbose in an error scenario? ________________________________________________________ Current Ver: 1.60k FAQ : http://faq.thebat.dutaint.com Unsubscribe: mailto:[EMAIL PROTECTED] Archives : http://tbudl.thebat.dutaint.com Moderators : mailto:[EMAIL PROTECTED] TBTech List: mailto:[EMAIL PROTECTED] Bug Reports: https://bt.ritlabs.com
