Exchange 2013 SP1 POP3 Not Working

I have a single Exchange 2013 SP1 server that I cannot get POP3 or IMAP to work on.  All Exchange roles are on this server.

I have started both the frontend and backend services for POP3 and IMAP and set their startup type to Automatic.

I have made sure that both services are bound to the correct NIC(S) in the EAC.

I have performed a Test-PopConnectivity and a Test-ImapConnectivity cmdlet with the attached results.

I have also attached the results of a Get-PopSettings and Get-ImapSettings cmdlet.

I've experimented with the LoginType attribute on the PopSettings with no success.

I found this article about AcceptedDomains.  Mine have definitely been changed to match my configuration in Exchange 2010, with the root domain (domain.com) being the default.  This is also the domain of my Exchange server.
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26619610.html

The article mentions setting the domains back to the defaults.  How do I go about doing that?

From an Outlook client, I simply receive a "Log onto incoming mail server (POP3): Outlook cannot connect to your incoming e-mail server.  If you continue to receive this message, contact your server administrator or Internet service provider (ISP).

I enabled protocol logging for the pop3 service.  After multiple attempts and service restarts, my log looks like the one attached - not much information.
Test-PopConnectivity-Results.JPG
Test-ImapConnectivity-Results.JPG
Get-PopSettings-Results.JPG
Get-ImapSettings-Results.JPG
POP3BE20140826-1.LOG
LVL 1
marrjAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

marrjAuthor Commented:
I forgot to mention that the Windows firewall is turned off on my 2013 server.  I can successfully telnet into the server over TCP 110, but there is no banner; just a black screen.  As soon as I press any key, the session terminates.
0
gheistCommented:
You need to wait for POP3 banner before typing anything.
0
marrjAuthor Commented:
How long does that take?  I waited 10 minutes.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

marrjAuthor Commented:
At this point, when I telnet into port 110 from a client, from the server itself using the registered IP, or from the server itself using 127.0.0.1, the results are the same.  I'm presented with a blank screen with no banner.  I've tried changing the default ports for POP to something other than 110 and changing the proxy port to something other than 9955.  No luck.  The results are all the same.  HELP PLEASE!
0
gheistCommented:
restart pop3 service if still there is one?
0
marrjAuthor Commented:
I've restarted both the frontend and backend pop3 services too many times to count.  I've even restarted the information store and the entire server.  No luck.
0
marrjAuthor Commented:
I've also shut down the two POP3 services and looked at the Performance Monitor console to see if there was some other service listening on 110 or 9955.  There was not.  I'm going to say, at this point, my issue has something to do with the new Exchange 2013 topology.  I have both the frontend and backend roles installed on a single server, so my server will be proxying to itself on a lot of things.  This new concept has caused me grief before with other services such as receive connectors and throttling limitations.  Has anyone had experience with a colocated frontend/backend server in 2013 with the POP3 or IMAP protocols?
0
gheistCommented:
Does server itself permit user logins?
0
marrjAuthor Commented:
Can you elaborate a little on what you mean by the server permitting logins?  I have just over 1000 mailboxes that are currently active on the server.  Users connect daily using MAPI over HTTPS, OWA, and Activesync.  Everything works perfectly, except POP and IMAP.
0
gheistCommented:
Pop3 consists of 2 services - POP3 server and pop3 backend. Are both running?
0
marrjAuthor Commented:
Yes, both are running, have been set to automatic startup, and have been restarted countless times.  The frontend service is bound to TCP\110.  The backend, from what i can tell, is bound to TCP\9955.
0
marrjAuthor Commented:
Called Microsoft support...

I had two issues.

1. the components for the POP and IMAP services were in an "inactive" state.  After bringing them back to "Active", the service started responding with a banner.

2. The default self-signed cert would not work with the POP and IMAP authentications.  After generating a new cert and assigning it to those services, everything started working.
1

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
marrjAuthor Commented:
I had to call Microsoft to get it fixed.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.