Re: OSS community interaction (was: Re: *** bluber *** Re: Male xxxxxx enhancement formula^)
On Fri, Jun 03, 2005 at 11:43:29AM -0600, s. keeling wrote:
> Incoming from Ian Greenhoe:
> > On Mon, 2005-05-30 at 16:35 +1200, Chris Bannister wrote:
> > <snip>
> > > A C/R system on a mailing list? Please don't even consider it.
>
> Use of C/R is an excellent way to add yourself to my killfile.
>
> > Other suggestions are welcome. Please contribute some. If you have
I didn't say that.
> i) - Easily recognizable crap (dorks, p_n_s): report/delete immediately.
>
> - Anything from APNIC/Easynet is a complete waste of time
> (unresponsive ISPs == spammer's accounts are never in any
> jeopardy).
>
> - Posts to mailing lists from APNIC/Easynet are allowed.
>
> ii) Grab/file whitelisted senders (protect from SA).
>
> iii) Sift the rest through SA, and unreadable (foreign charsets).
> Either it's recognizably spam, or it falls through to
> ${DEFAULT}.
>
> ------------------------------------------------
> APNIC = "(58|59|60|61|124|125|126|202|203|210|211|218|219|220|221|222)"
> ALL256 = "[0-9][0-9]?[0-9]?"
> EASYNET = "195\\.40"
> LISTS = "(backports|debian|chkrootkit)"
>
> :0
> * $ ! (^TO|^From.*)${LISTS}
> * $ ^Received:.*(\\<${APNIC}\\.${ALL256}\\.${ALL256}\\.${ALL256}\\>|\\<${EASYNET}\\.${ALL256}\\.${ALL256}\\>)
> {
> LOG="(ap|kr|jp|en)nic IP - "
> :0
> /dev/null
> }
> ------------------------------------------------
>
> > BTW, As you are a subscriber, a) you've already gone through a c/r in
or that, in fact I agree with you.
> That is to protect us from others subscribing us without our
> knowledge. That's not C/R. That's verification of a subscription
> request. Comparing 1000 spam generated C/R's to one or two list
> subscriptions per month is ludicrous.
Reply to: