RE: 4D and Exchange Server with IMAP

2017-06-27 Thread 4dialog via 4D_Tech
-and-Exchange-Server-with-IMAP-tp5752675p5752802.html Sent from the 4D Tech mailing list archive at Nabble.com. ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html

RE: 4D and Exchange Server with IMAP [RESOLVED]

2017-06-20 Thread Dennis, Neil via 4D_Tech
> If you are using domain\user then make sure to escape the \ like this: > Domain\\User I was using the format correctly... To test what was going on I used telnet session went like this: telnet server 143 > *ready message A1 LOGIN "domain\\user" "password" > A1 NO LOGIN failed So I did some

RE: 4D and Exchange Server with IMAP

2017-06-20 Thread Paul Dennis via 4D_Tech
I am just using username not domain\username but I think this is something to do with exchange setup. What error are you getting ? 10061 is the imap proxy whereas 10064 is auth. Can you telnet to port 993 ? -- View this message in context: http://4d.1045681.n5.nabble.com/4D-and-Exchange

RE: 4D and Exchange Server with IMAP

2017-06-20 Thread Timothy Penner via 4D_Tech
Hi, > I'm seeing the same thing, I use domain\username as the user name. I used u...@domain.com format and it worked for me. If you are using domain\user then make sure to escape the \ like this: Domain\\User Let me know if that helps, -Tim

RE: 4D and Exchange Server with IMAP

2017-06-20 Thread Dennis, Neil via 4D_Tech
Paul I'm seeing the same thing, I use domain\username as the user name. I have verified at a low level that the IMAP_Login opens a connection to the exchange server (It looks like the client and server are talking). But IMAP_Login returns an error anyway. I have not found a solution yet.

RE: 4D and Exchange Server with IMAP

2017-06-20 Thread Paul Dennis via 4D_Tech
-and-Exchange-Server-with-IMAP-tp5752675p5752686.html Sent from the 4D Tech mailing list archive at Nabble.com. ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options

RE: 4D and Exchange Server with IMAP

2017-06-20 Thread Paul Dennis via 4D_Tech
a connection but then its closed. Thanks Paul -- View this message in context: http://4d.1045681.n5.nabble.com/4D-and-Exchange-Server-with-IMAP-tp5752675p5752684.html Sent from the 4D Tech mailing list archive at Nabble.com

Re: 4D and Exchange Server with IMAP

2017-06-19 Thread npdennis via 4D_Tech
> Using the correct password, and specifying the last parameter as 1 ("use > SSL"), this works. > ^By works, I mean the command completes within 2 seconds, $ErrorNum is 0, and > vImap_ID is 1 Thanks, good to know. I will double check the password, but I’m pretty sure it was OK as I tried a

RE: 4D and Exchange Server with IMAP

2017-06-19 Thread Timothy Penner via 4D_Tech
Hi Neil, I just tried this with our corporate exchange server: C_LONGINT(vImap_ID) C_TEXT(vHost;vUserName;vUserPassword) vHost:="exchange.notmyactualserver.com" vUserName:="u...@notmyactualserver.com" vUserPassword:="notmyactualpassword" vImap_ID:=0 IT_SetPort (14;993) $ErrorNum:=IMAP_Login

RE: 4D and Exchange Server with IMAP

2017-06-19 Thread Dennis, Neil via 4D_Tech
> Which port are you connecting to? SSL? Is it set using IT_SetPort? I don't specify the port with IT_SetPort, I let IMAP_Login pick the port depending on the SSL flag. I have confirmed that IMAP_Login is using port 143 for clear connection and 993 for SSL/TLS connections. When I test with

RE: 4D and Exchange Server with IMAP

2017-06-19 Thread Timothy Penner via 4D_Tech
Hi Neil, Which port are you connecting to? SSL? Is it set using IT_SetPort? If you are using and older version of 4DIC, then you may need to make sure the password does not contain any special characters (such as & or *). -Tim

4D and Exchange Server with IMAP

2017-06-19 Thread Dennis, Neil via 4D_Tech
Did anyone ever get the IMAP_Login to work with MS Exchange server? When I connect with IMAP_Login I get either a 10061 or a 10064 (connection time out or reset) but when I connect to the same machine and port with TCP_Open I get a valid connection and a response: "* OK The Microsoft Exchange