--On Wednesday, October 23, 2013 11:32 PM +0200 Axb <axb.li...@gmail.com>
wrote:
URIBL_BLOCKED is not good news .-)
I wouldn't touch that score...
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
Ok.
Here is something I don't understand -- Why I get utterly different values
from email that goes through the MTA, and the SA command line.
I *just* received an email, with the following scoring:
X-Spam-Flag: NO
X-Spam-Score: 2.717
X-Spam-Level: **
X-Spam-Status: No, score=2.717 tagged_above=-10 required=3
tests=[BAYES_50=0.8, HTML_EXTRA_CLOSE=0.001, HTML_MESSAGE=0.001,
RDNS_NONE=0.793, URI_HEX=1.122] autolearn=no
So I dumped it to a text file, and ran it through SA from the command line,
and I get:
X-Spam-Checker-Version: SpamAssassin 3.4.0-pre3-r1435395 (2013-01-18) on
edge02-zcs.vmware.com
X-Spam-Level: ***
X-Spam-Status: No, score=4.0 required=5.0
tests=RCVD_IN_MSPIKE_H2,RCVD_IN_PSBL,
RDNS_NONE,T_MIME_NO_TEXT,UNPARSEABLE_RELAY,URIBL_BLOCKED
autolearn=no
version=3.4.0-pre3-r1435395
Now, why don't I have "URIBL_BLOCKED" in *both*? It still seems to me that
URIBL lookups are not occurring when going through the MTA, regardless of
whether or not I'm blocked. Is Amavis screwing with things here, since SA
is called via Amavis?
--Quanah
--
Quanah Gibson-Mount
Architect - Server
Zimbra, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
