Newer versions of
SpamBlocker support several new features, giving you more control to fight spam, both inbound and outbound.
Many of the changes are listed here:
http://forum.directadmin.com/showthread.php?t=50059
Info on
easy_spam_figher (ESF) and
BlockCracking (BC).
If you're running CustomBuild 2.0, it can install these things for you (please make sure
pre-requisites for SpamAssassin are installed, before executing the commands):cd /usr/local/directadmin/custombuild
./build update
./build set eximconf yes
./build set eximconf_release 4.5
./build set blockcracking yes
./build set easy_spam_fighter yes
./build set spamd spamassassin
./build set exim yes
./build exim
./build set dovecot_conf yes
./build dovecot_conf
./build spamassassin
./build update
./build exim_conf
Where we recommend recompiling exim before doing ./build exim_conf, to ensure it has SRS compiled in.
SpamAssassin can also somewhat tricky to install, so we also recommend
that before installing EasySpamFighter (which requires SpamAssassin to
be running)
Custom Variables
The 4.3.0+ version of SpamBlocker supports custom variables and custom strings.
1) Custom strings (text shown in smtp output) should be taken from:/etc/exim.strings.conf
and any changes you want to override, add to /etc/exim.strings.conf.custom
with your desired changes. Do not edit the exim.strings.conf directly.
Also, the exim.strings.conf.custom MUST use == instead of = for it's
values, to let exim know that we want to override the defaults. It will
error out if you use a single = character, when it's already been set.
2) Custom variables (changes to the exim behavior/functionality) should be added to:/etc/exim.variables.conf.custom
They
can be values that already exist in /etc/exim.variables.conf.default,
or extra variables from the top section of the /etc/exim.conf. Once
you've set your exim.variables.conf.custom, they need to be merged into
/etc/exim.variables.conf, which CB2.0 can do for you, but using:./build exim_conf
We
used he merge method because exim does not allow a variable to be set
twice (== does not work), and also because we may want to add more
default variables in the future, but still allow you to override the
values you want.
It's important to use the correct method of customizing the data, so
that your changes remain when the exim.conf rewrite happens.
