Ricardo Kleemann writes:
Well it's not that simple. Even though the list has is sent with the list address' envelope sender, somehow the antispam registration request gets sent to the original sender, I'm guessing probably the registration bot is checking the envelope sender, but then sending the actual request to theFrom address. Like I said before, this very large list is a newsletter type,which really only the list owner sends a daily message. Most of the registration requests are from one particular domain, and although of course not all of the users in that domain have this feature turned on, it is a significant number, probably a couple thousand from the 20+ thousand.So the list owner gets flooded with these requests, and can't handle them. Just to add a little more complication to the mix... the list owner is a blind man who uses a special computer setup that allows him to communicate very well on the computer, he's done this for years, and amazingly enough handles thousands of messages per day. I was just trying to be helpful to prevent him from having to handle even more since he's getting flooded with these registration requests that had already been taken care of a couple of years ago.
I can offer two suggestions in this situation: A) A suitable maildrop recipeB) 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.
pgpb4wFA5JIau.pgp
Description: PGP signature
------------------------------------------------------------------------- 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
