> I'm not willing to control at the <processor name=...> config.xml
> entry level, but at the <mailet match=...> level. I'll write an
> example. I would like to be able to write:
> <mailet match="AttachmentFileNameIs=..." class="Bounce">
> <inline>heads</inline>
> <attachment>none</attachment>
> <passThrough>false</passThrough>
> <prefix>[REJECTED]</prefix>
> <message>...</message>
> <onMatchException>nomatch</onMatchException>
> </mailet>
I don't believe that I like that use of XML. The body of the mailet tag is
for the mailet, not the matcher or the processor. As you noted, this would
be "done with a few lines of code in LinearProcessor." There is also a
proposed change to the DTD for James v3, which impacts this area.
An alternative would be:
<mailet match="..." class="..." [match|mailet]Exception="...">
making it an attribute of the mailet tag, instead of a child element.
> if I had this possibility, I would like to have all matchers and
> mailets catching and handling only the exceptions that they can
> locally manage, and throw up (or not catch) things that they
> cannot deal with.
I agree.
Still unresolved is what to do about per-recipient exceptions, instead of
per-message exceptions. But I believe that we can extend that handling
later by throwing a specific exception conveying the information, either by
chaining or collection.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
