Incoming mail settings with 365

Does the email connector work with office 365? I was able to get the out going mail settings to work fine but get an error with the incoming.
> Connecting to Pop3 server...
> Connecting to Pop3 server...
RqType = 0 WinSock error 10060 Connection timed out

Have tried with both port 110 and 995. I have read previous problems due with TLS and disabling on server end but because this is 365 there is no way to disable this feature. Do you have any suggestions?

Try connecting to it with Stunnel. Click here for an article about using it, while it explains how to use it with Gmail it should be more or less to same.

Thanks for the prompt reply. I have tested the stunnel but seem to be getting the same error messages once more.

2012.06.18 16:12:09 LOG5[3764:2488]: stunnel 4.53 on x86-pc-mingw32-gnu platform
2012.06.18 16:12:09 LOG5[3764:2488]: Compiled/running with OpenSSL 0.9.8s-fips 4 Jan 2012
2012.06.18 16:12:09 LOG5[3764:2488]: Threading:WIN32 SSL:+ENGINE+OCSP+FIPS Auth:none Sockets:SELECT+IPv6
2012.06.18 16:12:09 LOG5[3764:2488]: Reading configuration from file stunnel.conf
2012.06.18 16:12:10 LOG5[3764:2488]: FIPS mode is enabled
2012.06.18 16:12:10 LOG5[3764:2488]: Configuration successful

Is the message I'm getting within stunnel so looks to be configured correctly

It's hard to tell what is causing this. You get a timeout error which probably means that wither the connection request did not get to the 365 mail servers (blocked by your firewall is an option here), the Port number configured is invalid (and thus no response comes back) and maybe the 365 server refuses the connection (though usually in such cases the mail server returns an error saying so).

Please check the settings and let us know how it goes.

I've tried a few more changes and different ports not getting a different message
> Connecting to Pop3 server...
< +OK The Microsoft Exchange POP3 service is ready.
> USER *****
< -ERR Command is not valid in this state.
RqType = 1 POP3 error 500 -ERR Command is not valid in this state.

Thank you for the update. Please send us your RangerMSP log files for analysis. Maybe additional information will be included there. To send us the log files please use the Help > Technical Support menu in RangerMSP.

Issue has now been resolved after much testing and help from CommitCRM Technical Support.
Here is a copy of my stunnel.conf

client = yes
[pop3s]
accept = 127.0.0.1:1109
connect = 365 pop:995

[SMTP Outgoing]
accept = 127.0.0.2:259
connect = 356 smpt:465

Both pop and smtp can be found going through owa, options, see all options, my account,Settings for POP, IMAP, and SMTP access. Mine start with pod...

On the Incoming email setting because you have accept listening for the
IP Loop back/ Localhost in the stunnel.conf

Pop3 host was to be put in just as 'localhost'
Pop3 port 1109

Thank you for posting this and for sharing the resolution with the community. I'm sure it will help others configure RangerMSP to work with Office 365.

You don't need to use stunnel.conf if you are on Commitcrm version 6.0 :)

What's different about 6.0?

It naively supports connections to SSL based mail servers without the need to use Stunnel.