16 Sep
2009
16 Sep
'09
11:50 a.m.
Dominic Cleal (dominic(a)computerkb.co.uk) wrote:
On Wednesday 16 September 2009 11:44:19 Robert
Leverington wrote:
Its worth noting that this method leaves the user's client to filter
mail based on headers, and it will always add the headers even if its
not spam (:true bit).
I like the authenticated bit though, hadn't thought of that myself :)
I had gone down the same path originally on my new server, but found I
liked the way it used to work on my old machine where the email gets
tagged as SPAM in the subject and also encloses the spam in the email
report as an attachment. If you want to go down that route I would
suggest sa-exim - was very easy to install and configure, and quite a
few resources out there explaining it.
Andy.
Currently I have done the following in attempting
to configure my mail
server to use SpamAssassin, per the documentation at [1]:
- Replace exim4-daemon-light with exim4-daemon-heavy
- Add "spamd_address = 212.13.194.5 783" to
/etc/exim4/exim4.conf.template.
You're missing adding the call to SpamAssassin in your DATA ACL - see the next
section in the Exim documentation that you linked to. There's a commented
out example in the acl_check_data ACL in the template file, or
acl/40_exim4-config_check_data in the split config.
I also exclude authenticated users from the scan, which neatly avoids scanning
outbound mail in most cases with the extra condition line:
warn
!authenticated = *
spam = Debian-exim:true
message = X-Spam_score: $spam_score\n\
X-Spam_score_int: $spam_score_int\n\
X-Spam_bar: $spam_bar\n\
X-Spam_report: $spam_report