Author |
|
labv Newbie
Joined: 23 May 2016
Online Status: Offline Posts: 3
|
Posted: 23 May 2016 at 1:17am | IP Logged
|
|
|
We experience login problems when using Mailbee Objects from a Windows service. A separate normal Windows application is able to log in correctly. This problem happens with Mailbee DLL version 9.0.0.213. Previously the application used version 5.6.0.136, and if I revert back to this old version, the problem disappears.
1. Problem at a customer site
IMAP login fails:
Error code: 312
Server reply: MBC000002 NO AUTHENTICATE failed.
The service is run as a particular user.
2. Problem with our own server
This login problem only happens when running the service as Local System (SYSTEM), combined with NTLM login (regular login works).
Running the service as Local System (SYSTEM):
08:47:15 [MailBee POP3 v9.0.0.212. Registered version]
08:47:15 [Connecting to server 192.168.0.100 at port 110]
08:47:15 [Using NTLM/MSN/GSSAPI authentication]
08:47:15 [Sending AUTH NTLM\r\n]
08:47:15 [Sending NTLM/MSN/GSSAPI Request]
08:47:15 [Error: Incorrect credentials]
08:47:15 [Server responded: + TlRMTVNTUAACAAAAEAAQADgAAAA1gonil+r1QbxYgLwAAAAAAAAAAJoAmgBIAAAABQLODgAAAA9WAEkARABJAEMATwBEAEUAAgAQAFYASQBEAEkAQwBPAEQARQABAB4AVgBJAEQASQBDAE8ARABFAFMARQBSAFYARQBSADEABAAcAHYAaQBkAGkAYwBvAGQAZQAuAGwAbwBjAGEAbAADADwAVgBJAEQASQBDAE8ARABFAFMARQBSAFYARQBSADEALgB2AGkAZABpAGMAbwBkAGUALgBsAG8AYwBhAGwAAAAAAA==\r\n]
08:47:15 [Possible error reason: incorrect domain name, username or password]
Similarly for IMAP:
09:53:53 [MailBee IMAP4 v9.0.0.212. Registered version]
09:53:53 [Connecting to server 192.168.0.100 at port 143]
09:53:53 [Using secure authentication]
09:53:53 [Sending command: MBC000001 AUTHENTICATE NTLM\r\n]
09:53:53 [Sending encoded NTLM/MSN/GSSAPI Request]
09:53:53 [Error: Incorrect credentials]
09:53:53 [Server responded: TlRMTVNTUAACAAAAEAAQADgAAAA1gonipgqcWt6pU00AAAAAAAAAAJoAmgBIAAAABQLODgAAAA9WAEkARABJAEMATwBEAEUAAgAQAFYASQBEAEkAQwBPAEQARQABAB4AVgBJAEQASQBDAE8ARABFAFMARQBSAFYARQBSADEABAAcAHYAaQBkAGkAYwBvAGQAZQAuAGwAbwBjAGEAbAADADwAVgBJAEQASQBDAE8ARABFAFMARQBSAFYARQBSADEALgB2AGkAZABpAGMAbwBkAGUALgBsAG8AYwBhAGwAAAAAAA==]
09:53:53 [Possible error reason: incorrect domain name, username or password]
09:53:53 [Error: Connection failure]
Running the service as a particular user works (for this problem):
09:22:40 [MailBee POP3 v9.0.0.212. Registered version]
09:22:40 [Connecting to server 192.168.0.100 at port 110]
09:22:40 [Using NTLM/MSN/GSSAPI authentication]
09:22:40 [Sending AUTH NTLM\r\n]
09:22:40 [Sending NTLM/MSN/GSSAPI Request]
09:22:40 [Sending NTLM/MSN/GSSAPI Response]
09:22:40 [Connected to the server, getting statistics]
09:22:40 [Got stat, 0 message(s) available. Total size is 0 bytes]
09:22:40 [Disconnecting from the server]
09:22:40 [Connection closed]
|
Back to Top |
|
|
labv Newbie
Joined: 23 May 2016
Online Status: Offline Posts: 3
|
Posted: 23 May 2016 at 1:22am | IP Logged
|
|
|
This question is actually about the ActiveX version of mailbee objects. Sorry wrong subforum.
|
Back to Top |
|
|
Alex AfterLogic Support
Joined: 19 November 2003
Online Status: Offline Posts: 2206
|
Posted: 23 May 2016 at 1:33am | IP Logged
|
|
|
NTLM authentication depends on the context of the currently logged user. Because SYSTEM user does not have a mail account on your Exchange server, you cannot login.
Regards,
Alex
|
Back to Top |
|
|
labv Newbie
Joined: 23 May 2016
Online Status: Offline Posts: 3
|
Posted: 23 May 2016 at 7:16am | IP Logged
|
|
|
Strange then that version 5 is able to login in using NTLM, even as SYSTEM. Anyway, actually the more important issue for us is the first problem mentioned.
Error code: 312, Server reply: MBC000002 NO AUTHENTICATE failed.
Any idea what is the problem there?
|
Back to Top |
|
|
Alex AfterLogic Support
Joined: 19 November 2003
Online Status: Offline Posts: 2206
|
Posted: 23 May 2016 at 9:27am | IP Logged
|
|
|
"MBC000002 NO AUTHENTICATE failed." needs to be checked on the server (in its logs, maybe). The server just says "failed", it does not explain the reason. No error code, nothing. So you'll need to discuss this with the server admin.
Quote:
Strange then that version 5 is able to login in using NTLM, even as SYSTEM.
|
|
|
Old version utilized its own implementation of NTLM, not relying on Windows. The main disadvantage of that method was the lack of ability to use the context of the current Windows user (so that password had always to be provided). Modern implementation is fine with empty creds. if you're supplying creds, you may need to try different schemas of login name: user@domain, user\domain, domain\user.
Or, you can use regular login via SSL/TLS connection or just regular login only (as both the server and the client are within the same LAN).
Regards,
Alex
|
Back to Top |
|
|