Hi,
I have made some additions to the excellent rule set that comes with Pegasus' Content Control (SPAMBUST.DAT). My new rules are in a separate file (MY_SPAMBUST.DAT). This is to avoid problems when updating or re-installing Pegasus - e.g. the risk of overwriting the file, losing my additions.
It seems like Pegasus runs Content Control definitions in isolation, comparing the sum of weights for a definition to the threshold for that definition. Each definition starts fresh from zero. So, if SPAMBUST.DAT detects a dotted-decimal URL (weight 20) and MY_SPAMBUST.DAT detects an offer to lose weight (weight 35 - that is for Content Control, not the weight loss ;-) the sum of weights still isn't over the threshold of 50.
Is there a way to make CC use the combined weights from all definitions? Or is it safe to put my extra rules in the SPAMBUST.DAT file? In that case, how do I incorporate improvements to SPAMBUST.DAT that may be included in future releases of Pegasus?
Best regards,
Erik
<p>Hi,</p><p>I have made some additions to the excellent rule set that comes with Pegasus' Content Control (SPAMBUST.DAT). My new rules are in a separate file (MY_SPAMBUST.DAT). This is to avoid problems when updating or re-installing Pegasus - e.g. the risk of overwriting the file, losing my additions.
</p><p>It seems like Pegasus runs Content Control definitions in isolation, comparing the sum of weights for a definition to the threshold for that definition. Each definition starts fresh from zero. So, if SPAMBUST.DAT detects a dotted-decimal URL (weight 20) and MY_SPAMBUST.DAT detects an offer to lose weight (weight 35 - that is for Content Control, not the weight loss ;-) the sum of weights still isn't over the threshold of 50.</p><p>Is there a way to make CC use the combined weights from all definitions? Or is it safe to put my extra rules in the SPAMBUST.DAT file? In that case, how do I incorporate improvements to SPAMBUST.DAT that may be included in future releases of Pegasus?
&nbsp;</p><p>Best regards,</p><p>Erik&nbsp;</p>