<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
well, i think i must correct some things.<br>
there is only one email-account used for catching spam. and only mails that
spamassassin doesn´t identify correctly and<br>
manually forwarded by the users to this account are reported. nothing else!
so there is no autoreporting. only 100% by users identified spammails are
we want to provide a mechanism in our company to report spam that is not
being identified by other ressources such as dcc, razor, heuristical scans
Tony L. Svanstrom wrote:<br>
<pre wrap="">On Sun, 17 Nov 2002 the voices made Vernon Schryver write:
<pre wrap=""> - People using SpamAssassin to direct mail that their SA scoring
says is spam have surely installed SA, whether they direct that
spam to /dev/null, a mailbox, or a program such as `dccproc -t many`.
- I'm not sure what the other person is doing.
The way I understod it he's going to add SA to the server, and autoreport
everything SA catches to DCC.
My "problem" with that is that I don't think it's a good idea to autoreport
from one spamcatching solution to another, since that will just up the number
of false positives; so I guess my question is if there's an official policy
regarding reporting 'many' to DCC based on software like SA.