Re: TLS Handshake and Certificate problems

2020-04-16 Thread Thomas Fernandez
Hello Paul,

On Thu, 16 Apr 2020 10:59:28 -0400 GMT (16-Apr-20, 21:59 +0700 GMT),
Paul Van Noord wrote:

> 4/16/2020  10:41 AM

> Hi Thomas,

> On 4/15/2020 Thomas Fernandez wrote:

TF>> Hello Paul,

TF>> On Wed, 15 Apr 2020 11:17:14 -0400 GMT (15-Apr-20, 22:17 +0700 GMT),
TF>> Paul Van Noord wrote:

>> There will have been a reason for that, don't you think?

> Isn't the Beta usually taken down when Ritlabs issues a new Beta
> or release version?

TF That's correct. It has become useless, as any bugs found should not be
TF distributed any more. That's the whole idea of beta testing.

>>> There have been multiple occasions in the past where a given beta caused
>>> problems  for me requiring me to go to a previous version. This is why I
>>> keep  copies  of  all acceptable betas. "Latest and greatest" are not
>>> synonymous!

TF>> Yes, beta versions can have problems, that's why users of beta
TF>> versions are called beta testers, and they participate in the beta
TF>> forum (or mailing list, as it is in the case of TheBat) and report
TF>> back. There is never a reason for someone who is not a beta tester to
TF>> download any beta version.

TF>> Once the release version is out, there is no need to revert back to a
TF>> beta version.

TF>> Otherwise, there would be something fundamentally wrong with the beta
TF>> process. I'm not saying saying this never happens in the world, I am
TF>> just saying it would be highly unusual if you have to revert back from
TF>> a release version to a beta version to make have a better version.

> I  have  been  a  TB user for 32 years. I have been a beta tester for at
> least 12 years. Perhaps my TB experience exceeds your experience. I have
> clients  all  over  the  world.  I  fail to appreciate someone of lesser
> experience  telling me the "facts". A closed mind slams the door shut on
> ability to learn.

You are right here, I bow to your experience. I have only be a beta
tester for TB for 21 years. My MSc in Computing is already more than
10 years old, and my programming skills that started in 1978 are a bit
rusty by now, so they don't count. I feel privileged to have found a
master in you.

> My  methods  have  proven their value in the test of time and experience
> for  me  and  my  clients.  Since  I highly customize the TB ui for each
> client.  It  is  absurd  that a release of a MSI would be published with
> this  glaring  defect.  It  forced  me  back  to  a  beta  where Toolbar
> Customization worked as it did for many years!

Yes, as I said: It is the exception. The exception does not make it a
rule though. If I were you, I would not use beta versions with my
clients, but that's your decision. I would test the new releases
myself before upgrading, and if I cannot recommend them, would go back
to the previous release. Not any beta version; I would recommend them
only for beta testers, never for production and especially not for
clients.

But that's me, and people work differently. And here is a fact: I hope
the IT guy in my company does not install any beta versions on our
computers.

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.14 (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-16 Thread Thomas Fernandez
Hello Andrew,

On Thu, 16 Apr 2020 20:11:14 +0930 GMT (16-Apr-20, 17:41 +0700 GMT),
Andrew Savchenko wrote:

>> This is getting off-topic. Anyway, I am not a beta tester for Windows,
>> and the update is automatic. I am not following the Win10 version
>> numbers and never had a desire to go back to any beta version before
>> the release version that I am using. There is absolutely no reason to
>> go back to a beta version that is older than the release version you
>> are using, is there?

> I agree with the "off-topic" statement. Let's say we have our
> differences, which is fine, as both approaches have right for existence.

OK.

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.14 (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-16 Thread Thomas Fernandez
Hello Andrew,

On Thu, 16 Apr 2020 19:23:49 +0930 GMT (16-Apr-20, 16:53 +0700 GMT),
Andrew Savchenko wrote:

> Hello Thomas,

> Thursday, April 16, 2020, 10:40:58 AM, you wrote:

>> There is never a reason for someone who is not a beta tester to
>> download any beta version.

>> Once the release version is out, there is no need to revert back to a
>> beta version.

> Those are rather broad statements.

>> Message reply created with The Bat! Version 9.1.14 (64-bit)
>> under Windows 10.0 Build 18362

> Following the logic from above, how come you are not running the latest
> stable Windows? Build 18362 is neither most recent one nor LTSC.

This is getting off-topic. Anyway, I am not a beta tester for Windows,
and the update is automatic. I am not following the Win10 version
numbers and never had a desire to go back to any beta version before
the release version that I am using. There is absolutely no reason to
go back to a beta version that is older than the release version you
are using, is there?

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.14 (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-15 Thread Thomas Fernandez
Hello Paul,

On Wed, 15 Apr 2020 11:17:14 -0400 GMT (15-Apr-20, 22:17 +0700 GMT),
Paul Van Noord wrote:

 There will have been a reason for that, don't you think?

>>> Isn't the Beta usually taken down when Ritlabs issues a new Beta
>>> or release version?

TF>> That's correct. It has become useless, as any bugs found should not be
TF>> distributed any more. That's the whole idea of beta testing.

> There have been multiple occasions in the past where a given beta caused
> problems  for me requiring me to go to a previous version. This is why I
> keep  copies  of  all acceptable betas. "Latest and greatest" are not
> synonymous!

Yes, beta versions can have problems, that's why users of beta
versions are called beta testers, and they participate in the beta
forum (or mailing list, as it is in the case of TheBat) and report
back. There is never a reason for someone who is not a beta tester to
download any beta version.

Once the release version is out, there is no need to revert back to a
beta version.

Otherwise, there would be something fundamentally wrong with the beta
process. I'm not saying saying this never happens in the world, I am
just saying it would be highly unusual if you have to revert back from
a release version to a beta version to make have a better version.

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.14 (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-15 Thread MAU
Hello Paul,

> There have been multiple occasions in the past where a given beta caused
> problems  for me requiring me to go to a previous version. This is why I
> keep  copies  of  all acceptable betas. "Latest and greatest" are not
> synonymous!

While  I  see  your point and kind of a agree with you, I do not agree
with  your  "method"  of  using  betas.  Downloading  betas is for the
purpose  of  helping  Ritlabs  to  test new features or changes to TB.
Downloading  or  using "older betas" defeats this purpose and, anyway,
betas should not be used por production work.

-- 
Best regards,

Miguel A. Urech (Els Poblets (Alicante) - Spain)
Using The Bat! v9.1.14





Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-14 Thread Thomas Fernandez
Hello MFPA,

On Tue, 14 Apr 2020 16:26:49 +0100 GMT (14-Apr-20, 22:26 +0700 GMT),
MFPA wrote:

> On Tuesday 14 April 2020 at 12:43:19 PM, in
> , Thomas Fernandez wrote:-


>> There will have been a reason for that, don't you think?

> Isn't the Beta usually taken down when Ritlabs issues a new Beta
> or release version?

That's correct. It has become useless, as any bugs found should not be
distributed any more. That's the whole idea of beta testing.

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.14 (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-14 Thread MFPA
Hi


On Tuesday 14 April 2020 at 12:43:19 PM, in
, Thomas Fernandez wrote:-


> There will have been a reason for that, don't you think?

Isn't the Beta usually taken down when Ritlabs issues a new Beta 
or release version?

-- 
Best regards

MFPA  

To steal ideas from one person is plagiarism; 
to steal from many is research.

Using The Bat! Version 8.8.2.5 (BETA) (64-bit) on Windows 10.0 Build 18362  



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-14 Thread Thomas Fernandez
Hello Thomas,

On Mon, 13 Apr 2020 23:08:09 +0700 GMT (13-Apr-20, 23:08 +0700 GMT),
Thomas Fernandez wrote:

TF>>> Anyway, I have never used command line parameters. I just added that
TF>>> parameter in the shortcut (with and without blank after ...exe) but
TF>>> Windows complains. What should I do?

>> This one worked for me:

>> "C:\Program Files\The Bat!\thebat64.exe" /tls_disable_ecdhe

>> Hope it helps.

> Yes it did, and guess what: I just downloaded the mails from my Gmail
> account! Thanks.

> Note (FWIW): It works when using the gmail.com servers. On the other
> account, which I set to googlemail.com, TB asked me for the password.
> Of course, I hadn't changed it, but I changed the servers to gmail.com
> and it worked.

When sending, TB sends me a pop-up dialog each and every single time.
I have to click OK, but there is no way that I can say "accept this
cert for good".

Update: I just switched from "Internal Implementation" back to
"Microsoft CryptoAPI", and now the dialog does not appear any more.

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.14 (64-bit)
under Windows 10.0 Build 18362

Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-14 Thread Thomas Fernandez
Hello Andrew,

On Tue, 14 Apr 2020 21:03:04 +0930 GMT (14-Apr-20, 18:33 +0700 GMT),
Andrew Savchenko wrote:

>> Good to hear. Don't download from unauthrotised sites.
[...]

> v8.8.9.12 files were removed from RT's website, that is the only reason I
> have provided those links.

There will have been a reason for that, don't you think?

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.14 (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-14 Thread Thomas Fernandez
Hello Luca,

On Tue, 14 Apr 2020 12:20:31 +0200 GMT (14-Apr-20, 17:20 +0700 GMT),
Luca via TBUDL wrote:

> Andrew Savchenko:

>> Hello Paul,
>>
>> Friday, April 10, 2020, 7:43:01 AM, you wrote:
>>
>> >>> I'm comfy with the late v.8, I would appreciate very much if I could 
>> >>> downgrade
>> >>> and keep on with that while v.9 grows mature.
>>
>> S>> I wholeheartedly agree!
>> S>> The customization, where even available, doesn't stick. It reverts
>> S>> back to the default after each restart!
>>
>> > The behavior is the same here.
>>
>> Latest v8 beta available in public:
>> https://mega.nz/file/JktHDQDT#zki2R-F6loABaYNkKeVa_H5nPtPt4Wg9QaMEUDH9KSk
>> http://uploaded.net/file/gvpoinfr

> It won't work!

Good to hear. Don't download from unauthrotised sites.

> A new 8.x release should be issued to solve the problem. I cannot
> see any on the beta list.

Here are the release versions: 
https://www.ritlabs.com/en/products/thebat/archive-versions.php
The release version of v8 was issued after *all* the betas for v8. Why
you want to download a beta version with bugs that there fixed in the
release is beyond me.

If you are interested in contributing to beta testing though, it will
be better to subscribe to TBBETA and get the versions from Ritlabs
rather than from some unauthorised sites where you don't know what you
actually download.

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.14 (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-13 Thread Thomas Fernandez
Hello Thomas,

On Mon, 13 Apr 2020 23:08:09 +0700 GMT (13-Apr-20, 23:08 +0700 GMT),
Thomas Fernandez wrote:

TF>>> Anyway, I have never used command line parameters. I just added that
TF>>> parameter in the shortcut (with and without blank after ...exe) but
TF>>> Windows complains. What should I do?

>> This one worked for me:

>> "C:\Program Files\The Bat!\thebat64.exe" /tls_disable_ecdhe

>> Hope it helps.

> Yes it did, and guess what: I just downloaded the mails from my Gmail
> account! Thanks.

> Note (FWIW): It works when using the gmail.com servers. On the other
> account, which I set to googlemail.com, TB asked me for the password.
> Of course, I hadn't changed it, but I changed the servers to gmail.com
> and it worked.

When sending, TB sends me a pop-up dialog each and every single time.
I have to click OK, but there is no way that I can say "accept this
cert for good".

Update: I just switched from "Internal Implementation" back to
"Microsoft CryptoAPI", and now the dialog does not appear any more.

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.14 (64-bit)
under Windows 10.0 Build 18362

Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-13 Thread Thomas Fernandez
Hello David,

On Mon, 13 Apr 2020 09:57:44 -0600 GMT (13-Apr-20, 22:57 +0700 GMT),
David Shepherd wrote:

> Monday, April 13, 2020, 9:39:36 AM, you wrote:

TF>> Anyway, I have never used command line parameters. I just added that
TF>> parameter in the shortcut (with and without blank after ...exe) but
TF>> Windows complains. What should I do?

> This one worked for me:

> "C:\Program Files\The Bat!\thebat64.exe" /tls_disable_ecdhe

> Hope it helps.

Yes it did, and guess what: I just downloaded the mails from my Gmail
account! Thanks.

Note (FWIW): It works when using the gmail.com servers. On the other
account, which I set to googlemail.com, TB asked me for the password.
Of course, I hadn't changed it, but I changed the servers to gmail.com
and it worked.

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.12.1 (BETA) (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-13 Thread David Shepherd


Monday, April 13, 2020, 9:39:36 AM, you wrote:


TF> Anyway, I have never used command line parameters. I just added that
TF> parameter in the shortcut (with and without blank after ...exe) but
TF> Windows complains. What should I do?

Hello Thomas,

This one worked for me:


"C:\Program Files\The Bat!\thebat64.exe" /tls_disable_ecdhe

Hope it helps.

Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-13 Thread Thomas Fernandez
Hello MFPA,

On Mon, 13 Apr 2020 14:41:35 +0100 GMT (13-Apr-20, 20:41 +0700 GMT),
MFPA wrote:

> On Sunday 12 April 2020 at 3:39:44 AM, in
> , Thomas Fernandez wrote:-

>> Interesting, because my error message mentions avast:

>>>[...]
>>>12-Apr-20, 09:31:04: FETCH - Issuer: generated by
>>>avast! antivirus for SSL/TLS scanning, avast! Web/Mail
>>>Shield, avast! Web/Mail Shield Root.

> Avast inserts itself as a proxy or "man in the middle" to be able to
> scan the traffic on SSL/TLS/HTTPS connections. That's why the
> certificate says "generated by avast! antivirus for SSL/TLS scanning".
> That certificate is only used to encrypt the connection from Avast to
> The Bat!. A quick web search on "antivirus tls scanning" suggests that
> AVG and Kapersky do it this way as well

So it is not an avast problem but a TB problem. I think we already
established that.

> Do you get the same if, under Options | S/MIME and TLS..., you tell
> The Bat! to use Microsoft CryptoAPI (Windows Certificate Store)
> instead of Internal Implementation (The Bat! Address Book)?

Yes. I did that some time ago, I forgot the reason. I have now
switched it back to Internal Implementation, but to no avail. Even
after restart of TB, I still get the same error message.

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.12.1 (BETA) (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-13 Thread Thomas Fernandez
Hello MFPA,

On Mon, 13 Apr 2020 15:48:02 +0100 GMT (13-Apr-20, 21:48 +0700 GMT),
MFPA wrote:

> On Monday 13 April 2020 at 2:41:35 PM, in
> , MFPA wrote:-

> Never mind what else I wrote. I have a gmail account I rarely use. I
> checked incoming mail and got the "certificate cannot be used for this
> purpose" error message.

I had this error in the beginning. Now it is "TLS protocol error:
Internal error BuildClientKeyExchange."

> The solution that has worked for me for the last ten minutes is to use
> the command line parameter /tls_disable_ecdhe as suggested at
> https://support.google.com/mail/thread/38537691?hl=en#recommended-answers.
> I'll just have to remember to remove the command line parameter when I
> migrate to a TB! version 9.1910 or higher.

In that thread, Max says that the problem is solved in 9.1.10. That is
not the case.

Anyway, I have never used command line parameters. I just added that
parameter in the shortcut (with and without blank after ...exe) but
Windows complains. What should I do?

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.12.1 (BETA) (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-13 Thread MFPA
Hi


On Monday 13 April 2020 at 2:41:35 PM, in
, MFPA wrote:-


> Hi

Never mind what else I wrote. I have a gmail account I rarely use. I 
checked incoming mail and got the "certificate cannot be used for this 
purpose" error message.

The solution that has worked for me for the last ten minutes is to use 
the command line parameter /tls_disable_ecdhe as suggested at 
https://support.google.com/mail/thread/38537691?hl=en#recommended-answers. 
I'll just have to remember to remove the command line parameter when I 
migrate to a TB! version 9.1910 or higher.


-- 
Best regards

MFPA  

I'd give my right arm to be ambidextrous.

Using The Bat! Version 8.8.2.5 (BETA) (64-bit) on Windows 10.0 Build 18362  



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-13 Thread MFPA
Hi


On Sunday 12 April 2020 at 3:39:44 AM, in
, Thomas Fernandez wrote:-



> Interesting, because my error message mentions avast:

>>[...]
>>12-Apr-20, 09:31:04: FETCH - Issuer: generated by
>>avast! antivirus for SSL/TLS scanning, avast! Web/Mail
>>Shield, avast! Web/Mail Shield Root.

Avast inserts itself as a proxy or "man in the middle" to be able to
scan the traffic on SSL/TLS/HTTPS connections. That's why the
certificate says "generated by avast! antivirus for SSL/TLS scanning".
That certificate is only used to encrypt the connection from Avast to
The Bat!. A quick web search on "antivirus tls scanning" suggests that
AVG and Kapersky do it this way as well

Do you get the same if, under Options | S/MIME and TLS..., you tell
The Bat! to use Microsoft CryptoAPI (Windows Certificate Store)
instead of Internal Implementation (The Bat! Address Book)?

-- 
Best regards

MFPA  

Never interrupt me when I'm trying to interrupt you.

Using The Bat! Version 8.8.2.5 (BETA) (64-bit) on Windows 10.0 Build 18362  



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems (Gmail)

2020-04-12 Thread Thomas Fernandez
Hello Assad,

On Sun, 12 Apr 2020 13:25:24 +0400 GMT (12-Apr-20, 16:25 +0700 GMT),
Assad Baroot wrote:

>>> Maxim wrote this in the list of changes in version 9.1.10:
>>>
>>> [-] The Bat! did require "Key Encipherment" or "Key Agreement" in
>>> "Key Usage" certificate attribute for TLS even if the certificate
>>> was only used to sign ephemeral keys to provide perfect forward
>>> secrecy. If a server only supports perfect forward secrecy TLS
>>> cipher suites, the certificate used by this server may have no
>>> "Key Encipherment" or "Key Agreement" in the "Key Usage"
>>> attribute.

M>> I  wish  I could understand what all that means, sounds "like Chinese"
M>> to me.

>  I don't understand either but since this version, I no longer get
>  the   TLS  error.  I  suppose  Maxim  wanted  to say he fixed the
>  certificate problem.

Not working in this version. Since it is not avast (MAU and Avrim
confirmed that they don't use it), I have opened open a bug report:
https://bt.ritlabs.com/view.php?id=1989

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.12.1 (BETA) (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-12 Thread Avram Sacks
I am coming late to this "party," having been offline since April 8.  I use
The Bat for 18 e-mail accounts:   5 private domains, a dormant Yahoo
account, and 12 Gmail accounts.   Beginning April 7 I have been unable to
send mail from any of the Gmail accounts.   The error message is "The
server has aborted the connection."  and, like everyone else, the log file
shows "TLS handshake failure. Invalid server certificate (The certificate
cannot be used for this purpose."

I have never used Avast.  I use Bitdefender and have done so for nearly 6
years and I use The Bat  ver. 7.4.16.  Not version 8 and not version 9.
 My wife has a separate installation of The Bat on her computer (ver
5.8.8), with the same 12 Gmail accounts.Curiously, she doesn't seem to
have any problem sending e-mail from at least two of the 12 Gmail
accounts.  We haven't checked the other 10 accounts.Because I access
this forum from a gmail account, I am only able to send this e-mail because
I have accessed my gmail account online.

Reading  through this thread it appears that a definitive solution has yet
to be found and it seems that updating to the latest version has its own
problems.Maxim may have fixed the problem for ver 9.1.10, but it sounds
like ver 9 has other problems.   So, can this problem be fixed from those
of us with earlier versions?  I would not object to upgrading to ver 9, but
it seems that there are other problems with ver. 9.   Should I revert to
ver. 5.8.8?

-- 
Avi

Avram Sacks, using The Bat! Pro ver. 7.1.18 on Win 7 Pro

Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-12 Thread MAU
Hello Thomas,

> What antivirus software do you use?

I  don't  use  any  antivirus  plug-in  specific  for TB. As a general
purpose one I use ESET-NOD32

-- 
Best regards,

Miguel A. Urech (Els Poblets (Alicante) - Spain)
Using The Bat! v9.1.12.1 (BETA)




Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-12 Thread MAU
Hello Assad,

> Maxim wrote this in the list of changes in version 9.1.10:
>
> [-] The Bat! did require "Key Encipherment" or "Key Agreement" in
> "Key Usage" certificate attribute for TLS even if the certificate
> was only used to sign ephemeral keys to provide perfect forward
> secrecy. If a server only supports perfect forward secrecy TLS
> cipher suites, the certificate used by this server may have no
> "Key Encipherment" or "Key Agreement" in the "Key Usage"
> attribute.

I  wish  I could understand what all that means, sounds "like Chinese"
to me.

-- 
Best regards,

Miguel A. Urech (Els Poblets (Alicante) - Spain)
Using The Bat! v9.1.12.1 (BETA)




Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-11 Thread Thomas Fernandez
Hello MAU,

On Sat, 11 Apr 2020 18:00:34 +0200 GMT (11-Apr-20, 23:00 +0700 GMT),
MAU wrote:

> Hello Thomas,

>> I still believe it is caused by avast, though.

> I experienced the intermittent certificate problems a few day ago, and
> I have never ever used Avast.

Interesting, because my error message mentions avast:

>12-Apr-20, 09:31:04: FETCH - Certificate S/N: 
>55ABDA4795C64E4EA2615599FC93D1DC, algorithm: 1.2.840.10045.2.1 (256 bits), 
>issued from 24-Mar-20 06:48:03 to 16-Jun-20 06:48:03, for 1 host(s): 
>pop.gmail.com.
>12-Apr-20, 09:31:04: FETCH - Owner: US, California, Mountain View, Google LLC, 
>pop.gmail.com.
>12-Apr-20, 09:31:04: FETCH - Issuer: generated by avast! antivirus for SSL/TLS 
>scanning, avast! Web/Mail Shield, avast! Web/Mail Shield Root.
!12-Apr-20, 09:31:04: FETCH - TLS protocol error: Internal error 
BuildClientKeyExchange.

What antivirus software do you use?

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.12.1 (BETA) (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-11 Thread Maggie Meister
Hi MAU and Thomas

On Saturday, April 11, 2020 at 12:00:34 PM you wrote:

M> Hello Thomas,

M> I experienced the intermittent certificate problems a few day ago, and
M> I have never ever used Avast.

If it is not avast, then can it be assumed that the problem is
either the Host or TB!?
  

-- 

Best Regards,
Maggie  http://www.OurCabinOnTheCreek.com 


Home is where the books are.


-- 
This email has been checked for viruses by AVG.
https://www.avg.com



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-11 Thread Susanne
Hello,

Saturday, April 11, 2020, 9:00:34 AM, MAU wrote:

> I experienced the intermittent certificate problems a few day ago, and
> I have never ever used Avast.

Same here.

-- 
Best regards,
 Susannemailto:sisk...@gmail.com

Using The Bat! 9.1.12
OS: Windows 10.0 Build 17763 

Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-11 Thread MAU
Hello Thomas,

> I still believe it is caused by avast, though.

I experienced the intermittent certificate problems a few day ago, and
I have never ever used Avast.

-- 
Best regards,

Miguel A. Urech (Els Poblets (Alicante) - Spain)
Using The Bat! v9.1.12.1 (BETA)



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-11 Thread Maggie Meister
Hi Thomas,

On Friday, April 10, 2020 at 11:53:17 PM you wrote:

<...>
TF> FWIW, I have two gmail accouints, one uses the servers gmail.com and
TF> the other googlemail.com. The problem is not intermittent any more,
TF> but it is now reliably producable on both computers:

>>11-Apr-20, 10:49:02: FETCH - Issuer: generated by avast! antivirus for 
>>SSL/TLS scanning, avast! Web/Mail Shield, avast! Web/Mail Shield Root.
TF> !11-Apr-20, 10:49:03: FETCH - TLS protocol error: Internal error 
BuildClientKeyExchange.

TF> I still believe it is caused by avast, though.

I do not usually run current versions of anything, so my TB! is 
7.0.0.56. I also have Avast. We find this problem intermittently. 
While I am not at all technically adept, we have lived with this 
because we believe it is coming from the Server (Hostica or 
Lunarpages). However, we had not considered that it could be 
coming from Avast... Even that is not up to date. My OS is 
Win7Pro., on Panasonic CF-31. 

-- 

Best Regards,
Maggie  http://www.OurCabinOnTheCreek.com 


Discontent is the first step in the progress of a man or a
nation.


-- 
This email has been checked for viruses by AVG.
https://www.avg.com



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-11 Thread Thomas Fernandez
Hello Andrew,

On Sat, 11 Apr 2020 20:55:12 +0930 GMT (11-Apr-20, 18:25 +0700 GMT),
Andrew Savchenko wrote:

> Hello Thomas,

> Saturday, April 11, 2020, 8:35:35 PM, you wrote:

>> There are newer betas... ;-)

> of v8? Please share.

Why would you want a beta version of v8? What would be better in that
version than in the release version?

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.12.1 (BETA) (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-11 Thread Thomas Fernandez
Hello Andrew,

On Sat, 11 Apr 2020 14:12:38 +0930 GMT (11-Apr-20, 11:42 +0700 GMT),
Andrew Savchenko wrote:

> Hello Thomas,

> Saturday, April 11, 2020, 1:58:28 PM, you wrote:

>> Why would you want to download an old beta version?

> Because newer "release" version is not production ready. Check all the
> complains about UI in v9 branch posted to this list in the past weeks.

There are newer betas... ;-)

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.12.1 (BETA) (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-10 Thread Thomas Fernandez
Hello Andrew,

On Sat, 11 Apr 2020 13:43:13 +0930 GMT (11-Apr-20, 11:13 +0700 GMT),
Andrew Savchenko wrote:

> Saturday, April 11, 2020, 1:19:35 PM, you wrote:

>> May I suggest to not download beta versions from any unauthorised
>> sites. If you want to use beta versions, please become a member of the
>> TBBETA discussion group and downlaod the official betas from the
>> Ritlabs website only.

> While "do not download unknown binaries" is generally a good advice,
> these files were removed from RitLabs website.

Right, old betas will be removed when bugs have been found (this is
what beta testing does) and they are replaced by the next beta, or if
Ritlabs is satisfied enough to change them into a release version.

Why would you want to download an old beta version?

That said, I think you would be a good and valuable addition to the
community of TheBat beta testers.

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.12.1 (BETA) (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-10 Thread Thomas Fernandez
Hello Andrew,

On Fri, 10 Apr 2020 11:56:59 +0930 GMT (10-Apr-20, 9:26 +0700 GMT),
Andrew Savchenko wrote:

> Hello Paul,

> Friday, April 10, 2020, 7:43:01 AM, you wrote:

 I'm comfy with the late v.8, I would appreciate very much if I could 
 downgrade
 and keep on with that while v.9 grows mature.

S>>> I wholeheartedly agree!
S>>> The customization, where even available, doesn't stick. It reverts
S>>> back to the default after each restart!

>> The behavior is the same here.

> Latest v8 beta available in public:
> https://mega.nz/file/JktHDQDT#zki2R-F6loABaYNkKeVa_H5nPtPt4Wg9QaMEUDH9KSk
> http://uploaded.net/file/gvpoinfr

May I suggest to not download beta versions from any unauthorised
sites. If you want to use beta versions, please become a member of the
TBBETA discussion group and downlaod the official betas from the
Ritlabs website only.

To subsdcribe, send an email to tbbeta-j...@thebat.dutaint.com

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.12 (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-10 Thread Thomas Fernandez
Hello Thomas,

On Fri, 10 Apr 2020 11:10:02 +0700 GMT (10-Apr-20, 11:10 +0700 GMT),
Thomas Fernandez wrote:

> Hello Thomas,

> On Fri, 10 Apr 2020 10:59:30 +0700 GMT (10-Apr-20, 10:59 +0700 GMT),
> Thomas Fernandez wrote:

>> Hello Maxim,

>> On Thu, 9 Apr 2020 16:17:04 +0300 GMT (09-Apr-20, 20:17 +0700 GMT),
>> Maxim Masiutin via TBUDL wrote:

>>> Thursday, April 9, 2020, 4:11:08 PM, you wrote:

 Yes I did, and restarted the computer.
 Program version 20.2.2401 (build 20.2.5130.567)

 However, I just switched the servers back to googlemail.com and now
 there is no problem. I'll watch it, as it was also intermittent in the
 past, and will report if the problem occurs again.

>>> Can you switch the server to pop.gmail.com?

>>> I've just found that somebody else is also experiencing this issue:
>>> https://www.computerbase.de/forum/threads/gmail-mailabruf-mit-the-bat-und-avast.1936644/

>> That didn't help for exporting the cert from avast, but this did:
>> https://support.postbox-inc.com/hc/en-us/articles/204602300-Invalid-Security-Certificate-Error-when-using-AVAST
>> Scroll down to "Alternative Solution".

>> I successfully exported the cert (in *.der format) and stored it on my
>> HD.

>> When trying to import the cert into TB (Addressbook - View - Windows
>> Certificates - Trusted Root), the browse option was set to defaults
>> *.cer, *.crt. There are some other options in the drop-down menu but
>> not *.der.

>> So I imported the cert anyway (using the All option), but still get
>> the same error. I believe TB cannot read the cert format.

> Update: Avast allows the export of the cert as *.crt (I didn't see
> that before), and now I imported it successfully at the above path.
> However, even after restart of TB, still the same problem.

FWIW, I have two gmail accouints, one uses the servers gmail.com and
the other googlemail.com. The problem is not intermittent any more,
but it is now reliably producable on both computers:

>11-Apr-20, 10:49:02: FETCH - Issuer: generated by avast! antivirus for SSL/TLS 
>scanning, avast! Web/Mail Shield, avast! Web/Mail Shield Root.
!11-Apr-20, 10:49:03: FETCH - TLS protocol error: Internal error 
BuildClientKeyExchange.

I still believe it is caused by avast, though.

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.12 (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-10 Thread Susanne
Hello,

Thursday, April 9, 2020, 7:26:59 PM, Andrew wrote:

> Latest v8 beta available in public:
> https://mega.nz/file/JktHDQDT#zki2R-F6loABaYNkKeVa_H5nPtPt4Wg9QaMEUDH9KSk
> http://uploaded.net/file/gvpoinfr

Does this version not have the certificate problem, or the customization 
troubles?


-- 
Best regards,
 Susannemailto:sisk...@gmail.com

Using The Bat! 9.1.10
OS: Windows 10.0 Build 17763 

Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-09 Thread Thomas Fernandez
Hello Thomas,

On Fri, 10 Apr 2020 10:59:30 +0700 GMT (10-Apr-20, 10:59 +0700 GMT),
Thomas Fernandez wrote:

> Hello Maxim,

> On Thu, 9 Apr 2020 16:17:04 +0300 GMT (09-Apr-20, 20:17 +0700 GMT),
> Maxim Masiutin via TBUDL wrote:

>> Thursday, April 9, 2020, 4:11:08 PM, you wrote:

>>> Yes I did, and restarted the computer.
>>> Program version 20.2.2401 (build 20.2.5130.567)

>>> However, I just switched the servers back to googlemail.com and now
>>> there is no problem. I'll watch it, as it was also intermittent in the
>>> past, and will report if the problem occurs again.

>> Can you switch the server to pop.gmail.com?

>> I've just found that somebody else is also experiencing this issue:
>> https://www.computerbase.de/forum/threads/gmail-mailabruf-mit-the-bat-und-avast.1936644/

> That didn't help for exporting the cert from avast, but this did:
> https://support.postbox-inc.com/hc/en-us/articles/204602300-Invalid-Security-Certificate-Error-when-using-AVAST
> Scroll down to "Alternative Solution".

> I successfully exported the cert (in *.der format) and stored it on my
> HD.

> When trying to import the cert into TB (Addressbook - View - Windows
> Certificates - Trusted Root), the browse option was set to defaults
> *.cer, *.crt. There are some other options in the drop-down menu but
> not *.der.

> So I imported the cert anyway (using the All option), but still get
> the same error. I believe TB cannot read the cert format.

Update: Avast allows the export of the cert as *.crt (I didn't see
that before), and now I imported it successfully at the above path.
However, even after restart of TB, still the same problem.

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.12 (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-09 Thread Thomas Fernandez
Hello Maxim,

On Thu, 9 Apr 2020 16:17:04 +0300 GMT (09-Apr-20, 20:17 +0700 GMT),
Maxim Masiutin via TBUDL wrote:

> Thursday, April 9, 2020, 4:11:08 PM, you wrote:

>> Yes I did, and restarted the computer.
>> Program version 20.2.2401 (build 20.2.5130.567)

>> However, I just switched the servers back to googlemail.com and now
>> there is no problem. I'll watch it, as it was also intermittent in the
>> past, and will report if the problem occurs again.

> Can you switch the server to pop.gmail.com?

> I've just found that somebody else is also experiencing this issue:
> https://www.computerbase.de/forum/threads/gmail-mailabruf-mit-the-bat-und-avast.1936644/

That didn't help for exporting the cert from avast, but this did:
https://support.postbox-inc.com/hc/en-us/articles/204602300-Invalid-Security-Certificate-Error-when-using-AVAST
Scroll down to "Alternative Solution".

I successfully exported the cert (in *.der format) and stored it on my
HD.

When trying to import the cert into TB (Addressbook - View - Windows
Certificates - Trusted Root), the browse option was set to defaults
*.cer, *.crt. There are some other options in the drop-down menu but
not *.der.

So I imported the cert anyway (using the All option), but still get
the same error. I believe TB cannot read the cert format.

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.12 (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-09 Thread Susanne
Hello,

Thursday, April 9, 2020, 10:27:36 AM, Luca wrote:

> I'm comfy with the late v.8, I would appreciate very much if I could downgrade
> and keep on with that while v.9 grows mature.

I wholeheartedly agree!
The customization, where even available, doesn't stick. It reverts back to the 
default after each restart!


-- 
Best regards,
 Susannemailto:sisk...@gmail.com

Using The Bat! 9.1.10
OS: Windows 10.0 Build 17763 

Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-09 Thread Luca via TBUDL
Maxim Masiutin via TBUDL:

> Will release an updated MSI within a few hours.

I just installed Voyager 9.1.10.1, problem with Gmail is gone, but... is there
another way to cope with this recurrent problem? I wouldn't update right now,
I think v.9 is not ready. All my personal buttons on the toolbar are gone and
I can't see a way to get them back, and TB dies trying, already froze a couple
of times in the 'customize' section.

I'm comfy with the late v.8, I would appreciate very much if I could downgrade
and keep on with that while v.9 grows mature.

-- 
Windows 10 Professional 64
The Bat! Voyager Professional Edition 9.1.10.1 (OTFE) 

Luca - e-mail: p.stevens at libero.it



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-09 Thread Maxim Masiutin via TBUDL
Hello Thomas,

Thursday, April 9, 2020, 4:11:08 PM, you wrote:

> Yes I did, and restarted the computer.
> Program version 20.2.2401 (build 20.2.5130.567)

> However, I just switched the servers back to googlemail.com and now
> there is no problem. I'll watch it, as it was also intermittent in the
> past, and will report if the problem occurs again.

Can you switch the server to pop.gmail.com?

I've just found that somebody else is also experiencing this issue: 
https://www.computerbase.de/forum/threads/gmail-mailabruf-mit-the-bat-und-avast.1936644/

-- 
Maxim Masiutin
Ritlabs, SRL
Director



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-09 Thread Thomas Fernandez
Hello Thomas,

On Thu, 9 Apr 2020 20:11:08 +0700 GMT (09-Apr-20, 20:11 +0700 GMT),
Thomas Fernandez wrote:

> Hello Maxim,

> On Thu, 9 Apr 2020 15:49:58 +0300 GMT (09-Apr-20, 19:49 +0700 GMT),
> Maxim Masiutin via TBUDL wrote:

>> Hello Thomas,

>> Thursday, April 9, 2020, 2:44:31 PM, you wrote:

09-Apr-20, 18:37:07: FETCH - Issuer: generated by avast! antivirus for 
SSL/TLS scanning, avast! Web/Mail Shield, avast! Web/Mail Shield Root.
>>> !09-Apr-20, 18:37:08: FETCH - TLS protocol error: Internal error 
>>> BuildClientKeyExchange.

>> Are you sure that you have indeed updated Avast? What version of
>> Avast are you using? We've got information from one persion that
>> after he updated Avast today, the BuildClientKeyExchange error vanished.

> Yes I did, and restarted the computer.
> Program version 20.2.2401 (build 20.2.5130.567)

> However, I just switched the servers back to googlemail.com and now
> there is no problem. I'll watch it, as it was also intermittent in the
> past, and will report if the problem occurs again.

And here we go:

>09-Apr-20, 20:13:45: FETCH - Certificate S/N: 
>55ABDA4795C64E4EA2615599FC93D1DC, algorithm: 1.2.840.10045.2.1 (256 bits), 
>issued from 24-Mar-20 06:48:03 to 16-Jun-20 06:48:03, for 1 host(s): 
>pop.gmail.com.
>09-Apr-20, 20:13:45: FETCH - Owner: US, California, Mountain View, Google LLC, 
>pop.gmail.com.
>09-Apr-20, 20:13:45: FETCH - Issuer: generated by avast! antivirus for SSL/TLS 
>scanning, avast! Web/Mail Shield, avast! Web/Mail Shield Root.
!09-Apr-20, 20:13:45: FETCH - TLS protocol error: Internal error 
BuildClientKeyExchange.

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.10 (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-09 Thread Thomas Fernandez
Hello Maxim,

On Thu, 9 Apr 2020 15:49:58 +0300 GMT (09-Apr-20, 19:49 +0700 GMT),
Maxim Masiutin via TBUDL wrote:

> Hello Thomas,

> Thursday, April 9, 2020, 2:44:31 PM, you wrote:

>>>09-Apr-20, 18:37:07: FETCH - Issuer: generated by avast! antivirus for 
>>>SSL/TLS scanning, avast! Web/Mail Shield, avast! Web/Mail Shield Root.
>> !09-Apr-20, 18:37:08: FETCH - TLS protocol error: Internal error 
>> BuildClientKeyExchange.

> Are you sure that you have indeed updated Avast? What version of
> Avast are you using? We've got information from one persion that
> after he updated Avast today, the BuildClientKeyExchange error vanished.

Yes I did, and restarted the computer.
Program version 20.2.2401 (build 20.2.5130.567)

However, I just switched the servers back to googlemail.com and now
there is no problem. I'll watch it, as it was also intermittent in the
past, and will report if the problem occurs again.

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.10 (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-09 Thread Maxim Masiutin via TBUDL
Hello Thomas,

Thursday, April 9, 2020, 2:44:31 PM, you wrote:

>>09-Apr-20, 18:37:07: FETCH - Issuer: generated by avast! antivirus for 
>>SSL/TLS scanning, avast! Web/Mail Shield, avast! Web/Mail Shield Root.
> !09-Apr-20, 18:37:08: FETCH - TLS protocol error: Internal error 
> BuildClientKeyExchange.

Are you sure that you have indeed updated Avast? What version of Avast are you 
using? We've got information from one persion that after he updated Avast 
today, the BuildClientKeyExchange error vanished.

-- 
Maxim Masiutin
Ritlabs, SRL
Director



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-09 Thread Thomas Fernandez
Hello Luca,

On Thu, 09 Apr 2020 13:13:36 +0200 GMT (09-Apr-20, 18:13 +0700 GMT),
Luca via TBUDL wrote:

>> >> >   starting today, I have intermittent problems sending emails in one 
>> >> > account (so far).
>> >> >   Error message in the log is TLS handshake failure. Invalid server
>> >> > certificate (The certificate cannot be used for this purpose).
>> >> >
>> >> >   Is there a fix for that?
>> >> >
>> >> >   Found this online:
>> >> > https://support.google.com/mail/thread/38537691?hl=en
>> >>
>> >> Did you try this solution (from the website you linked):
>> >>
>> >> change the smtp.gmail.com into
>> >> smtp.googlemail.com
>>
>> > It doesn't work. Same problem here with IMAP.
>>
>> if you fill
>> in the smtp server deetails in the Receiving Mail section, you won't
>> be able to receive any mails in any case.

> I am well aware of that. smtp.googlemail.com doesn't work here as SMTP server.

>> This is what happened over here: Suddenly I couldn't receive mails
>> from gmail any more on my laptop, changed to googlemail. It worked.

> Doesn't work either here.

Funny thing this: I updated TheBat to the latest version, and avast
antivirus. Now my Gmail account works reliably using the gmail.com
servers. If I use googlemail.com, I see an error message in TheBat's
protocol which appears to come from avast (if I read it correctly):

 09-Apr-20, 18:37:07: FETCH - receiving mail messages
 09-Apr-20, 18:37:07: FETCH - Connecting to POP3 server pop.googlemail.com on 
port 995
 09-Apr-20, 18:37:07: FETCH - Initiating TLS handshake
>09-Apr-20, 18:37:07: FETCH - Certificate S/N: 
>50D0051BC4485D4E8AA50D42F12A832B, algorithm: 1.2.840.10045.2.1 (256 bits), 
>issued from 24-Mar-20 06:48:05 to 16-Jun-20 06:48:05, for 1 host(s): 
>pop.googlemail.com.
>09-Apr-20, 18:37:07: FETCH - Owner: US, California, Mountain View, Google LLC, 
>pop.googlemail.com.
>09-Apr-20, 18:37:07: FETCH - Issuer: generated by avast! antivirus for SSL/TLS 
>scanning, avast! Web/Mail Shield, avast! Web/Mail Shield Root.
!09-Apr-20, 18:37:08: FETCH - TLS protocol error: Internal error 
BuildClientKeyExchange.

>> So, as others have said, the problem is intermittent and certainly a
>> problem in Google's side, not TB.

> I do think it's The Bat, because I have the same account with the same
> configuration on my Android smartphone, using K-9 as a client, and there are
> no problem with it.

What anti-virus software are you using?

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.10 (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-09 Thread Luca via TBUDL
Thomas Fernandez:

> Hello Luca,
> 
> On Wed, 08 Apr 2020 12:07:30 +0200 GMT (08-Apr-20, 17:07 +0700 GMT),
> Luca via TBUDL wrote:
> 
> > Thomas Fernandez:
> 
> >> Hello Susanne,
> >>
> >> On Tue, 7 Apr 2020 14:04:34 -0700 GMT (08-Apr-20, 4:04 +0700 GMT),
> >> Susanne wrote:
> >>
> >> >   starting today, I have intermittent problems sending emails in one 
> >> > account (so far).
> >> >   Error message in the log is TLS handshake failure. Invalid server
> >> > certificate (The certificate cannot be used for this purpose).
> >> >
> >> >   Is there a fix for that?
> >> >
> >> >   Found this online:
> >> > https://support.google.com/mail/thread/38537691?hl=en
> >>
> >> Did you try this solution (from the website you linked):
> >>
> >> change the smtp.gmail.com into
> >> smtp.googlemail.com
> 
> > It doesn't work. Same problem here with IMAP.
> 
> if you fill
> in the smtp server deetails in the Receiving Mail section, you won't
> be able to receive any mails in any case.

I am well aware of that. smtp.googlemail.com doesn't work here as SMTP server.

> This is what happened over here: Suddenly I couldn't receive mails
> from gmail any more on my laptop, changed to googlemail. It worked.

Doesn't work either here.

> I could still receive mails on my PC, using gmail. Then suddenly, I
> could not. I was too lazy to change it, and now I can receive them
> again.
> 
> On my laptop, I suddenly could not receive mails from googlemail any
> more. Being busy, I didn't do anything, and now I can receive them
> again.
> 
> So, as others have said, the problem is intermittent and certainly a
> problem in Google's side, not TB.

I do think it's The Bat, because I have the same account with the same
configuration on my Android smartphone, using K-9 as a client, and there are
no problem with it.

-- 
Windows 10 pro 64
The Bat! Voyager Professional Edition 8.8.9.11 (OTFE) 

Luca - e-mail: p.stevens at libero.it






Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-08 Thread Susanne
Hello,

Wednesday, April 8, 2020, 6:58:09 AM, Maxim wrote:

> Will release an updated MSI within a few hours.

I've installed the new version and can now send mail again! Thanks!

A new problem: I can't configure the status bar at all.
Used to have a button for "reply to all quoting selected text) that I use all 
the time.
Can't figure out how to do this now? I can't rearrange the icons either. The 
commands 
page under customize is completely empty for the status bar.


-- 
Best regards,
 Susannemailto:sisk...@gmail.com

Using The Bat! 9.1.10
OS: Windows 10.0 Build 17763 

Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-08 Thread Susanne
Hello,

Wednesday, April 8, 2020, 3:07:30 AM, Luca wrote:

> It doesn't work. Same problem here with IMAP.

Same here. Still intermittent problems, with or without changing to googlemail.
One account only, so far.

-- 
Best regards,
 Susannemailto:sisk...@gmail.com

Using The Bat! 8.8.2
OS: Windows 10.0 Build 17763 

Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-08 Thread Maxim Masiutin via TBUDL
Will release an updated MSI within a few hours.



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-08 Thread Thomas Fernandez
Hello Luca,

On Wed, 08 Apr 2020 12:07:30 +0200 GMT (08-Apr-20, 17:07 +0700 GMT),
Luca via TBUDL wrote:

> Thomas Fernandez:

>> Hello Susanne,
>>
>> On Tue, 7 Apr 2020 14:04:34 -0700 GMT (08-Apr-20, 4:04 +0700 GMT),
>> Susanne wrote:
>>
>> >   starting today, I have intermittent problems sending emails in one 
>> > account (so far).
>> >   Error message in the log is TLS handshake failure. Invalid server
>> > certificate (The certificate cannot be used for this purpose).
>> >
>> >   Is there a fix for that?
>> >
>> >   Found this online:
>> > https://support.google.com/mail/thread/38537691?hl=en
>>
>> Did you try this solution (from the website you linked):
>>
>> change the smtp.gmail.com into
>> smtp.googlemail.com

> It doesn't work. Same problem here with IMAP.

IMAP is an alternative to POP, i.e. for fetching mails. SMTP is for
sending mails, regardless whether you use POP or IMAP. So, if you fill
in the smtp server deetails in the Receiving Mail section, you won't
be able to receive any mails in any case.

This is what happened over here: Suddenly I couldn't receive mails
from gmail any more on my laptop, changed to googlemail. It worked.

I could still receive mails on my PC, using gmail. Then suddenly, I
could not. I was too lazy to change it, and now I can receive them
again.

On my laptop, I suddenly could not receive mails from googlemail any
more. Being busy, I didn't do anything, and now I can receive them
again.

So, as others have said, the problem is intermittent and certainly a
problem in Google's side, not TB.

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.6.2 (BETA) (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-08 Thread Luca via TBUDL
Thomas Fernandez:

> Hello Susanne,
> 
> On Tue, 7 Apr 2020 14:04:34 -0700 GMT (08-Apr-20, 4:04 +0700 GMT),
> Susanne wrote:
> 
> >   starting today, I have intermittent problems sending emails in one 
> > account (so far).
> >   Error message in the log is TLS handshake failure. Invalid server
> > certificate (The certificate cannot be used for this purpose).
> >
> >   Is there a fix for that?
> >
> >   Found this online:
> > https://support.google.com/mail/thread/38537691?hl=en
> 
> Did you try this solution (from the website you linked):
> 
> change the smtp.gmail.com into
> smtp.googlemail.com

It doesn't work. Same problem here with IMAP.

-- 
Windows 10 pro 64
The Bat! Voyager Professional Edition 8.8.9.11 (OTFE) 

Luca - e-mail: p.stevens at libero.it



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-08 Thread MAU
Hello Susanne,

>   starting today, I have intermittent problems sending emails in one account 
> (so far).
>   Error message in the log is TLS handshake failure. Invalid server
> certificate (The certificate cannot be used for this purpose).

I  observed  the  same  thing  yesterday,  intermittent  problems when
sending or receiving with my gmail account. No problem so far today.

>   Is there a fix for that?

I  don't  think  it  is  a  TB  problem. The error messages refer to a
problem with the server (i.e. gmail) certificate. As I say, no problem
today, and my TB is the same that yesterday.

-- 
Best regards,

Miguel A. Urech (Els Poblets (Alicante) - Spain)
Using The Bat! v9.1.6.5 (BETA)




Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-07 Thread Susanne
Hello,

Tuesday, April 7, 2020, 5:19:10 PM, Thomas wrote:
> Did you try this solution (from the website you linked):

No, I haven't! That solution wasn't there yet when I last looked.

Thanks, will try that now!

-- 
Best regards,
 Susannemailto:sisk...@gmail.com

Using The Bat! 8.8.2
OS: Windows 10.0 Build 17763 

Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: TLS Handshake and Certificate problems

2020-04-07 Thread Thomas Fernandez
Hello Susanne,

On Tue, 7 Apr 2020 14:04:34 -0700 GMT (08-Apr-20, 4:04 +0700 GMT),
Susanne wrote:

>   starting today, I have intermittent problems sending emails in one account 
> (so far).
>   Error message in the log is TLS handshake failure. Invalid server
> certificate (The certificate cannot be used for this purpose).
>
>   Is there a fix for that?
>
>   Found this online:
> https://support.google.com/mail/thread/38537691?hl=en

Did you try this solution (from the website you linked):

QUOTE

This works for me:

change the smtp.gmail.com into
smtp.googlemail.com
and change the pop.gmail.com into
pop.googlemail.com

Send mail:
smtp.googlemail.com
Secure to dedicated port (TLS)
Port: 465

receive mail:
pop.googlemail.com
Secure to dedicated port (TLS): Yes
Port: 995

 The Bat! Professional Edition v8.8.9

UNQUOTE

--


Cheers,
Thomas.

Message reply created with The Bat! Version 9.1.6.2 (BETA) (64-bit)
under Windows 10.0 Build 18362



Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html