Description of problem: Since latest sa-update from 06 june Spamassassin logs to both messages and maillog Version-Release number of selected component (if applicable): spamassassin-3.4.0-4.fc20.x86_64 How reproducible: Allways Steps to Reproduce: 1. 2. 3. Actual results: Spamassassin logs to both messages and maillog Expected results: Spamassassin log to maillog only Additional info: Output of messages log after sa-update run 06 june: Jun 6 05:53:23 ls3ka systemd: Stopping Spamassassin daemon... Jun 6 05:53:23 ls3ka systemd: Starting Spamassassin daemon... Jun 6 05:53:23 ls3ka systemd: Started Spamassassin daemon. Jun 6 05:53:29 ls3ka spamd: Jun 6 05:53:29.933 [56521] info: spamd: server started on IO::Socket::IP [127.0.0.1]:783, IO::Socket::IP [::1]:783 (running version 3.4.0) Jun 6 05:53:29 ls3ka spamd: Jun 6 05:53:29.933 [56521] info: spamd: server pid: 56521 Jun 6 05:53:29 ls3ka spamd: Jun 6 05:53:29.936 [56521] info: spamd: server successfully spawned child process, pid 56598 Jun 6 05:53:29 ls3ka spamd: Jun 6 05:53:29.940 [56521] info: spamd: server successfully spawned child process, pid 56599 Jun 6 05:53:29 ls3ka spamd: Jun 6 05:53:29.942 [56521] info: prefork: child states: IS Jun 6 05:53:29 ls3ka spamd: Jun 6 05:53:29.942 [56521] info: prefork: child states: II Jun 6 05:54:27 ls3ka clamd: SelfCheck: Database status OK. Jun 6 05:54:27 ls3ka clamd[37565]: SelfCheck: Database status OK. Jun 6 05:55:01 ls3ka systemd: Starting Session 2815 of user root. Jun 6 05:55:01 ls3ka systemd: Started Session 2815 of user root. Jun 6 06:00:01 ls3ka systemd: Starting Session 2817 of user root. Jun 6 06:00:01 ls3ka systemd: Started Session 2817 of user root. Jun 6 06:00:01 ls3ka systemd: Starting Session 2816 of user root. Jun 6 06:00:01 ls3ka systemd: Started Session 2816 of user root. Jun 6 06:01:01 ls3ka systemd: Starting Session 2818 of user root. Jun 6 06:01:01 ls3ka systemd: Started Session 2818 of user root. Jun 6 06:01:34 ls3ka spamd: Jun 6 06:01:34.280 [56598] info: spamd: connection from localhost6.localdomain6 [::1]:36989 to port 783, fd 6 Jun 6 06:01:34 ls3ka spamd: Jun 6 06:01:34.284 [56598] info: spamd: setuid to sa-milt succeeded Jun 6 06:01:34 ls3ka spamd: Jun 6 06:01:34.299 [56598] info: spamd: processing message (unknown) for sa-milt:988 Jun 6 06:01:39 ls3ka spamd: Jun 6 06:01:39.604 [56598] info: spamd: identified spam (22.5/4.6) for sa-milt:988 in 5.3 seconds, 11688 bytes. Jun 6 06:01:39 ls3ka spamd: Jun 6 06:01:39.605 [56598] info: spamd: result: Y 22 - AXB_XMAILER_MIMEOLE_OL_1ECD5,BAYES_80,DCC_CHECK,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DOS_OE_TO_MX,FORGED_MUA_OUTLOOK,FORGED_OUTLOOK_HTML,FROM_MISSP_MSFT,HTML_FONT_LOW_CONTRAST,HTML_MESSA GE,MIME_HTML_ONLY,MISSING_MID,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS,SUBJECT_NEEDS_ENCODING,T_FROM_MISSP_DKIM,URIBL_BLACK,URIBL_DBL_SPAM,URIBL_JP_SURBL,URIBL_WS_SURBL scantime=5.3,size=11688,user=sa-milt,uid=988,required_score=4.6,rhost=localhost6.localdomain6,raddr=::1, rport=36989,mid=(unknown),bayes=0.946495,autolearn=spam autolearn_force=no Jun 6 06:01:39 ls3ka spamd: Jun 6 06:01:39.684 [56521] info: prefork: child states: II
I am not seeing this here on my f20 machine... ;( Are you using rsyslog? Have you made any changes to rsyslog.conf? What does: 'rpm -V spamassassin rsyslog' show?
I have not changed anything. rsyslog.conf is original. I checked it. [root@ls3ka ~]# rpm -V spamassassin rsyslog S.5....T. c /etc/mail/spamassassin/local.cf S.5....T. c /etc/mail/spamassassin/v310.pre [root@ls3ka ~]#
What are your changes to local.cf? anything logging related? Can you attach your /etc/sysconfig/spamassassin also?
There is nothing logging related in /etc/mail/spamassassin/local.cf [root@ls3ka ~]# more /etc/sysconfig/spamassassin # Options to spamd SPAMDOPTIONS="-c -m5 -H"
I just confirm that I recently discovered the same behaviour!
ok. I was able to track this down. Hopefully fixed package on the way soon...
spamassassin-3.4.0-6.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/spamassassin-3.4.0-6.fc20
Package spamassassin-3.4.0-6.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing spamassassin-3.4.0-6.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-7509/spamassassin-3.4.0-6.fc20 then log in and leave karma (feedback).
Thank you as I installed spamassassin-3.4.0-6.fc20 it seems to be solved now.
Fixed. But still an issue on the spamassassin package related to https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7057
spamassassin-3.4.0-7.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/spamassassin-3.4.0-7.fc20
spamassassin-3.4.0-7.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.