>-----Original Message----- >From: Daniel Quinlan [mailto:[EMAIL PROTECTED] >Sent: Monday, July 04, 2005 5:18 PM >To: users@spamassassin.apache.org >Subject: Re: SpamAssassin 3.1.0-pre3 released! > > >Chris Santerre wrote on Mon, 4 Jul 2005 12:39:48 -0400 : > >>> Just a heads up to all, multi.uribl.com will not be included in this >>> release by default. You have to manually add it. The staff of >>> URIBL.com want it this way for now. > >"Kai Schaetzl" <[EMAIL PROTECTED]> writes: > >> You mean all the >> urirhssub URIBL_SC_SURBL multi.surbl.org. A 2 >> body URIBL_SC_SURBL eval:check_uridnsbl('URIBL_XX_SURBL') >> will get changed before final release? > >To clarify, Chris is not speaking for Apache SpamAssassin.
I never do. > He is advertising Advertising? Um...ouch! > the confusingly-named "URIBL.com" blacklist which is an >alternative to SURBL. URIBL.com has not requested that Apache >SpamAssassin use their (his?) blacklist Not mine. Its a group thing. I have the biggest mouth. > so Apache SpamAssassin has not >considered testing it or including it in a release. As always, we >recommend deploying our standard rule set. Yeah, because SARE and URIBL are so terrible. /sarcasim. >Chris, please be clearer in the future. Thanks. Which is again, my comment: "only those smart enough to manually config their SA reap the benefit" --Chris (Wondering who spit in DQ's frosted flakes.)
