Re: spamc --reporttype= not working and curious log message.

2018-04-20 Thread John Hardin
On Fri, 20 Apr 2018, Kevin A. McGrail wrote: If RH/CentOS chose to simply remove those plugins, I would follow like and kind for building the package. +1 -- Kevin A. McGrail Asst. Treasurer & VP Fundraising, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project

Re: spamc --reporttype= not working and curious log message.

2018-04-20 Thread Kevin A. McGrail
If RH/CentOS chose to simply remove those plugins, I would follow like and kind for building the package. -- Kevin A. McGrail Asst. Treasurer & VP Fundraising, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171 On Fri, Apr

Re: spamc --reporttype= not working and curious log message.

2018-04-20 Thread Reio Remma
Neither spamassassin-3.4.0-2.el7.src.rpm (CentOS 7.4) nor spamassassin-3.4.1-17.fc27.src.rpm have the mentioned files in their source at all. Reio On 20.04.18 17:06, Kevin A. McGrail wrote: Giovanni, I was considering killing it as well. And I was going to look at how CentOS handled this in

Re: spamc --reporttype= not working and curious log message.

2018-04-20 Thread Kevin A. McGrail
Giovanni, I was considering killing it as well. And I was going to look at how CentOS handled this in the 3.4.1 for their rpms. -- Kevin A. McGrail Asst. Treasurer & VP Fundraising, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail -

Re: spamc --reporttype= not working and curious log message.

2018-04-20 Thread Giovanni Bechis
On 04/20/18 13:53, Kevin A. McGrail wrote: > FYI, I'm well aware of the 3.4 test issue with rulesrc.  I have it symlinked > to a checkout for my purposes.  I'll document that more. > > I am using CentOS 7 as well for testing and not aware of these perl > dependency issues you are having. 

Re: spamc --reporttype= not working and curious log message.

2018-04-20 Thread Reio Remma
I suspect rpmbuild gleans the requirements from script files when building. Mail-SpamAssassin-3.4.2/lib/Mail/SpamAssassin/Plugin/RabinKarpBody.pm:use RabinKarpAccel; Mail-SpamAssassin-3.4.2/lib/Mail/SpamAssassin/Util/MemoryDump.pm:use Devel::Size qw(size total_size);

Re: spamc --reporttype= not working and curious log message.

2018-04-20 Thread Kevin A. McGrail
FYI, I'm well aware of the 3.4 test issue with rulesrc. I have it symlinked to a checkout for my purposes. I'll document that more. I am using CentOS 7 as well for testing and not aware of these perl dependency issues you are having. Please elaborate further. -- Kevin A. McGrail Asst.

Re: spamc --reporttype= not working and curious log message.

2018-04-20 Thread Reio Remma
On 20.04.18 9:50, Giovanni Bechis wrote: On 04/19/18 09:24, Reio Remma wrote: [...] *Update:* none of the --option= switches work. handle_user (userdir) unable to find user: '' is caused because I have the -username switch as --username=amavis instead of --username amavis It worked in 3.4.1.

Re: spamc --reporttype= not working and curious log message.

2018-04-20 Thread Reio Remma
On 20.04.18 9:50, Giovanni Bechis wrote: On 04/19/18 09:24, Reio Remma wrote: [...] *Update:* none of the --option= switches work. handle_user (userdir) unable to find user: '' is caused because I have the -username switch as --username=amavis instead of --username amavis It worked in 3.4.1.

Re: spamc --reporttype= not working and curious log message.

2018-04-20 Thread Giovanni Bechis
On 04/19/18 09:24, Reio Remma wrote: [...] > *Update:* none of the --option= switches work. > > handle_user (userdir) unable to find user: '' is caused because I have the > -username switch as --username=amavis instead of --username amavis > > It worked in 3.4.1. > > Is it at all possible

Re: spamc --reporttype= not working and curious log message.

2018-04-20 Thread Giovanni Bechis
On 04/19/18 18:54, Reio Remma wrote: > I ran make test now - not exactly a pass. > cc dev@, I think this is a regression. > There were lots of complaints about: "Maybe you need to kill a running spamd > process?" There was no spamd running. > > The RPM is actually working nicely on our

Re: spamc --reporttype= not working and curious log message.

2018-04-19 Thread Reio Remma
I ran make test now - not exactly a pass. There were lots of complaints about: "Maybe you need to kill a running spamd process?" There was no spamd running. The RPM is actually working nicely on our production system (after I removed the = from spamc options). This is all on CentOS 7.

Re: spamc --reporttype= not working and curious log message.

2018-04-19 Thread Kevin A. McGrail
Certainly sounds odd. Does make test pass before you build the RPM? -- Kevin A. McGrail Asst. Treasurer & VP Fundraising, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171 On Thu, Apr 19, 2018 at 3:24 AM, Reio Remma

Re: spamc --reporttype= not working and curious log message.

2018-04-19 Thread Reio Remma
On 19.04.18 9:45, Reio Remma wrote: Hello! I'm trying to use this to report spam: spamc --reporttype=report --username=amavis < mail However all I get is: spamc[9632]: Please specify a legal report type It works if I omit the = after --reporttype. This is with SA 3.4.2 from SVN, iirc it

spamc --reporttype= not working and curious log message.

2018-04-19 Thread Reio Remma
Hello! I'm trying to use this to report spam: spamc --reporttype=report --username=amavis < mail However all I get is: spamc[9632]: Please specify a legal report type It works if I omit the = after --reporttype. This is with SA 3.4.2 from SVN, iirc it worked the other day with