Spamd variation

Hi,
   From the man page it appears that spamd relies on 
static information about spam originators.
Why not a more dynamic scheme ?.

Why not run the content of the mail through a spam
detector (like dspam), find the spam score and make
decisions based on that. I know that spam detection
is no where near perfect but it can be used for
assigning a 'badness score' to a site(originator of
email). So a site keeps getting this score and the
average (per msg) exceeds a we black list the site for
fixed duration. Similarly for white listing.

'Badness score' and also be assigned for other things,
like trying to send to non-existant user (a typical
spammer probe), absence of mx entry etc.


A milter(sendmail/postfix) can be implemented for
this.
Thus decisions will be more dynamic and 'configuration
free'.

Does this sound reasonable ?

regards
Praveen


     
____________________________________________________________
_______________________
You snooze, you lose. Get messages ASAP with AutoCheck
in the all-new Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/newma
il_html.html

* Praveen <madtantricyahoo.com> [2007-06-12
05:14]:
> Hi,
>    From the man page it appears that spamd relies on 
> static information about spam originators.
> Why not a more dynamic scheme ?.

	No, it doesn't. please read the man page instead of
trolling.

> 
> Why not run the content of the mail through a spam
> detector (like dspam), find the spam score and make
> decisions based on that. I know that spam detection
> is no where near perfect but it can be used for
> assigning a 'badness score' to a site(originator of
> email). So a site keeps getting this score and the
> average (per msg) exceeds a we black list the site for
> fixed duration. Similarly for white listing.
> 

	No. spamd does not do content filtering.

> 'Badness score' and also be assigned for other things,
> like trying to send to non-existant user (a typical
> spammer probe), absence of mx entry etc.
> 
> A milter(sendmail/postfix) can be implemented for
> this.
> Thus decisions will be more dynamic and 'configuration
> free'.

	As it is, spamd in greylisting mode (the default)
is very configuration free. but it sounds like you
actually don't run it, and are just trolling. 

	-Bob

On 6/12/07, Soner Tari <listkulustur.org> wrote:
> Probably a simple shell script could do the job, which
would look at
> SpamAssassin logs to find out the spam score and IP
address, and insert
> into spamd blacklists as necessary. The only caveat is
that threshold
> spam score for blacklisting should be kept very high to
prevent
> inserting false positives into spamd blacklist.
>
> In my experience spamd is very successful, but
SpamAssassin catches some
> spam e-mails that spamd misses occasionally. (After
all, OpenBSD
> maillists also use both, see http://www.openbsd.o
rg/mail.html).
>
> Please correct me if I am wrong, but I believe the OP's
point was missed
> in the other replies. I also would like to know what
people at misc
> think about such a scheme.

I think you summed it up; no modifications to spamd are
necessary,
your post-spamd filters can modify blacklists directly with
a little
ingenuity and some script-fu. Remember, it's unix. Modular.
Pieces.
Simplicity.

DS