https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6698
Bug #: 6698
Summary: New DCC.pm improves performance, is more resilient.
Product: Spamassassin
Version: 3.3.2
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Plugins
AssignedTo: [email protected]
ReportedBy: [email protected]
Classification: Unclassified
Created attachment 5010
--> https://issues.apache.org/SpamAssassin/attachment.cgi?id=5010
/tmp/DCCpatch.txt and DCC.pm
Vernon Schryver <[email protected]>, author of DCC has worked on a new DCC.pm
plugin
>From his email:
-----Original Message-----
From: Vernon Schryver [mailto:[email protected]]
Sent: Wednesday, November 09, 2011 12:52 PM
To: Michael Scheidell
Subject: RE: DCC.pm
> Let me try to present them again, since 3.3.3? 3.4? is on the horizon.
>
> Is there a bugzilla open for it yet? If not, I will open one.
I don't know.
> What are the changes? All upward compatible? Or will something change?
I believe it is entirely upward compatible.
Besides a lot of cleaning of the original ad hoc and now rather crufty perl
source, it has improved error messages, better searching for the dccproc and
cdcc programs, and speed improvements from calling them less frequently and
using dccsight instead of re-scanning the message.
It also has dcc_learn_score.
That mechanism reports spam detected by SpamAssassin with a score of 'many' to
DCC.
A DCC installation has started using it on its incoming mail of about 750K
messages/day. It has had little effect on DCC installations that set DCC
thresholds to reasonable values. Judging from the global graphs, it has
noticable effects on the majority that use the old DCC.pm default of 9999999
for 'many'.
The effect is to promote the count for a spam checksum from a substantial
number to 'many'
attached is patch (so you can see what changed) and full, DCC.pm.
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
