On 2/11/2013 3:23 AM, Anirudha Patil wrote:
I have a MTA setup of [Postfix + Amavis-new + ClamAV + Spamassasin] of
which only the spamassasin part is disabled. Now i wish to enable the
Spamcontrol part.
<snip>
[root@host spamassassin]# cat /etc/sysconfig/spamassassin
# Options to spamd
SPAMDOPTIONS="-d -c -m5 -H"
This is irrelevant if you are using SpamAssassin via Amavisd-new.
[root@host spamassassin]# cat local.cf <http://local.cf>
# These values can be overridden by editing
~/.spamassassin/user_prefs.cf <http://user_prefs.cf>
# (see spamassassin(1) for details)
# These should be safe assumptions and allow for simple visual sifting
# without risking lost emails.
required_hits 5
report_safe 0
rewrite_header Subject [SPAM]
When you are calling SA via Amavis, the portions of SA's config related
to required_hits and any header re-writing are ignored in favor of the
settings in the Amavis config.
[root@host spamassassin]# ps -elf | grep spam
5 S root 29836 1 46 81 0 - 7184 pause 09:38 ?
00:00:00 /usr/bin/spamd -d -c -m5 -H
1 S root 29839 29836 0 78 0 - 7184 - 09:38 ?
00:00:00 spamd child
1 S root 29840 29836 0 78 0 - 7184 - 09:38 ?
00:00:00 spamd child
1 S root 29841 29836 0 81 0 - 7184 - 09:38 ?
00:00:00 spamd child
1 S root 29842 29836 0 81 0 - 7184 - 09:38 ?
00:00:00 spamd child
1 S root 29843 29836 0 81 0 - 7184 - 09:38 ?
00:00:00 spamd child
4 R root 29845 28512 0 78 0 - 1171 - 09:38 pts/2
00:00:00 grep spam
Amavisd-new runs the SA code internally. You do not need to have spamd
running.
--
Bowie
