You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by William Stearns <ws...@pobox.com> on 2004/04/20 04:13:31 UTC

blacklist_from preferred format

Good afternoon, all,
	(This is probably the most embarrasing post I've had to make, 
especially after a _year_ of publishing a blacklist.  I'm sorry I haven't 
gotten to this sooner.)

	I've been putting out the sa-blacklist.current.cf with the same 
domain in multiple forms; it's time to stop that.
	The current sa-blacklist.current.cf list has, for example:

blacklist_from *@www.spamplace.com
blacklist_from *@*.spamplace.com
blacklist_from *@spamplace.com

	Is there any reason I shouldn't have _only_

blacklist_from *@*.spamplace.com

	?  The www, obviously, can go as it's rarely used for sender 
domain (and I have the .uri.cf list and surbl.org for embedded 
hyperlinks).  Is there any reason to keep the 

blacklist_from *@spamplace.com

	?
	Unless I hear complaints, the conversion tools will create 
an sa-blacklist.current.cf with just 

blacklist_from *@*.spamplace.com

	lines for each domain.
	Cheers,
	- Bill

---------------------------------------------------------------------------
        "What is the most effective Windows NT remote management tool? 
A car."
        -- Network Intrusion Detection, An Analyst's Handbook
           2nd Edition, 2000
           Stephen Northcutt et al, page 147
(Courtesy of Rodrigo Goya <lu...@securenet.com.mx>)
--------------------------------------------------------------------------
William Stearns (wstearns@pobox.com).  Mason, Buildkernel, freedups, p0f,
rsync-backup, ssh-keyinstall, dns-check, more at:   http://www.stearns.org
--------------------------------------------------------------------------

Re: blacklist_from preferred format

Posted by Steven Dickenson <st...@mrchuckles.net>.
Simon Byrnand wrote:
> I think you'll find that both those cases are covered by *spamplace.com  
> ? (Which is a valid wildcard use in blacklist_from as far as I'm aware)

Yes, but it will also cover notaspamplace.com, which is undesirable.

Steven
-- 
Steven Dickenson <st...@mrchuckles.net>
http://www.mrchuckles.net

Re: blacklist_from preferred format

Posted by Kai Schaetzl <ma...@conactive.com>.
Simon Byrnand wrote on Tue, 20 Apr 2004 15:54:49 +1200:

> Looks like you do have to do *@*.spamplace.com and *@spamplace.com after all...
>

Maybe a change to how SA handles this would be helpful?

blacklist_from domain.com

would block any mail from that domain or a subdomain of it.

If that makes the parsing overly complicated introduce a new one:

blacklist_domain domain.com


Kai

-- 

Kai Sch�tzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
IE-Center: http://ie5.de & http://msie.winware.org




Re: blacklist_from preferred format

Posted by Simon Byrnand <si...@igrin.co.nz>.
At 15:44 20/04/2004, William Stearns wrote:

>Good evening, Simon,
>
>On Tue, 20 Apr 2004, Simon Byrnand wrote:
>
> > At 15:27 20/04/2004, William Stearns wrote:
> >
> > >On Mon, 19 Apr 2004, William Stearns wrote:
> > >
> > > >       I've been putting out the sa-blacklist.current.cf with the same
> > > > domain in multiple forms; it's time to stop that.
> > >
> > >         A little more thought about the problem reminded me that
> > >blacklist_from doesn't use regexes, it uses wildcards.  Both:
> > >
> > >blacklist_from *@*.spamplace.com
> > >
> > >         and
> > >
> > >blacklist_from *@spamplace.com
> >
> > I think you'll find that both those cases are covered by *spamplace.com  ?
> > (Which is a valid wildcard use in blacklist_from as far as I'm aware)
>
>         Too true.
>         I'm a little concerned about a short spammer domain, though.
>Lets say my list someday got "link.com" as a spammer.  Because my two
>lines require a preceding "@" or ".", I don't believe they'd trigger on
>mails from "larry@earthlink.com", and I fear yours would.
>         Is there a way to reduce it to one rule per domain that doesn't
>risk that FP?

Hmm, you've got me there. Didn't even consider that possibility :(

Looks like you do have to do *@*.spamplace.com and *@spamplace.com after all...

Regards,
Simon


Re: blacklist_from preferred format

Posted by William Stearns <ws...@pobox.com>.
Good evening, Simon,

On Tue, 20 Apr 2004, Simon Byrnand wrote:

> At 15:27 20/04/2004, William Stearns wrote:
> 
> >On Mon, 19 Apr 2004, William Stearns wrote:
> >
> > >       I've been putting out the sa-blacklist.current.cf with the same
> > > domain in multiple forms; it's time to stop that.
> >
> >         A little more thought about the problem reminded me that
> >blacklist_from doesn't use regexes, it uses wildcards.  Both:
> >
> >blacklist_from *@*.spamplace.com
> >
> >         and
> >
> >blacklist_from *@spamplace.com
> 
> I think you'll find that both those cases are covered by *spamplace.com  ? 
> (Which is a valid wildcard use in blacklist_from as far as I'm aware)

	Too true.
	I'm a little concerned about a short spammer domain, though.  
Lets say my list someday got "link.com" as a spammer.  Because my two
lines require a preceding "@" or ".", I don't believe they'd trigger on
mails from "larry@earthlink.com", and I fear yours would.
	Is there a way to reduce it to one rule per domain that doesn't 
risk that FP?

> (PS thanks for the effort in maintaining your sa-list, I'm using it via 
> ws.surbl.org and SpamCopURI and it provides a useful extra amount of 
> scoring to help catch those marginal ones...)

	On behalf of the contributors, you're welcome.  *sincere smile*
	Cheers,
	- Bill

---------------------------------------------------------------------------
	How's my programming?  Call 1-800-DEV-NULL
(Courtesy of http://www.tux.org/~ricdude/)
--------------------------------------------------------------------------
William Stearns (wstearns@pobox.com).  Mason, Buildkernel, freedups, p0f,
rsync-backup, ssh-keyinstall, dns-check, more at:   http://www.stearns.org
--------------------------------------------------------------------------

Re: blacklist_from preferred format

Posted by Simon Byrnand <si...@igrin.co.nz>.
At 15:27 20/04/2004, William Stearns wrote:

>Good evening, all,
>
>On Mon, 19 Apr 2004, William Stearns wrote:
>
> >       I've been putting out the sa-blacklist.current.cf with the same
> > domain in multiple forms; it's time to stop that.
>
>         A little more thought about the problem reminded me that
>blacklist_from doesn't use regexes, it uses wildcards.  Both:
>
>blacklist_from *@*.spamplace.com
>
>         and
>
>blacklist_from *@spamplace.com

I think you'll find that both those cases are covered by *spamplace.com  ? 
(Which is a valid wildcard use in blacklist_from as far as I'm aware)

Regards,
Simon

(PS thanks for the effort in maintaining your sa-list, I'm using it via 
ws.surbl.org and SpamCopURI and it provides a useful extra amount of 
scoring to help catch those marginal ones...)


Re: blacklist_from preferred format

Posted by William Stearns <ws...@pobox.com>.
Good evening, all,

On Mon, 19 Apr 2004, William Stearns wrote:

> 	I've been putting out the sa-blacklist.current.cf with the same 
> domain in multiple forms; it's time to stop that.

	A little more thought about the problem reminded me that 
blacklist_from doesn't use regexes, it uses wildcards.  Both:

blacklist_from *@*.spamplace.com

	and

blacklist_from *@spamplace.com

	are needed, as the first one will miss larry@spamplace.com.
	Both forms now used.  Still saves 638 rules.
	Cheers,
	- Bill

---------------------------------------------------------------------------
	"Be vewy vewy quiet...I'm hunting Jedi."
	-- Darth Fudd
(Courtesy of Peter da Silva <pe...@baileynm.com>)
--------------------------------------------------------------------------
William Stearns (wstearns@pobox.com).  Mason, Buildkernel, freedups, p0f,
rsync-backup, ssh-keyinstall, dns-check, more at:   http://www.stearns.org
--------------------------------------------------------------------------