OK, I'll add it.

For future reference what is the mechanism in James that would split the two if the first wasn't a "list-" match? I noticed that if I send to "[EMAIL PROTECTED],[EMAIL PROTECTED]" something causes the second email address for the listserv to be put back through the processors so that it works as expected. It seems like if I could put the listserv mailet at a different point in the processor piping the two addresses would be split into independent messages before it ever got to the mailet and matcher.

In the meantime I'll probably modify my listserv mailet to loop through all the recipients and send to them rather than just the first in the list.

Thanks.

-J

Noel J. Bergman wrote:

if somebody sent to "[EMAIL PROTECTED],
[EMAIL PROTECTED]" wouldn't the first
matcher catch the email and then ghost it when done so the
second match on "list-yyyyyy" would never happen?



Please put that in bugzilla. There isn't a quick fix because the mailet doesn't know the address that caused it to be invoked.

JDBCListserv supports a <list_address> element, which tells it the address
it supports.  That should probably be added to AvalonListserv.

Mark's new list serve has the same bug.

--- Noel


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




Reply via email to