Check that you aren't getting large attachments in the incoming emails. Shouldn't be anything over 5MB. you can regulate either in FP or at the Mail Server. I would do it at the mailserver if possible
I've verified the issue isn't attachements. I was just doing some testing and found that Footprints kills/bounces the connection for some reason. I need to remove the email inbox, save, rebuild and then save again and it picks up. Normally I don't need to do this, email will start picking up from 1-5 hours after that.
Are you using Office 365?
Microsoft Office 365 does have sending/receiving limits as detailed in this Technet article....
Specifically of interest is the limits section.
No, we are using on premises Exchange servers. We would look in the future to to 365 but not for our monitored inboxes.
I've run capturing logs and I don't see errors yet, it will just give up for minutes or hours at a time. Now that I have a work around I can keep us functional, but the processing is killed for all inboxes (we have three at the moment). I only needed to remove and re-add one inbox last time and it picked back up for all.
Where did you see that Footprints was bouncing / killing the connection - was that in your Exchange logs?
No, I didn't take a look at the Exchange logs side. It appears to be around some odd paging parameters in the Tomcat logs, normally when FP reaches out to obtain mailbox settings I see this:
*.business.emailrequest.IncomingEmailLoggingHelper.debug()|*.business.emailrequest.DefaultIncomingEmailAdministration.getIncomingEmailServers()||Retrieving Incoming Email Servers. Paging parameters start=-1, limit=-1|
But when the issue appears I also see:
*.business.emailrequest.IncomingEmailLoggingHelper.debug()|*.business.emailrequest.DefaultIncomingEmailAdministration.getIncomingEmailServers()||Retrieving Incoming Email Servers. Paging parameters start=0, limit=8|
Either once I clear out the connections and rebuild, or if FP decides to start picking up I no longer see that odd 2nd parameter in the logs.