Symptom 1Users who have a mailbox on Microsoft Exchange Server 2013 or Microsoft Exchange Server 2016 may find that their connections to POP3 or IMAP4 stop working. Additionally, they may receive the following error message:
The connection is being closed. Unable to read data from the transport connection: An
existing connection was forcibly closed by the remote host.Server response while making
connection:. ---> System.IO.IOException: Unable to read data from the transport
connection: An existing connection was forcibly closed by the remote host. --->
System.Net.Sockets.SocketException: An existing connection was forcibly closed by the
remote hostThe related service are started, no error/warning events in system or
Symptom 2Users can telnet to a POP3 or IMAP port by using the server FQDN. However, they don’t see the banner. Instead, they see only a blank screen.
You can use following command to check on the status of components:
- Use the following command to determine which requester made PopProxy inactive:Get-ServerComponentState -Identity <ServerName> -Component PopProxy).LocalStates
In the following example, HealthAPI is displayed as the requester that changed the state of PopProxy to Inactive.
- Use the following command to make PopProxy active:Set-ServerComponentState -Identity <ServerName> -component PopProxy -state Active -requester HealthAPI
Article ID: 3025138 - Last Review: Dec 16, 2015 - Revision: 1