That may explain my problem. I wrote a matcher called "RecipientIsLike" which matches any recipient like "list" and sends it to my custom listserv. The listserv then looks at the original recipient and queries the database for the list of users. Which means that I only have one mailet that will match the "list" so that I don't have to modify the config.xml file everytime my users add a list to the database. Technically both recipients in the example "[EMAIL PROTECTED], [EMAIL PROTECTED]" should match. Then the listserv only processes the first in the list so it never sees the second listserv address. In your example it would work because you have separate and distinct mailet/matches for each list.
So my backup plan of looping through all recipients in my listserv mailet is actually a good solution since it will process all matches, and any non-matches will continue on through the processor pipe. Right? I was worried about losing the non-matches but it sounds like that won't be a problem.
In any case, it doesn't sound like there are any bugs here, just a misunderstanding of how things work.
-J
Noel J. Bergman wrote:
Wait a minute ... Jay, I was wrong ... distracted making dinner ... hold on.
The matcher does it. The way a matcher works is that it selects the recipients that will be processed by the mailet. Matchers like HostIs are just all or nothing, but otherwise, the matcher says which subset of recipients will be processed.
So if I have multiple recipients, and use RecipientIs, then only that recipient should be passed along to the mailet for processing.
So if I have e-mail sent to "[EMAIL PROTECTED], [EMAIL PROTECTED]", what should happen is that the RecipientIs matchers should peel off a single recipient for the listserv mailet. The recipient set will get split into two sets: matching and notMatching. As long as neither one is empty, it continues. So the matching set, containing just the current list, should be processed by the listserv. The message is then ghosted. But the other set still continues with its duplicate of the message.
So now that I've had my dinner, if you are not seeing the above behavior, then we need to find out why.
Ignore my earlier message.
--- Noel
--------------------------------------------------------------------- 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]
