> I can offer two suggestions in this situation: > > A) A suitable maildrop recipe > > B) Invest a few days in grepping the logs, compiling a list of the > culprits, > then unsubscribe each one and/or mail them a clue-by-four.
I don't understand, a maildrop recipe exactly for what? I believe the problem in this particular case is that the list recipients were probably expecting the envelope sender to be list-bounce rather than list-bounce-# but I don't see how maildrop could fix that... Thanks Ricardo ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
