Kris, thanks for the help. It looks to me like the problem may lie in
the way MIMEDefang 2.63 is interacting with SpamAssassin. When I run
spamassassin -D on a message that causes hits on the SpamHaus tests, it
scores correctly. Time to pester the MIMEDefang developers, maybe.
Karl
Kris De
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kris Deugau schrieb:
|> I appreciate the advice to hack our DNS configuration, but I'd prefer
|> to keep all my SpamAssassin tweaks in the SpamAssassin config file and
|> not have to document and (subsequently remember to actually look at
|> the doc
Karl Boyken wrote:
We're running SpamAssassin from MIMEDefang 2.63 on RedHat Linux
Enterprise Server 5. With previous versions, I'd hacked our site-wide
configuration file to use a local Spamhaus mirror. The file I hacked
was the MIMEDefang config file sa-mimedefang.cf, which is equivalent to
Let me try this again:
We're running SpamAssassin from MIMEDefang 2.63 on RedHat Linux
Enterprise Server 5. With previous versions, I'd hacked our site-wide
configuration file to use a local Spamhaus mirror. The file I hacked
was the MIMEDefang config file sa-mimedefang.cf, which is equivale
