On Thu, 15 Aug 1996, Paul Haas wrote:
> > Hey, if I'm writing it you know it will be configurable. I wouldn't dream
> > of forcing a policy like this on anyone, especially since I don't really
> > see the utility of it given confirmed subscriptions. Still, it might have
> > some utility for some list owners, so I'll look at coding it.
>
> When people do malicious multiple subscribes to my sites, they subscribe to
> the test mailing lists, as well as the production lists. A cron job that
> unsubscribes addresses from all lists if they were subscribed to the test
> lists would undo much of the damage from the multiple subscribes.
I have a utility program that I've created that will unsubscribe an
address from a group of lists. You just define the lists in a text file,
one list-name per line. It will also remove people from individual lists,
subscribe them. Another program I've created will request a copy of the
subscription list to the same group of lists (defined in the text file).
This is useful for being run with cron (I have included special
programming just to make it be "cron-aware") once a night. It also detects
a previous backup (for yesterday) and erases it if today's backup is
bigger or keeps it if today's is smaller (possibly indicating some
problem). Since my ISP is currently experiencing problems and the
mailserver got messed up, I've included even more programming for error
handling (not requesting TWO sets of backups at once).
It's fairly nice and if there's interest, I'll prep it for a release. I'm
always upgrading it, just because I have a big interest in it for my own
work.
Oh, it's also meant to be run in conjunction with a mail filtering
program. (I use procmail, but I guess any one would do the job)
-------------------------------------------------------------------------
| Brock Rozen | brozen@netvoyage.net | http://www.netvoyage.net/~brozen |
-------------------------------------------------------------------------
References:
|
|
