Pegasus Mail & Mercury

When gmail attempts to send a message to my Mercury mail server (v 4.72) the connection proceeds normally until STARTTLS when everything goes south.  The session log looks like this: 02:19:37.640: >> STARTTLS<cr><lf>02:19:37.640: << 220 OK, begin SSL/TLS negotiation now.<cr><lf>02:19:37.781: 22: Error -32 ...

We recently upgraded to Mercury 4.72 and Windows 2008 R2 on 32 bit architecture. Occasionally , under high volumes our Mercury mail Queue is failing to process correctly. The Mercury service seems to be CPU bound, consuming 12%CPU on a Quad CPU for hours. No email is delivered. A restart of  the service un-hangs it and the queue is quickly ...

Peter Strömblad:I'm having a hard time following your question. Is it IMAP that doesn't work? If so, try enabling session logging in MercuryI, and see what goes wrong from one of your client computers. If you see no activity at all, I'd say you have a firewall problem with your 2008 server, not allowing connections over TCP port 143 to Mercury, ...