Noel-
Thanks for the response. After reading your reply and
looking over my matcher code, I found the silly error
that was causing the odd behavior. By mistakenly
returning the sender's address, this code was in
effect routing the mail back to the sender.
// code with the bug:
public Collection match (Mail mail)
throws MessagingException
{
Collection matches = new ArrayList();
MailAddress address = mail.getSender();
String user = address.getUser();
if (isUserOutPendingEnabled(address))
{
matches.add(address);
}
return matches;
}
// correct code here:
public Collection match (Mail mail)
throws MessagingException
{
Collection matches = new ArrayList();
MailAddress address = mail.getSender();
String user = address.getUser();
if (isUserOutPendingEnabled(address))
{
matches.addAll (mail.getRecipients());
}
return matches;
}
It seems to be working now. Thanks for the pointer.
Carl
--- "Noel J. Bergman" <[EMAIL PROTECTED]> wrote:
> All mail, at least currently, enters through the
> "root" processor. Matchers
> do not effect messages, per se. Matchers effect
> recipient lists (matched,
> not matched), and that is what ends up having an
> effect on message routing.
> Without looking at your matcher, it would be hard to
> say what it does to the
> recipient list.
>
> --- Noel
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
