Email polling 'stuck' on particular case
We have an issue where one case is 'stuck' in the email polling of FogBugz. When I mean stuck, I mean that every time FogBugz trys to connect to our exchange server, it keeps detecting an existing email as new. So every time it polls the email, it treats it as a new case. We now have over 400 cases of the same exact email/issue and we have been forced to stop our FogBugz service until a resolution is found.
This can happen if your POP3 server times out while Dispatcho is publishing the message to FogBugz. Then when Dispatcho finishes publishing the message to FogBugz it goes to delete the message from the POP3 server, but the server has timed out so it cannot be deleted. Then dispatcho reconnects and starts over again. I've only seen this once before. Timeouts on the web server side are already handled by Dispatcho.
Michael H. Pryor (fogcreek)
Fog Creek Home