Michael,
> I am assuming that since amavisd calls SA once per email (even with
> multiple recipients), that SA would be ignoring 'get_required_score' value.
> since that is different, potentially on all recipients.
Yes, the 'required_hits' and the get_required_score() are only used
by SpamAssassin to assemble a report header field and body text,
where a mismatch with a kill level / tag2 level is pretty much of
only cosmetic nature. The X-Spam-Level, X-Spam-Flag, and X-Spam-Score
from SA are ignored and replaced by amavis lookalikes anyway.
> reason I ask, I am working on a new DCC.pm that supports more of the
> commercial DCC functions, and one of the features of a 'non SA' type DCC
> install.
>
> # and if SpamAssassin concluded that the message is spam
> my $permsgstatus = $options->{permsgstatus};
> return if $permsgstatus->get_score() <
> ($permsgstatus->get_required_score() + $conf->{dcc_learn_score});
That would be a precedence. I believe currently no other plugin
compares score to required_hits for the moment.
> normally, DCC is run in a 'prequeue' filter, getting ip address and
> comparing checksums for all inbound email. That way, if multiple people
> get the email, DCC can keep track of that 'bulk' email, its volume and
> be able to deliver those scores to anyone querying the database.
>
> with SA, sa would set the required_score, and the new DCC.pm would be
> able to report back to DCC the ip addresses and fuzzy checksums of any
> emails that were above the sa required_score.
If this serves only as an approximate decision, I believe it would
not make much difference if kill level and required_hits are close
but not exactly of the same value.
> with how amavisd-new does it, I am not sure this would work, since I
> think amavisd passes the SA required_score (or am I wrong?)
No, it doesn't pass required_score to SA, it would not be possible to
do so given that each recipient may have a different kill/tag2 level
and there is only one required_score in SA. Instead, amavisd just
takes the score from SA, and compares it to each recipient's thresholds,
then decides what to do, individually for each recipient.
Mark
------------------------------------------------------------------------------
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
