bestsync.us

Hello,

we are using BestSync 2019 (v14.0.1.7). I've set everything fine, see picture "mail settings".

Log after testing:
SMTP Connecting.
<220 xxx Microsoft ESMTP MAIL Service ready at Mon, 24 Jan 2022 15:58:01 +0100
>EHLO VM-SFLHAM-SFA01
<250-xxx Hello [10.226.80.120]
250-SIZE
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-X-ANONYMOUSTLS
250-AUTH NTLM
250-X-EXPS GSSAPI NTLM
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250-XEXCH50
250-XRDST
250 XSHADOW

Failed to establish connection with SMTP server.


I have also added a screenshot of wireshark, marked the difference to the next below.

I programmed a little test-tool which uses same server settings and can send emails, wireshark output can be found on the third picture.

Somehow the authentication is missing in the bestsync test.

Hope you can help us

The cause of the problem is that BestSync does not support NTLM authentication now.
Please give us one or two weeks to impliment the function.

Hey, this sounds good

Will this change also be available for BestSync 2019 or do we have to upgrade to the newest version?

Regards

We have released BestSync 2022 Version 17.0.0.5.
The new version supported NTLM authentication when it sends emails through IIS's SMTP service.
Please try the new version to see if it resolved the problem.
I'm sorry that we only implement new features on the newest version.

Hello,

i tried the new version. Sadly it doesn't work yet.

I've added a new screenshot. NTLM authentication starts but gives back a wrong authentication. If you compare the new screenshot with the third one above, you can see, that the encrypted part is different from the working one in my test.

Regards

We have tested on our Windows Server 2019, BestSync worked fine.
Could you please tell me the version of you windows server, or is it possible that you create a test account for us to debug this problem?
You can send the test account to risefly@risefly.com.

Hey,

I tried it on Windows Server 2012 R2. Sadly there is no option to get access to the server from external.

Today I did another test on Windows Server 2016 with following result:

>EHLO SW-HAMLHT-V511
<250-smailin.ads.dlh.de Hello [57.57.252.59]
250-SIZE 37748736
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-AUTH
250-8BITMIME
250-BINARYMIME
250 CHUNKING
SMTP Send mail.

With my working tool I got this with difference after STARTTLS.

From the log message, I can see that you have not enabled the "Integrated Windows Authentication" option in the "Authentication" settings of the "properties" setting of the SMTP server.

We have installed a Windows Server 2012 server and Tested the Email function of BestSync, the function worked fine in the test.

Here is the test log in the Windows Server 2012:
SMTP Connecting.
<220 WIN-SERVER2012 Microsoft ESMTP MAIL Service, Version: 8.5.9600.16384 ready at Thu, 10 Feb 2022 23:32:10 -0800
>EHLO WIN-SERVER2012
<250-WIN-SERVER2012 Hello [192.168.56.108]
250-AUTH NTLM
250-TURN
250-SIZE 2097152
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250 OK
>AUTH NTLM TlRMTVNTUAABAAAABTIAAA4ADgAuAAAADgAOACAAAABXSU4tU0VSVkVSMjAxMldJTi1TRVJWRVIyMDEy
<334 TlRMTVNTUAACAAAAHAAcADgAAAAFAoICkVV5kZd2ZVUAAAAAAAAAAJAAkABUAAAABgOAJQAAAA9XAEkATgAtAFMARQBSAFYARQBSADIAMAAxADIAAgAcAFcASQBOAC0AUwBFAFIAVgBFAFIAMgAwADEAMgABABwAVwBJAE4ALQBTAEUAUgBWAEUAUgAyADAAMQAyAAQAHABXAEkATgAtAFMARQBSAFYARQBSADIAMAAxADIAAwAcAFcASQBOAC0AUwBFAFIAVgBFAFIAMgAwADEAMgAHAAgADbH8ehkf2AEAAAAA
>TlRMTVNTUAADAAAAGAAYAIAAAAAYABgAmAAAABwAHABAAAAACAAIAFwAAAAcABwAZAAAAAAAAACwAAAAAQIAAFcASQBOAC0AUwBFAFIAVgBFAFIAMgAwADEAMgB6AGgAbwB1AFcASQBOAC0AUwBFAFIAVgBFAFIAMgAwADEAMgD0efaNgvbv03d9P43KuHBuyj+Zo/Ef4fLSp34kOXSVnhzJgY0oiphZfc2IsecSsRo=
<235 2.7.0 Authentication successful
SMTP Send mail.
>MAIL FROM:<zhou@192.168.56.108>
<250 2.1.0 zhou@192.168.56.108....Sender OK
>RCPT TO:<risefly@risefly.com>
<250 2.1.5 risefly@risefly.com
>DATA
<354 Start mail input; end with <CRLF>.<CRLF>
>From: zhou@192.168.56.108
>To:
>risefly@risefly.com
>
>Subject:
>BestSync 2022 Testing Mail
>
>MIME-Version: 1.0
>X-Mailer: BestSync
>Date:Fri, 11 Feb 2022 07:32:10 GMT
>Content-Type: text/plain;
charset=utf-8
Sending mail text.
>
>
>
.
<250 2.6.0 <WIN-SERVER20121XvpF00000003@WIN-SERVER2012> Queued mail for delivery
SMTP Send mail OK.
>QUIT
<221 2.0.0 WIN-SERVER2012 Service closing transmission channel
SMTP Close.

Hello,

on Windows Server 2012 it doesn't work for me. But on Windows Server 2016 it does! (I had forgotten to set the recipient and so the test mail went into nirvana... )

Because Windows Server 2016 is the destination os on which currently BestSync 2019 is running, I hope that the mail sending will work on that system If not I'll get in touch with you again.