asked on

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.
https://www.experts-exchange.com/questions/26619610/Exchange-server-2010-Pop-Imap-Error.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

marrj

ASKER

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.

gheist

You need to wait for POP3 banner before typing anything.

marrj

ASKER

How long does that take? I waited 10 minutes.

marrj

ASKER

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!

gheist

restart pop3 service if still there is one?

marrj

ASKER

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.

marrj

ASKER

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?

gheist

Does server itself permit user logins?

marrj

ASKER

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.

gheist

Pop3 consists of 2 services - POP3 server and pop3 backend. Are both running?

marrj

ASKER

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.

ASKER CERTIFIED SOLUTION

marrj

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

marrj

ASKER

I had to call Microsoft to get it fixed.