Description of problem: All test with spamc reports NO spam even if there is a spam identified in /var/log/maillog by spamd. All spams are delivered to my mailbox. :( Version-Release number of selected component (if applicable): spamassassin-3.2.2-1.fc7 How reproducible: always Steps to Reproduce: 1. run spamd 2. create a spam mail file in /tmp/spamtest 3. run "spamc -R < /tmp/spamtest" Actual results: 0/0 Expected results: 24.7/4.0 ... identified spam details or something similiar... Additional info: Running spamassassin as separate program (not spamc) works well. See: spamassassin < /tmp/test | grep X-Spam-Status X-Spam-Status: Yes, score=43.0 required=1.0 tests=BAYES_99,DATE_IN_PAST_03_06, Previous version of spamassassin worked fine for my, only this latest not.
What is the result of: cat /usr/share/doc/spamassassin-3.2.2/sample-spam.txt | spamc
Created attachment 160520 [details] output of requested command Result has same MD5 checksum as source.
[ondrejj@work ~]$ md5sum /usr/share/doc/spamassassin-3.2.2/sample-spam.txt 23de00e370e172bf1131549161f4971b /usr/share/doc/spamassassin-3.2.2/sample-spam.txt [ondrejj@work ~]$ cat /usr/share/doc/spamassassin-3.2.2/sample-spam.txt | spamc | md5sum 23de00e370e172bf1131549161f4971b - [ondrejj@work ~]$
New information: turning off pyzor plugin (or uninstalling pyzor package) helps for me. May be you can simulate this bug by installing "pyzor" package and restarting spamassassin. Also it can be connected to bug #250547 also reported by me today.
http://koji.fedoraproject.org/packages/spamassassin/3.2.2/ Please test the latest build from here
Works fine. Thank you. It solved both my problems #250548 and #250547. Release: spamassassin-3.2.2-2.fc7