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
On Tue, 12 Jun 2007 03:04:23 -0700 (PDT), Praveen wrote:
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
Praveen wrote:
From the man page it appears that spamd relies on
static information about spam originators.
greylisting is pretty dynamic.
---
Lars Hansson
RW wrote:
On Tue, 12 Jun 2007 03:04:23 -0700 (PDT), Praveen wrote:
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
* Praveen [EMAIL PROTECTED] [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
From what I understand from the post, you are suggesting a scheme
similar to what snort2pf is doing for snort and pf. In layman terms,
when snort issues an alert, snort2pf informs pf about the attacker's IP,
and pf takes an action. AFAIK, this is currently the only way to convert
snort from an IDS
On 6/12/07, Soner Tari [EMAIL PROTECTED] 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
7 matches
Mail list logo
