The new "on{Match|Mailet}Exception" support introduced in 2.2.0a5 was causing an
endless "config.xml" loop caused by JamesSpoolManager not setting state to Mail.ERROR
in case of an Exception not instance of MessagingException being thrown by a Mailet or
Matcher. In such situation the message was resent to the current processor instead of
going to Mail.ERROR.Vincenzo P.S. Noel, the part of the patch here for v3 is not cumulative with the patch I submitted yesterday (Monday) for v3 (see "RE: [PATCH]On matcher/mailet exception handler") but should be applied *after* it. I don't have yet my account and hence cannot commit, so I leave it to you.
onExceptionHandler_loop_v3.patch
Description: Binary data
onExceptionHandler_loop_v2.patch
Description: Binary data
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
