Bug 7439 - Pyzor whitelisted messages hits PYZOR_CHECK too
Summary: Pyzor whitelisted messages hits PYZOR_CHECK too
Status: RESOLVED DUPLICATE of bug 6108
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Plugins (show other bugs)
Version: 3.4.2
Hardware: PC Linux
: P2 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-24 19:37 UTC by Vagisto Lerpinio
Modified: 2019-06-13 05:36 UTC (History)
4 users (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vagisto Lerpinio 2017-06-24 19:37:04 UTC 
Hello,


message header:
X-Spam-Pyzor: Whitelisted.
X-Spam-Report: 
	* -0.0 SPF_PASS SPF: sender matches SPF record
	*  0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	*      (********[at]gmail.com)
	* -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
	*  2.0 PYZOR_CHECK Listed in Pyzor (http://pyzor.sf.net/)
	*  0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily
	*      valid
	* -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's
	*       domain

spamassassin debug log:

giu 24 21:27:56.964 [6148] dbg: plugin: loading Mail::SpamAssassin::Plugin::Pyzor from @INC
giu 24 21:27:56.966 [6148] dbg: pyzor: network tests on, attempting Pyzor
[..]
giu 24 21:27:58.597 [6148] dbg: pyzor: pyzor is available: /usr/bin/pyzor
giu 24 21:27:58.597 [6148] dbg: util: secure_tmpfile created a temporary file /tmp/.spamassassin6148TmJsGhtmp
giu 24 21:27:58.597 [6148] dbg: check: create_fulltext_tmpfile, written 3444 bytes to file /tmp/.spamassassin6148TmJsGhtmp
giu 24 21:27:58.597 [6148] dbg: dns: entering helper-app run mode
giu 24 21:27:58.597 [6148] dbg: pyzor: opening pipe: /usr/bin/pyzor --homedir /etc/spamassassin/pyzor check < /tmp/.spamassassin6148TmJsGhtmp
giu 24 21:27:58.599 [6150] dbg: util: setuid: ruid=0 euid=0
giu 24 21:27:58.736 [6148] dbg: pyzor: [6150] finished: exit 1
giu 24 21:27:58.736 [6148] dbg: pyzor: got response: public.pyzor.org:24441 (200, 'OK') 2109107 78436
giu 24 21:27:58.737 [6148] dbg: dns: leaving helper-app run mode
giu 24 21:27:58.737 [6148] dbg: check: tagrun - tag PYZOR is now ready, value: Whitelisted.
giu 24 21:27:58.737 [6148] dbg: pyzor: listed: COUNT=2109107/5 WHITELIST=78436
giu 24 21:27:58.738 [6148] dbg: rules: ran eval rule PYZOR_CHECK ======> got hit (1)
giu 24 21:27:58.738 [6148] dbg: rules: running meta tests; score so far=1.885


version/OS
$ apt-cache policy spamassassin
spamassassin:
  Installed: 3.4.1-6
  Candidate: 3.4.1-6
  Version table:
 *** 3.4.1-6 500
        500 http://mirrors.linode.com/debian stable/main amd64 Packages
        100 /var/lib/dpkg/status

$ uname -a
Linux bjt 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u1 (2017-06-18) x86_64 GNU/Linux

Maybe a bug in pyzor plugin?
Comment 1 RW 2017-06-24 20:42:11 UTC 
It has been reported before see bug 6108. Whitelisted means that someone has reported it as non-spam and quite a lot spam hits are whitelisted.
Comment 2 Vagisto Lerpinio 2017-06-25 07:53:58 UTC 
OK, understand. So from 2009 never has been changed.

Thank you.
Comment 3 Dave Jones 2018-01-30 22:06:03 UTC 
I guess this is not enough of a problem to get attention in this bug or 6108.
Comment 4 Henrik Krohns 2019-06-13 05:36:18 UTC 
Closing as duplicate.

*** This bug has been marked as a duplicate of bug 6108 ***