Pages: 1
RSS
MAJOR BUG in TheBat Pro 4.0.14, Connection settings
 
I used the v3.x.x pro (licensed) with iKey token and upgraded yesterday to the 4.0.14 pro/token. My connection is a LAN connection.

I always launch TheBat through SockCaps, an application that makes all the connections of TheBat (or of any other software launched by SocCaps) go through a socks server that is setup in SockCaps. The socks proxy is my company proxy.

No problem with the V3.x release, BUT ALL THE CONNECTIONS from TheBat v4 release do NOT go through the socks server, but are sent directly online. I suspect that the V4 checks the connection of the computer and connects directly there.

I completely un installed the v4, nmanually deleted the RIT register keys (btw WHY are them NOT DELETED when we uninstall thebat????), re-installed the v4 with no account (just created a test account), same thing.

And finally I all removed again and re-installed the v3 release!!!


That is of course a major bug as it seems not possible to use TheBat V4 with a socks proxy.
 
The problem you wrote about is happening because SocksCaps doesn't support the new TCP/IP (WinSock) API used by The Bat! since V4. The new API allows The Bat! to terminate the connections gracefully (avoid hanging tasks in The Bat! Connection Center) and use IPv6.

The native support of SOCKS4 in The Bat! will resolve this issue.

The new version of The Bat! will support SOCKS4 proxy for IMAP4, POP3 and SMTP. It will also support http proxy to download external images from html pages.

Pages: 1