Ricardo Kleemann writes:
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 theTo 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.
But they deserve to be. You do not correct rude, antisocial behavior by ignoring it or working around it. You correct it by confronting, isolating the offenders, and making sure they feel the consequences of their anti-social behavior.
It is rude, selfish, and arrogant, to shift the costs of dealing with your spam load to everyone else, in this manner. It is the height of arrogance for someone to believe that they're too important or too busy to filter their own mail, instead forcing others to jump through hoops in order to get their mail delivered. Perhaps this might be reasonable if someone is Lord High Posterchild Of The Known Universe, but for ordinary joe-shmoes this is rude, selfish behavior.
Besides, if everyone kept sending these challenges, in response to every message, nobody would ever receive a single mail from anyone, their mail robots will just keep bouncing registration requests between each other, in perpetuity. The only way this works now is because only a tiny minority of people engage in this arrogant, obnoxious practice. This is a classical example of the Tragedy Of The Commons.
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.
I understand your concerns, but I believe that the usefulness of the ability for list subscribers to manually retrieve messages they've accidentally bounced, because of temporary software problems, or their ISP's downtime, overrides the need to accomodate a small number of ignoramuses. That, I'm afraid, is the tradeoff here. I have nothing but contempt for these snobs. Maybe once every three months I get such a "registration message" myself, so I just kick the jerks off this list, I think they'll be too stupid to contribute to any useful discussion here, anyway. No big loss.
In the last eight years this is the first time this came up, so this is not a common occurence. I do not know why your specific list attracted so many aforementioned boobs. Nobody else seems to had the same problem, in the last eight years, as far as I can tell. Furthermore, Qmail's ezmlm does the same thing, as I said, and it predates Courier by some years. And I've seen other mailing list managers that also number their list messages. This is standard, reasonable practice, and I see no reason to change it just because there are, perhaps, more dumb people on the Internet, now.
pgpzyEum9L6oX.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
