Search  Rules  Login
TheBat English » The Bat! - Configuring the E-mail Client
Pages: 1
RSS
AppCrash at 8.5.2
 
#1
0  
Name der fehlerhaften Anwendung: thebat64.exe, Version: 8.5.2.0, Zeitstempel: 0x5b36093d
Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000cfae860
ID des fehlerhaften Prozesses: 0x348
Startzeit der fehlerhaften Anwendung: 0x01d40fbd900884e0
Pfad der fehlerhaften Anwendung: C:\Program Files\The Bat!\thebat64.exe
Pfad des fehlerhaften Moduls: unknown
Berichtskennung: 77e15d90-7bb7-11e8-ba4d-005056c00008
 
 
 
#2
0  
My guess is that you'd stand a better chance of getting a reply if you'd post in English.
 
 
 
#3
0  
non-working gmail the bat8.5.2

30.06.2018, 10:25:20: IMAP - TLS handshake started
! 30.06.2018, 10:25:20: IMAP - TLS handshake failed. Existing connections have been forced terminated by a remote host
30.06.2018, 10:25:32: IMAP - Connecting IMAP server imap.gmail.com to port 993
30.06.2018, 10:25:32: IMAP - TLS handshake started
! 30.06.2018, 10:25:32: IMAP - TLS handshake failed. Existing connections have been forced terminated by a remote host
30.06.2018, 10:25:39: IMAP - Connecting IMAP server imap.gmail.com to port 993
30.06.2018, 10:25:39: IMAP - TLS handshake
! 30.06.2018, 10:25:39: IMAP - TLS handshake failed. Existing connections have been forced terminated by a remote host
30.06.2018, 10:25:50: IMAP - Connecting IMAP server imap.gmail.com to port 993
30.06.2018, 10:25:50: IMAP - TLS handshake started
! 30.06.2018, 10:25:50: IMAP - TLS handshake failed. Existing connections have been forced terminated by a remote host
30.06.2018, 10:33:00: IMAP - Attaching imap.gmail.com IMAP to port 993
30.06.2018, 10:33:00: IMAP - TLS handshake
! 30.06.2018, 10:33:00: IMAP - TLS handshake failed. Existing connections have been forced terminated by a remote host
30.06.2018, 10:36:01: IMAP - Connecting IMAP server imap.gmail.com to port 993
30.06.2018, 10:36:01: IMAP - TLS handshake started
! 30.06.2018, 10:36:01: IMAP - TLS handshake failed. Existing connections have been forced terminated by a remote host
 
 
 
#4
0  
sloved:


do not update to 8.5.2 if you use Gmail. TLS

does not work version 8.5.2, does not work with google gmail
Edited: Krnac Martin - 30 June 2018 23:35:40
 
 
 
#5
0  
Posting in large text in Bold is offensive and indicates you're shouting. Some courtesy will be appreciated. Please refrain from that. And as I mentioned in a separate thread, you are wrong. It works fine for me. And I doubt I'm the only one. I don't doubt there may be issues in this transition to 1.2, but I trust the support team is working on them.

david
 
 
 
#6
0  
no, it does not work and I'm not the only one.

vers: 8.5:

30.06.2018, 22:37:55: IMAP - Connection to IMAP Server "imap.gmail.com" successfully established

vers: 8.5.2

! 30.06.2018, 22:38:36: IMAP - TLS handshake failed. Existing connections have been forced terminated by a remote host
Edited: Krnac Martin - 30 June 2018 23:45:33
 
 
 
#7
0  
Hello there,

Same error with 8.5.2.


I have a google account, a ymail account , a gmx account.

Three errors with TLS .

30.06.2018, 10:25:50: IMAP - Connecting IMAP server imap.gmail.com to port 993
30.06.2018, 10:25:50: IMAP - TLS handshake started
! 30.06.2018, 10:25:50: IMAP - TLS handshake failed. Existing connections have been forced terminated by a remote host
 
 
 
#8
0  
Do you have an antivirus that might have broken the  connections? If it is the case, and you have an antivirus, then I can  suspect that it is the antivirus that breaks the connections. In this  case, I can suggest you one of the following temporary solutions until  we update The Bat! for better compatibility with existing TLS software.  The solutions are:

1. Configure the antivirus to not break The Bat! connections
2. Configure The Bat! to disable Perfect Forward Secrecy by using the  following command-line parameter: /TLS_DISABLE_PERFECT_FORWARD_SECRECY
3. Configure The Bat! to disable TLS 1.2 by using the following command-line parameter: /TLS_VERSION_RANGE:0-2

The numbers in /TLS_VERSION_RANGE have the following meaning:
0 - SSL 3.0
1 - TLS 1.0
2 - TLS 1.1
3 - TLS 1.2

So, by specifying the "0-2" range you limit The Bat! to use any version between SSL 3.0 and TLS 1.1.

Just let me know which of the solutions helped.

To add a command-line parameter, you can modify the shortcut that  runs The Bat! by adding the parameter, or create a file with .cmd  extension that has the following contents (the example below is for  64-bit version of The Bat! with the command-line parameter  /TLS_DISABLE_PERFECT_FORWARD_SECRECY) and run this .cmd-file to run The  Bat! :
"C:\Program Files\The Bat!\thebat64.exe" /TLS_DISABLE_PERFECT_FORWARD_SECRECY

To figure out whether you are using an antivirus or not, check the mail account log (Ctrl+Shift+A) of the version of The Bat! that still connects. In case of GMail, the log line should look something like the following:

Code
03.07.2018, 18:50:08: IMAP  - Connecting to IMAP server imap.gmail.com on port 993
03.07.2018, 18:50:08: IMAP  - Initiating TLS handshake
03.07.2018, 18:50:08: IMAP  - Certificate S/N: 7B56C8C2401526C5, algorithm: RSA (2048 bits), issued from 6/19/2018 11:40:14 AM to 8/28/2018 1:32:00 AM,  for 1 host(s): imap.gmail.com.
03.07.2018, 18:50:08: IMAP  - Owner: "US", "California", "Mountain View", "Google LLC", "imap.gmail.com".
03.07.2018, 18:50:08: IMAP  - Issuer: "US", "Google Trust Services", "Google Internet Authority G3". Valid from 6/15/2017 12:00:42 AM to 12/15/2021 12:00:42 AM.
03.07.2018, 18:50:08: IMAP  - Root: "GlobalSign Root CA - R2", "GlobalSign", "GlobalSign". Valid from 12/15/2006 8:00:00 AM to 12/15/2021 8:00:00 AM.
03.07.2018, 18:50:09: IMAP  - TLS handshake complete
03.07.2018, 18:50:09: IMAP  - Connected to IMAP server (imap.gmail.com)
03.07.2018, 18:50:09: IMAP  - Gimap ready for requests from 93.116.229.36 u6-v6mb618275477wmc
03.07.2018, 18:50:09: IMAP  - Authenticating (user: "yourmailbox@gmail.com", method: "XOAUTH2")...
03.07.2018, 18:50:09: IMAP  - IMAP server authentication OK, server says "yourmailbox@gmail.com authenticated (Success)"



Pay attention to the lines "Owner" and "Root". If you see something like "Google LLC" as owner and "GlobalSign" as root, then the antivirus does not break the connection. But if you see your antivirus name there, then it does.
 
 
 
#9
0  
Hello,

The problem is now solved.

I have Kaspersky Internet Security 2019.

I desactivate Kaspersky SSL/TSL Root certificate and now it works like a charm.


The problem was Kaspersky Root Certificate.


Do you have Kaspersky anti-virus?


It works now with the BAT 8.5.2 TLS.
 
 
 
#10
0  
can I ask how you have disabled Kaspersky Root Certificate? thank you very much.
 
 
 
#11
0  
You can use The Bat! 8.5.4 available to download from https://www.ritlabs.com/en/products/thebat/download.php

This version resolves TLS 1.2 compatibility issues. Connection failures were caused by mail server servers which aborted the connection unless The Bat! sends signature_algorithms ClientHello extension on TLS 1.2. To resolve this incompatibility, The Bat! since version 8.5.4 always sends the signature_algorithms extension during TLS 1.2 handshake.
 
 
 
#12
0  
Quote
Krnac Martin wrote:
can I ask how you have disabled Kaspersky Root Certificate? thank you very much.

You can disable Kaspersky Root certificate in settings and click on advanced then click on network.
A window open with network settings of Kaspersky.

Then you can choose to disable Kaspersky HTTPS analysis.
 
 
 
#13
0  
Quote
Maxim Masiutin wrote:
You can use The Bat! 8.5.4 available to download from  https://www.ritlabs.com/en/products/thebat/download.php

This version resolves TLS 1.2 compatibility issues. Connection failures were caused by mail server servers which aborted the connection unless The Bat! sends signature_algorithms ClientHello extension on TLS 1.2. To resolve this incompatibility, The Bat! since version 8.5.4 always sends the signature_algorithms extension during TLS 1.2 handshake.
Hello,

It works well with The Bat! 8.5.4 . I have no longer TLS problems.
I can now reactivate Kaspersky.

Thanks again.
 
 
 
Pages: 1