A customer complained that POP3 was no longer working. After looking into this, it turned out that PopProxy was Inactive on the Exchange 2013 server. As to why it was inactive is unknown.
To start the PopProxy was challanging, generally you change ServerComponentState using the maintenance requester for most components. However running the following command did nothing:
Set-ServerComponentState -State Active -Requester Maintenance -Component PopProxy -Identity AB-EXCH-01
To start the PopProxy component, I needed to use the Exchange 2013 Health API as a requester.
Set-ServerComponentState -State Active -Requester HealthAPI -Component PopProxy -Identity AB-EXCH-01
To start the PopProxy was challanging, generally you change ServerComponentState using the maintenance requester for most components. However running the following command did nothing:
Set-ServerComponentState -State Active -Requester Maintenance -Component PopProxy -Identity AB-EXCH-01
To start the PopProxy component, I needed to use the Exchange 2013 Health API as a requester.
Set-ServerComponentState -State Active -Requester HealthAPI -Component PopProxy -Identity AB-EXCH-01
As shown below:
This is dummy text. It is not meant to be read. Accordingly, it is difficult to figure out when to end it. But then, this is dummy text. It is not meant to be read. Period.
ConversionConversion EmoticonEmoticon