In message <[EMAIL PROTECTED]> (on 1 March 2003 11:29:20
-0500), [EMAIL PROTECTED] (Tom Betz) wrote:
>If EFF wishes to see EFFector being delivered effectively, EFF must
>be considered a responsible mailing list manager. If EFF wishes to
>be considered responsible, EFF must act responsibly. This requires
>that EFF take at LEAST these two steps, and the sooner the better:
>
>1) Require that all future subscriptions to the EFFector mailing list
>be confirmed using some unforgeable token in a response (preferably
>by e-mail, but acceptably via a web link) from the prospective
>subscriber. and
I entirely agree. (I am speaking on this as someone who notified EFF that
their main outgoing mailserver had been placed on
inputs.relays.osirusoft.com, and did my best to get it removed (after being
properly fixed, of course) ASAP, given the timing in question - it was when
the so-called "anti-terrorist" USA "PATRIOT" Act was coming up for a vote.)
>2) Clean your existing mailing list by requiring all present
>"subscribers" -- I place that word in quotes because I have no
>confidence regarding how many of the addresses on your list actually
>belong to willing recipients -- to confirm (by means similar to those
>you will employ for new subscriptions) that they do indeed wish to
>receive EFFector. To allow for temporary undeliverables (something
>you should NOT do for initial subscriptions), you can even give them
>two or three opportunities to respond before you cut them off. This
>step will at once remove undeliverables from your mailing list and
>(more importantly) remove all unwilling recipients, protecting the
>EFFector mailing list from being reported to Razor (and other anti-
>spam tools) as spam.
There is, of course, the potential problem with this that, if EFFector is
going into spamtraps now, due to sabotage by others (enabled by a lack of
adequate confirmation protection) and carelessness on the part of people
failing to unsubscribe prior to leaving their accounts (and sysadmins
turning such accounts into spamtraps without checking on whether they were
thus unsubscribed - likewise careless, indeed irresponsible), these
confirmations are themselves likely to get picked up by Razor et al,
resulting in them getting blocked (despite the unique tokens given fuzzy
hashing). I'm not quite sure what can be done about this.
-Allen
--
Allen Smith http://cesario.rutgers.edu/easmith/
February 1, 2003 Space Shuttle Columbia
Ad Astra Per Aspera To The Stars Through Asperity
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Razor-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/razor-users
