Gianluca
1, Your .PRE files are (by default) in:
%ProgramFiles(x86)%\JAM Software\SpamAssassin for Windows\etc\spamassassin
You will find the 'AutoLearnThreshold' plugin you need in v310.pre.
You will find the BAYES and SHORTCIRCUIT plugins you need in v320.pre
(they may already be enabled - but if not just removed the #)
Then remove the loading of them from your Local.cf.
2,
To make them useful, your LOCAL.CF should read something like:
(Example)
ifplugin Mail::SpamAssassin::Plugin::Shortcircuit
# default: strongly-whitelisted mails are *really* whitelisted
now, if the
# shortcircuiting plugin is active, causing early exit to save CPU
load.
# Uncomment to turn this on
#
shortcircuit USER_IN_WHITELIST on
shortcircuit USER_IN_DEF_WHITELIST on
endif # Mail::SpamAssassin::Plugin::Shortcircuit
On 18/02/2018 01:21, John Hardin wrote:
On Sun, 18 Feb 2018, Gianluca Furnarotto wrote:
I’ve done this modifications in local.cf:
# ifplugin
loadplugin Mail::SpamAssassin::Plugin::Shortcircuit
loadplugin Mail::SpamAssassin::Plugin::AutoLearnThreshold
loadplugin Mail::SpamAssassin::Plugin::Bayes
#ok_languages en it
ok_locales en
# endif
And command spamassassin —lint doesn’t show any errors. Tomorrow I
will continue
the debugging. It seems it doesn’t agree ifplugin-endif and also
ok_languages
Three points:
(1) the syntax for "ifplugin" is:
ifplugin Mail::SpamAssassin::Plugin::whatever
It's a test to see whether that plugin is loaded, so that you can
write plugin-dependent rules without generating lint errors when the
plugin isn't loaded.
(2) "ifplugin" only accepts one plugin name.
(3) "loadplugin" commands should be in your v340.pre file, so that
they get loaded before any rules.
If you added that "ifplugin" block to your config file, what exactly
were you trying to achieve with that block?
