[JAMES-3197] MailetProcessor should handle NoClassDefFoundError

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.5.0, 3.6.0
• Component/s: Mailet Contributions
• Labels: bug
• Assignee: Unassigned
• Reporter: Benoit Tellier
• Created: 29/May/20 05:15
• Updated: 02/Jun/20 08:47
• Resolved: 02/Jun/20 08:47

Description

Due to JAMES-3176, we ended up having ExtractMDNOriginalJMAPMessageId throwing NoClassDefFoundError.

This error is not handled by the mailet processor, resulting in a mailqueue nack, and generated an infinite loop on top of RabbitMQ.

This error can happen too when a user specifies a custom mailet with unsatisfied dependencies.

Thus, when a mailet, or a matcher throws a `NoClassDefFoundError` we should execute mailet error handling normally, and prevent that infinite loop.