We are having a severe problem with James 3.0-M2 where it will operate correctly for hours or days, and then all of a sudden it will not process a lot of the mail it spools. Sometimes it will not process *any* mail that it spools, and other times it will spool a bunch of mail, and then process others seemingly at random. I have to restart James to get that spooled mail to be processed. But even then, sometimes the spooled mail is completely lost after a restart. I have seen several other threads lately with similar problems, but they haven't helped our situation.
We do not store mail in James for personal accounts and we have IMAP & POP3 disabled. Every inbound email has one of two things done to it: - it is processed locally by custom mailets & matchers - or it is relayed to our corporate Google Apps account A previous thread recommended checking all custom mailets and matchers. As far as I can tell, they are all working properly. There are no exceptions or errors in log/james-server.log, and in the scenario where James spools some mail & processes others, the mail that is processed is handled properly by our custom mailets & matchers. I've tried connecting to James JMX remotely via JConsole but have not been able to connect. Which port does James run JMX on? Any help with JMX would be appreciated. Does anyone have any other ideas about what we should look for? I noticed 3.0-beta3 is out now, were there fixes in beta3 related to mail being spooled but not processed? Thanks, Zach --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org