Am 14.03.2016 um 17:38 schrieb @lbutlr:
On Mar 14, 2016, at 9:27 AM, Reindl Harald <h.rei...@thelounge.net> wrote:
Am 14.03.2016 um 16:23 schrieb @lbutlr:
On Mar 14, 2016, at 6:42 AM, RW <rwmailli...@googlemail.com> wrote:
Unless you actually saw  email.amctheatres.com in X-Spam-Report, or in
debug, it's probably not what you are looking.

It slipped my mind, but HEADER_HOST_IN_BLACKLIST is misleading

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7256

That explains it. Since it is checking both the body and the headers I have to 
check the source of the message and see what it’s hitting. The blacklist 
setting I have, I thought, were pretty straight forward:

the rules below aren't it
they would hit "USER_IN_BLACKLIST"

blacklist_from *.119
blacklist_from *.administrator
blacklist_from *.admin

Then I’m lost.

 $ grep -ir blacklist /usr/local/etc/mail/spamassassin/* | grep -v _from
/usr/local/etc/mail/spamassassin/local.cf:score URI_HOST_IN_BLACKLIST  3.0
/usr/local/etc/mail/spamassassin/local.cf.sample:#   the opposite; blacklisted 
mails can also save CPU
/usr/local/etc/mail/spamassassin/local.cf.sample:# shortcircuit 
USER_IN_BLACKLIST       on
/usr/local/etc/mail/spamassassin/local.cf.sample:# shortcircuit 
USER_IN_BLACKLIST_TO    on
/usr/local/etc/mail/spamassassin/local.cf.sample:# shortcircuit 
SUBJECT_IN_BLACKLIST    on
/usr/local/etc/mail/spamassassin/v310.pre:# WhitelistSubject - 
Whitelist/Blacklist certain subject regular expressions
/usr/local/etc/mail/spamassassin/v310.pre.sample:# WhitelistSubject - 
Whitelist/Blacklist certain subject regular expressions

$ grep -ir blacklist /var/amavis/.spamassassin/

did you read the other replies like "No, you are looking for enlist_uri_host or blacklist_uri_host"?

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to