Michael Curry

An increase in incoming spam over the past few weeks has led me to try to adjust SpamAssassin's scoring to nudge some of the more egregious spam examples past the threshold, but I've encountered a configuration problem. Via the cPanel interface, I've adjusted the scoring for some of the rules from their defaults (e.g. changing RAZOR2_CHECK from 0.9 to 1.2) and hit save, and the interface seems to accept my changes and shows the new scores. However, the full headers of new incoming emails still show SpamAssassin assigning the old default scores to the rules I've changed. Is there some non-obvious step I'm neglecting? Thanks for your help!