Potential issue with NewMessage about s22.imap HOT 2 CLOSED

No there's no timeout. Some servers require clients to issue NOOP commands every once in a while as an indicator that the connection is still alive. If a client fails to do this, the server may close the connection. It almost sounds as if this is what happens.

If you want to do some digging, the NOOP code is in the "IssueNoop" method. You could put a trace or debug print in there to check if it's being called at all.

from s22.imap.

Ok, it appears to be working now. My windows service has been running for about an hour now and still receiving new messages. Here's what I changed.

1. Downloaded the source code from the Master branch
2. Compiled the code and used that as my reference
3. In my NewMessage event handler, I check for "if (e.MessageCount > 0)" before processing the message. It appears the NewMessage event is sometimes raised when MessageCount = 0. Possibly when the NOOP is executed?

I didn't spend the time digging in to this more. Right now it works and that's all I care about. So either a bug fix in the Master branch fixed it...or my MessageCount check.

Thanks for the quick reply...and great IMAP Library.

Many Thanks!

Bob

from s22.imap.