No, the matcher identify what to pass to the mailet itself.
To "block" the mail from being processed by the following you have to
use a consuming mailet (a mailet that sets the message state to GHOST).
Most mailets sets the state to GHOST unless you specify a
<passThrough>true</passThrough> attribute in the configuration.
Stefano
Santosh wrote:
I'm little confused about the working of a matcher. It's a simple doubt
though.
Consider a mail with:
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED] , [EMAIL PROTECTED], [EMAIL PROTECTED]
In the transport processor:
<mailet match="RecipientIsLocal " class="EchoMailet" /> --- call it 1
<mailet match="HostIsLocal" class=" EchoMailet " /> -- call it 2
Current HostName: adomain.com
localUsers: a & b (but not c)
EchoMailet simply prints the recipient addresses in the Mail object it
receives in the service(Mail mail) method. It extends GenericMailet.
According to my observations,
after 1: EchoMailet prints
[EMAIL PROTECTED]
[EMAIL PROTECTED]
after 2: EchoMailet prints
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Shouldn't the matcher RecipientIsLocal filter out [EMAIL PROTECTED] &
[EMAIL PROTECTED] such that at/after 2 only [EMAIL PROTECTED] Isn't this the
_expected_ behavior of any matcher?
Santosh.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
