>> 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 > > To catch the goober address confirmation requests coming back from those > twits, and filtering them away.
Oh I see... but my intention is not to filter them out. I was trying to be of help to my friend that still wants to send the message to all of those addresses, and had spent a lot of time in the past going through the confirmations. I was trying to ensure that he wouldn't get those confirmation requests just because I switched to another list processor... and that the recipients would still get their messages. But the only way for that to happen I guess would be for the list messages to be sent with the list-bounce sender address. ------------------------------------------------------------------------- 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
