Thanks Stefano.
However, the documentation hasn't got anything about
CommandListservProcessor, which is the one I'm interested in.
There is another thing. I am using James 2.2.0 and from the documentation it
looks like the CommandListserv stuff was introduced with James 2.3.0. So is
it the documentation wrong, or did I somehow added some 2.3 functionality to
2.3?
----- Original Message -----
From: "Stefano Bagnara" <[EMAIL PROTECTED]>
To: "James Users List" <[email protected]>
Sent: Sunday, October 29, 2006 11:26 AM
Subject: Re: Mailet order
It is a pipeline.
If the matcher matches the corresponding mailet is executed.
The flow depends on what the Mailet does: the mailet could consume the
mail (set state to GHOST), or it could move the mail to another processor
(set state to the processor name), or it could let the mail to pass
through (leave the state as is).
So in case of no-match, or the mailet do not consume/move the mail the
following matcher is tested.
Some mailet have a <passThrough> option to decide wether the mail should
be consumed or not, others have hardcoded behaviour that should be clear
reading the docs:
http://james.apache.org/server/2.3.0/provided_mailets.html
Stefano
Giulio Troccoli wrote:
Hi everybody,
Is there an order how the mailet are "executed"? Does James process the
email for the first mailet that "matches" or for all the mailets that
"matches"?
Here is an example.
<mailet match="[EMAIL PROTECTED]"
class="CommandListservProcessor">
...
<mailet match="[EMAIL PROTECTED]"
class="CommandListservProcessor">
...
If webmaster sends an email to testML, will the first and only the first
mailet be processed? Or will both be?
Thanks
Giulio
---------------------------------------------------------------------
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]
