yes I changed it to 993, but now I know what is happening. There are 2 servers: one backend and one frontend. I was told to connect to the frontend server which listend on 143. The backend server listened on 993.
Now I can login - thanks for your help - the openssl tip gave me the insight. Cheers, Adrian. Am 12.07.2011 17:18, schrieb Ludo Brands: >> when I check Capability I get: >> >> IMAP4,IMAP4rev1,IDLE,LOGIN-REFERRALS,MAILBOX-REFERRALS,NAMESPA >> CE,LITERAL+,UIDPLUS,CHILDREN >> >> So there is no STARTTLS - AutoTLS shouldn't work. >> >> Now I checked the other possibilities of SSLType: >> >> LT_SSLv2: Error error:140650B5:SSL routines:CLIENT_HELLO:no >> ciphers available in function: login >> >> LT_SSLv3: Error error:1408F10B:SSL >> routines:SSL3_GET_RECORD:wrong version number in function: login >> >> LT_TLSv1_1 and LT_SSHv2: Error Network subsystem is unusable in >> function: login >> >> >> I guess, that the IMAP support on this specific exchange >> server is not properly setup. Problem is, that I don't have >> the rights to install anything except my program. So I can't >> check the IMAP support with another email program. >> >> Cheers, Adrian. >> > Connection to port 143 is apparently working (capability returns something). > There isn' t a problem with a firewall blocking the ssl port? Also, when you > specified FullSSL, did you specify TargetPort as this should be set to the > IMAP ssl port used by the server? > > Ludo > ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ synalist-public mailing list synalist-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synalist-public
