if you're mail matched either but not both then the two different matchers would invoke the same mailet.
It sort of depends on what's going on, what your goals are, etc. The matching emails could be dropped out of the current processor or not depending on how you configure it (for ex if the mailet just adds a footer to the mail, then you wouldn't want to drop out of the current process but if it were matching a black list item you'd probably want to send it to a different processor). In the footer example , you'd want to make sure that you didn't put two footers (in the case where some emails match both matchers) in so you'd make sure that the emails dropped out of the processor A by redirecting them to a separate processor B leaving the second mailet to catch the remaining ones and redirect those also to processor B. Now you may need to rejoin the processor A stream. That's also simple. Break processor A at the point where B emails are to rejoin and have all A's and all B's go to a third processor AA. Simple processor handling is easy to think about. If you get really complicated you can use some task flow tool like Microsoft Project. That's all that's happening here. bp --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
