chibenwa opened a new pull request, #1128:
URL: https://github.com/apache/james-project/pull/1128
…ssor
Today, if I specify a mailet pointing to a processor that do not exist,
James will start, and the failure will be managed at runtime: upon processing,
each mail needed to be processed by the unspecified processor will instead go
to the error processor.
Recovering data from such a failure is quite a journey in itself.
Example of such configuration:
```
<mailet matcher="All" class="ToProcessor">
<processor>notFound</processor>
</mailet>
```
Instead of handling such failures at runtime, we could instead abort James
startup.
Given we add a new method on the mailet interface, for a mailet to give the
list of processor it needs, we can trivially implement such a check in the
mailet container.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
