Hi,
Have a look to the configuration file conf/mailetcontainer.xml
To understand the order of execution of mailet, follow these simple rules :
- Starting point : The root processor.
- Order of execution : Sequential. The first mailet you see is applied,
the the second and then the third....
- Condition of execution of a mailet : the matcher clause of your
mailet. If this condition is not satisfied, then this mailet is skipt.
- When to stop : No more mailet to execute ( ie : end of a processor )
or the state of the mail is changed to GHOST ( which can be done by
mailets : eg LocalDelivery
- Conditionnal jump : you have the ToProcessor mailet that moves the
orocessed e-mail on top of a new processor of your choice. Combined with
a matcher, you get a conditionnal jump.
So you just have to insert this where needed :
<processor state="someProcessor" enableJmx=true>
...
<mailet matcher="SenderIs" class="ToProcessor">
<processor>managed-known-sender</processor>
</mailet>
</processor>
...
<!-- Add this new processor -->
<processor state="managedd-known-sender" enableJmx=true>
<mailet matcher="SenderHostIs" class="..."/>
</processor>
Le 18/03/2015 18:40, Hassan Latif a écrit :
> Hello,
>
> I'm struggling to find some text on this. Is there any specific order of
> execution for the matcher/mailet clauses that are declared in
> mailetcontainer.conf. Let's say we want to first check whether the Sender
> is known (e.g. by using SenderIs matcher) and then check whether the sender
> is from a specific host (using SenderHostIs matcher), is there a way to
> enforce this order of execution?
>
> Appreciate your help.
>
> -Hassan
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
