Trap lists is a great idea. I was thinking of making a meta-db of
the user id's in all the lists. The database might keep the number
of lists subscribed to, time stamp of last sign-on, maybe a field
for weighting the other fields. The db would be checked as part of
a new user id process against a policy file. The policy file might
have things like a max number of lists per some time period. A zero
time period would make the max absolute. Has anybody done this?
Anybody think this would be useful? I'm volunteering some time as
Paul Haas wrote:
> On Tue, 12 Oct 1999, Steve Bergeon wrote:
> > Ok, right you are. What I meant was that I'm asking when to ask.
> Any time you subscribe to a list as other than a normal participant.
> If you try to subscribe to the alumni list for a nonexistent school, then
> I know, unambiguously, that you are not a normal participant.
> The trap lists exist to detect email bombings, spammers, sociologists,
> slimeballs, etc...
> You can't use random lists, start with lists where you know some of the
> ground rules.
> email@example.com http://www.hamjudo.com
> The April 97 WebSight magazine describes me as "(presumably) normal".