My company started requiring secured logins via SSL to its mail server, so I put The Bat aside (reluctantly) and switched to Outlook. Now that The Bat 1.60c supports TLS 1.0, I have attempted to switch back.
SMTP sends work most of the time using the "mail transport" setting "Secure to dedicated port (TLS)" and port 465. POP3 fetches never work, also using the "dedicated port" setting to port 995. These same ports work fine with Outlook, which uses SSL 2/3. Working with the server techs, they discovered that my POP3 login attempts create a server logfile message "none of the TLS cipher methods is supported." On The Bat side, the logfile reports "TLS protocol error: Invalid protocol version." I am not using any authentication. I call the server using a dial-up connection. I am running Windows Me. The company uses CommuniGate Pro from Stalker Software (www.stalker.com). My guess is that there is a problem with the TLS implementation in The Bat 1.60c, but it could be a server software problem instead. The fact that SMTP doesn't always work seems suspicious to me. I have tried all combinations of secured/ unsecured ports, with and without authentication, but nothing works. Is anyone successfully using TLS secure logins? Does anyone have suggestions as to what I might try next? Thank you in advance for your help. I miss The Bat! -- Charles Lehardy Summer Institute of Linguistics San Pablo Villa de Mitla, Oaxaca, Mexico ______________________________________________________ Archives : http://tbtech.thebat.dutaint.com Moderators : mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED]
