On Wed, Sep 16, 2009 at 10:44:19AM +0000, Robert Leverington wrote:
Currently I have done the following in attempting to
configure my mail
server to use SpamAssassin, per the documentation at [1]:
[...]
Does anyone have any pointers regarding how I can
troubleshoot this, or
anything I am doing wrong?
Others have pointed you at how to do this. Other things I like
doing (roughly in order):
- Rejecting clients that give a malformed HELO/EHLO command, or that
try to HELO with my host name.
- Greylisting connections from hosts with no reverse DNS.
- Selecting a very small number of good quality DNSBLs and rejecting
connections from hosts contained therein.
- Greylisting hosts that are in a range of other, less trusted
DNSBLs. This allows use of a number of the rfc-ignorant DNSBLs
and RHSBLs which by themselves only demonstrate poor behaviour,
not outright spamminess.
I don't like to greylist everything, but it is an option which
some people are comfortable with.
- Pass data to SpamAssassin (resource-intensive), reject if scores
more than say 10, greylist connection if it scores >5.
- Pass data to clamav.
Personally I do these things in the RCPT ACL because by then I know
if the mail is to (root|postmaster|abuse)@*. I will tend to be more
lenient with these emails as it's more important they get through.
If anyone has hooked dspam or crm114 up to Exim in a nice way then
I'd be interested in hearing how it's working out..
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
"I remember the first time I made love. Perhaps it was not love exactly but I
made it and it still works." -- The League Against Tedium