Thanks for the wiki info. I read over it. It doesn't completely explain what the default [onMailetException="error"] does. But I can assume that the philosophy of "error" is to just re-queue the message and start over. Is that correct? At least that is what it appears to be doing for me now. If so, I assume that if I say "ignore", the email message will simply terminate and NOT be re-queued, which is what I want. Have I got it correct?
I don't have any stack traces. In the mailet log, it is happily processing through the mail list, then there is an exception saying it can't get connection to mySQL. Then the maillist starts over just like it was a brand new note. It starts sending to the list again and the same exception occurs, etc. etc. until I delete the message from the spool. The connection problem with mySQL is an issue. But the biggest concern is to tame this infinite loop that results from it or any other possible error. Once that's done, I'll figure out the mySQL connection problem. Thanks. Jerry -----Original Message----- From: Stefano Bagnara [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 21, 2006 4:33 AM To: James Users List Subject: Re: Mail List Mailet Infinite Loop on db failure JWM wrote: > What do I need to do either in the mailet code or in the configuration file > to ensure any failure (with the db or anything else) on this mailet forces a > complete termination of this mail message and guaranteed no restart? Have you any stacktrace of the problem? Depending on the problem this could help: http://wiki.apache.org/james/HandlingExceptions Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
