Hello Vilius, On Mon, 27 Sep 2010 19:17:05 +0300 GMT (27/Sep/10, 23:17 PM +0700 GMT), Vilius Šumskas wrote:
>> I am actually quite taken aback by this unexpected reply. I have >> absolutely no understanding for this policy which will certainly hurt >> my company. If I cannot send a mail to my customer because his sysad >> didn't update the cert, I *will* lose business. VŠ> You can always choose a company with does provide services as they are VŠ> supposed to be served. By "another company", do you mean another email-client or another customer? VŠ> Bad cert is not The Bat!'s fault. And providing an option to bypass VŠ> that, is a security risk as explained numerious times on this list. Right. So I'll lose the customer because TB! doesn't allow me to override the security issue. You must be quite unaware of business reality to say something like this. To tell you the truth: It needs to be *my* decision whether I accept an unsecure cert. Anything else will make me look for another email client, this nannying is just not acceptable. It is indeed TB!'s fault if it doesn't allow me to accept the expired cert after my own personal evaluation. Get real. I need the email client to work the way I need it, that's all. The only alternative is to switch to another client. As much as I love TB!'s filtering capabilities, I just cannot afford my messages not going through to the customer. It's a basic necessity. Why is this difficult to understand? -- Cheers, Thomas. http://thomas.fernandez.hat-gar-keine-homepage.de/ Message reply created with The Bat! 4.2.36.4 under Windows XP 5.1 Build 2600 Service Pack 3 ________________________________________________________ Current beta is 4.2.33.9 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
