I have an Exchange 2003 server. All services were working find. Now the IMAP4 Services does not allow connections. Nothing changed since Friday. The service was started and working fine as of last Friday. However, Monday it started refusing connections. (I have a few users using IMAP4 clients). I tried to telnet port 143 and the server port refused the connection. There are no error messages in the application or services event logs pertaining to this problem. I tried restarting the service (startup type is set to automatic), then it hung up. In other words, when trying to restart IMAP4 service, it indicates that it is "Starting" but it then brings up a timeout message. The system has all the latest service patches and updates, I might add. I rebooted the system this morning, the IMAP4 service started but still refused connections. When restarting the service, the same thing happened as described above. When I try a "net start IMAPSvc" on a command line it tells me that service is started, but it still does not connect. I might add that it will not allow me to do a stop of this service on the command line. None of my research thus far has produced any results as to the cause of this issue. I suspect a corrupt file, but not sure. Is there any insight on what might be causing this problem?