Pages: 1
NTLM - Authentication unsuccessful, how to resolve
copied from smtp.log:

[16:46:36] S: 250-8bitmime
[16:46:36] S: 250-AUTH GSSAPI NTLM LOGIN
[16:46:36] S: 250 AUTH=LOGIN
[16:46:36] C: AUTH NTLM
[16:46:36] S: 334 NTLM supported
[16:46:41] S: 535 5.7.3 Authentication unsuccessful.
[16:46:41] C: AUTH LOGIN
[16:46:41] S: 334 VXNlcm5hbWU6
[16:46:41] C: c2VoYXBvbmRlckB0dG1haWwuY29t
[16:46:41] S: 334 UGFzc3dvcmQ6
[16:46:41] C: c2hwOTZzdA==
[16:46:41] S: 235 2.7.0 Authentication successful.

Question 1: how to resolve initial NTLM unsuccessful authentication?

If answer to 1 not available:

Question 2: how to make client opt for AUTH LOGIN instead of AUTH NTLM initially.
Thank you.
You cannot set that client side, the server offers a few options and TB tries the most secure first.
I'm just a user of The Bat! I don't work for Ritlabs.

So two alternatives appear to be available:

a) revert to a previous version of TB; or
b) tackle and wrestle with ISP for a successful NTLM authentication;

if unsuccessful, revert to a) above.

Trying NTML first, then downgrading -so to speak- to LOGIN causes a time delay of 5 seconds -constant. Not to mention the waste of S-C-S traffic and processing burden.

Thank you. Cheers.
Pages: 1