Logic requires asking these questions, so please bear with me. You say it fails after 30 minutes... How much volume is the email server seeing? Are you getting a huge spike in traffic, or is it just a connection timeout?
When you look at the messages you received, are any of them weird? I mean, is it a message from the same sender or containing an attachment that suddenly causes the failure? The exception you listed looks similar to a casting exception. My guess - without digging into the code - is that there is a message waiting to be processed that has a bad format on the queue. If you can remove that badly formatted message, things might free up. I have run into similar issues with custom mailets my project uses. I didn’t write them, merely adapt them from James 2.3.2 to 3.3.0. Try checking your timeouts, purging the top message from the queue, and tightening up your mail relaying. Sent from my iPad > On Feb 1, 2020, at 1:19 AM, Jerry Malcolm <techst...@malcolms.com> wrote: > --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
