Description of problem: Using the spamc (spam-client) executable does not return an error code or put the right headers in the output. It works fine with /usr/bin/spamassassin -e . Version-Release number of selected component (if applicable): Cauldron. How reproducible: Always. Steps to Reproduce: 1. Filter an email message through /usr/bin/spamc -s 100000000 -E -t 30. Reproducible: Steps to Reproduce:
(In reply to Shlomi Fish from comment #0) > Description of problem: > > Using the spamc (spam-client) executable does not return an error code or > put the right headers in the output. It works fine with > /usr/bin/spamassassin -e . > > Version-Release number of selected component (if applicable): > > Cauldron. > > How reproducible: > > Always. > > Steps to Reproduce: > 1. Filter an email message through /usr/bin/spamc -s 100000000 -E -t 30. > > > Reproducible: > > Steps to Reproduce: OK, I found out what the problem was: spamc was unable to connect to the spamd TCP socket so it simply passed the message as is. The problem is that SPAMDOPTIONS in /etc/sysconfig/spamd used --socketpath while to read from "man spamd": --socketpath pathname Listen on a UNIX domain socket at path pathname, in addition to sockets specified with a "--listen" option. This option is provided for compatibility with older versions of spamd. Starting with version 3.4.0 the "--listen" option can also take a UNIX domain socket as its value (an absolute path name). Unlike "--socketpath", the "--listen" option may be specified multiple times if spamd needs to listen on multiple UNIX or INET or INET6 sockets. Warning: the Perl support on BSD platforms for UNIX domain sockets seems to have a bug regarding paths of over 100 bytes or so (SpamAssassin bug 4380). If you see a 'could not find newly- created UNIX socket' error message, and the path appears truncated, this may be the cause. Try using a shorter path to the socket. By default, use of --socketpath without --listen will inhibit SSL connections and unencrypted TCP connections. To add other sockets, specify them with --listen, e.g. '--listen=:' or '--listen=*:' After I changed SPAMDOPTIONS to this line, everything is working again: SPAMDOPTIONS="-d -c -m5 -H --syslog=/var/log/spamassassin/spamd.log --listen=/run/spamd/spamd.socket --listen=localhost:783" I think I'll fix the package too. Regards, -- Shlomi Fish
Fixed in spamassassin-3.4.0-2.mga5.src.rpm . Resolving as fixed.
Status: NEW => RESOLVEDResolution: (none) => FIXED