|
Drew Burchett wrote: > I made this same mistake yesterday.
Turned out that I hadn’t enabled razor in v310.pre. Thanks very much for the reply Drew! I found that the line loading the Razor plug-in in v310.pre
was commented out: # Razor2 - perform Razor2 message checks. # # Razor2 is disabled here because it is not available for
unlimited free # use. It is currently free for personal use, subject to
capacity # constraints. See the Cloudmark SpamNet Service Policy for
more details. # # loadplugin Mail::SpamAssassin::Plugin::Razor2 Uncommenting the last line fixed the issue. |
