[Bug 7560] Spamassassin 3.4.1 plugin: failed to parse plugin

2018-02-21 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7560

Kevin A. McGrail  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |INVALID

--- Comment #6 from Kevin A. McGrail  ---
Closing and marking as abusive.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7560] Spamassassin 3.4.1 plugin: failed to parse plugin

2018-02-21 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7560

Jamie  changed:

   What|Removed |Added

 Resolution|DUPLICATE   |---
 Status|RESOLVED|REOPENED

--- Comment #5 from Jamie  ---
There is NO new version!  Get a NEW version of spam assassin on 
the Debian package manager (apt) 

Get me the head developer for this project now! 

This is NOT a duplicate what so ever this matter is in no way resolve and 
this matter is NOT fixed! 

I am sick of this crap!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7560] Spamassassin 3.4.1 plugin: failed to parse plugin

2018-02-21 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7560

Kevin A. McGrail  changed:

   What|Removed |Added

 CC||kmcgr...@apache.org

--- Comment #4 from Kevin A. McGrail  ---
Your response is nonsensical.  Did you test the patch?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7560] Spamassassin 3.4.1 plugin: failed to parse plugin

2018-02-21 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7560

--- Comment #3 from Jamie  ---
This is NOT a duplicate of 7208 at all! 


7208 claims to be fixed this is NOT fixed and is currently on going! 

This comes from  7208

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7208

"Status:RESOLVED FIXED" 


Reopen this ticket immediately! or get me the project leader immediately.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7560] Spamassassin 3.4.1 plugin: failed to parse plugin

2018-02-21 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7560

Bill Cole  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||sa-bugz-20080315@billmail.s
   ||cconsult.com
 Status|NEW |RESOLVED

--- Comment #2 from Bill Cole  ---
This was fixed in the current development code branches: 3.4 for v3.4.2 release
and trunk for 4.0 release. 

As noted in bug #7208, this fix is not yet in any release version.

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7560] Spamassassin 3.4.1 plugin: failed to parse plugin

2018-02-21 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7560

Jamie  changed:

   What|Removed |Added

 CC||darkshad9...@gmail.com

--- Comment #1 from Jamie  ---
This has also been reported to the Debian maintainers as well
ID: 891041

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891041

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7560] New: Spamassassin 3.4.1 plugin: failed to parse plugin

2018-02-21 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7560

Bug ID: 7560
   Summary: Spamassassin 3.4.1 plugin: failed to parse plugin
   Product: Spamassassin
   Version: 3.4.1
  Hardware: Other
OS: Linux
Status: NEW
  Severity: major
  Priority: P2
 Component: spamassassin
  Assignee: dev@spamassassin.apache.org
  Reporter: darkshad9...@gmail.com
  Target Milestone: Undefined

Package: Spamassassin
Version: 3.4.1
Severity: 

The issue appears to be something with spam assassin 3.4.1 and one of its
modules
URILocalBL. 

I am running Debian 4.9.51-1

root@server1:/var/log# cpanm Geo::IP
Geo::IP is up to date. (1.51)

root@server1:/var/log# cpanm Mail::SpamAssassin
Mail::SpamAssassin is up to date. (3.004001)

uname -a 
Linux server1 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64
GNU/Linux

I am getting the following error spamming my logs and it won't run
the URILocalBL.pm module. 

Now this comes from my /var/log/mail.log

Feb 21 10:18:21 server1 spamd[29378]: plugin: failed to parse plugin (from
@INC): Experimental each on scalar is now forbidden at
/usr/share/perl5/Mail/SpamAssassin/Plugin/URILocalBL.pm line $
Feb 21 10:18:21 server1 spamd[29378]: Compilation failed in require at (eval
118) line 1,  line 717.
Feb 21 10:18:22 server1 spamd[29378]: netset: cannot include 127.0.0.0/8 as it
has already been included
Feb 21 10:18:23 server1 spamd[29378]: zoom: able to use 347/347 'body_0'
compiled rules (100%)
Feb 21 10:18:28 server1 spamd[29378]: spamd: server started on IO::Socket::IP
[::1]:783, IO::Socket::IP [127.0.0.1]:783 (running version 3.4.1)
Feb 21 10:18:28 server1 spamd[29378]: spamd: server pid: 29378
Feb 21 10:18:28 server1 spamd[29378]: spamd: server successfully spawned child
process, pid 29382
Feb 21 10:18:28 server1 spamd[29378]: spamd: server successfully spawned child
process, pid 29384
Feb 21 10:18:28 server1 spamd[29378]: prefork: child states: IS
Feb 21 10:18:28 server1 spamd[29378]: prefork: child states: II

root@server1:/etc/spamassassin# spamassassin --lint
Feb 21 11:05:33.649 [4736] warn: plugin: failed to parse plugin (from @INC):
Experimental each on scalar is now forbidden at
/usr/share/perl5/Mail/SpamAssassin/Plugin/URILocalBL.pm line 353,  line
717.
Feb 21 11:05:33.649 [4736] warn: Compilation failed in require at (eval 158)
line 1,  line 717.
Feb 21 11:05:34.191 [4736] warn: netset: cannot include 127.0.0.0/8 as it has
already been included

root@server1:/etc/spamassassin# spamassassin -V
SpamAssassin version 3.4.1
  running on Perl version 5.24.1

root@server1:/etc/spamassassin# perl -v

This is perl 5, version 24, subversion 1 (v5.24.1) built for
x86_64-linux-gnu-thread-multi
(with 75 registered patches, see perl -V for more detail)

Copyright 1987-2017, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl".  If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.

root@server1:/etc/spamassassin# which spamasassin
root@server1:/etc/spamassassin# which spamassassin
/usr/bin/spamassassin

root@server1:/etc/spamassassin# cpan -i Geo::IP
Loading internal null logger. Install Log::Log4perl for logging messages
Reading '/root/.cpan/Metadata'
  Database was generated on Wed, 21 Feb 2018 05:29:02 GMT
Geo::IP is up to date (1.51).

Now I have seen this before and the SpamAssassin team claims
That this was fixed in Spamassassin 3.4.1 back in 2015.

But this error is occurring again 

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7208
and 
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7332

http://spamassassin.1065346.n5.nabble.com/Bug-7208-New-URILocalBL-fails-to-load-td116602.html


root@server1:/etc/spamassassin# spamassassin -D --lint 2>&1 | grep -i URILoca
-A5
Feb 21 11:20:34.559 [5100] dbg: plugin: loading
Mail::SpamAssassin::Plugin::URILocalBL from @INC
Feb 21 11:20:34.562 [5100] warn: plugin: failed to parse plugin (from @INC):
Experimental each on scalar is now forbidden at
/usr/share/perl5/Mail/SpamAssassin/Plugin/URILocalBL.pm line 353,  line
717.
Feb 21 11:20:34.562 [5100] warn: Compilation failed in require at (eval 158)
line 1,  line 717.
Feb 21 11:20:34.562 [5100] dbg: config: fixed relative path:
/var/lib/spamassassin/3.004001/updates_spamassassin_org/10_default_prefs.cf
Feb 21 11:20:34.562 [5100] dbg: config: using
"/var/lib/spamassassin/3.004001/updates_spamassassin_org/10_default_prefs.cf"
for included file
Feb 21 11:20:34.562 [5100] dbg: config: read file
/var/lib/spamassassin/3.004001/updates_spamassassin_org/10_default_prefs.cf
Feb 21 11:20:34.577 [5100] dbg: config: fixed relative path:
/var/lib/spamassassin/3.004001/updates_spamassassin_org/10_hasbase.cf

Appears 

[Bug 6929] rules cannot match X-Spam-ASN

2018-02-21 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6929

Giovanni Bechis  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #11 from Giovanni Bechis  ---
Example added in revision r1824930.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7168] More POD errors and warnings

2018-02-21 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7168

Giovanni Bechis  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Giovanni Bechis  ---
Committed in r1824686, all pod errors fixed as well as those in spamd-apache2
subdirectory.

-- 
You are receiving this mail because:
You are the assignee for the bug.

FINAL REMINDER: CFP for Apache EU Roadshow Closes 25th February

2018-02-21 Thread Sharan F

Hello Apache Supporters and Enthusiasts

This is your FINAL reminder that the Call for Papers (CFP) for the 
Apache EU Roadshow is closing soon. Our Apache EU Roadshow will focus on 
Cloud, IoT, Apache Tomcat, Apache Http and will run from 13-14 June 2018 
in Berlin.
Note that the CFP deadline has been extended to *25*^*th* *February *and 
it will be your final opportunity to submit a talk for thisevent.


Please make your submissions at http://apachecon.com/euroadshow18/

Also note that early bird ticket registrations to attend FOSS Backstage 
including the Apache EU Roadshow, have also been extended and will be 
available until 23^rd February. Please register at 
https://foss-backstage.de/tickets


We look forward to seeing you in Berlin!

Thanks
Sharan Foga, VP Apache Community Development

PLEASE NOTE: You are receiving this message because you are subscribed 
to a user@ or dev@ list of one or more Apache Software Foundation projects.




[Bug 7559] New: DKIM default minimum key size should be 1024 bits

2018-02-21 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7559

Bug ID: 7559
   Summary: DKIM default minimum key size should be 1024 bits
   Product: Spamassassin
   Version: SVN Trunk (Latest Devel Version)
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P2
 Component: Plugins
  Assignee: dev@spamassassin.apache.org
  Reporter: da...@apache.org
  Target Milestone: Undefined

Current 3.4 branch and trunk DKIM code is allowing a 768 bit key size.

OpenDKIM header:

Authentication-Results: smtp3i.ena.net;
dkim=policy reason="signing key too small" (768-bit key)
header.d=mails-express.com header.i=@mails-express.com header.b="Mv82gS9m"

DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=mails-express.com; s=default;

That message is hitting DKIM_VALID but shouldn't be considered valid these days
since a key size less than 1024 can be cracked trivially.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 6473] Making Bayes Learn RelayCountry Metadata

2018-02-21 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6473

--- Comment #7 from Kevin A. McGrail  ---
(In reply to Henrik Krohns from comment #6)
> Sorry to be a downer, but in the words of Justin Mason, any Bayes
> modification should go through a
> https://wiki.apache.org/spamassassin/TenFoldCrossValidation. Long time ago I
> messed around adding all sorts of tokens and did some 10fcv tests, sometimes
> results were even worse. So I wouldn't necessarily go claming moar crap the
> better.

Great point Henrik.  tfcv is standard for me to consider the patch.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 6473] Making Bayes Learn RelayCountry Metadata

2018-02-21 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6473

Henrik Krohns  changed:

   What|Removed |Added

 CC||h...@hege.li

--- Comment #6 from Henrik Krohns  ---
Sorry to be a downer, but in the words of Justin Mason, any Bayes modification
should go through a
https://wiki.apache.org/spamassassin/TenFoldCrossValidation. Long time ago I
messed around adding all sorts of tokens and did some 10fcv tests, sometimes
results were even worse. So I wouldn't necessarily go claming moar crap the
better.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 6929] rules cannot match X-Spam-ASN

2018-02-21 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6929

--- Comment #10 from Giovanni Bechis  ---
No,
at line 422 of ASN.pm there is:


$pms->{msg}->put_metadata('X-ASN', join(' ',@asn_tag_data));


-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 6929] rules cannot match X-Spam-ASN

2018-02-21 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6929

Benny Pedersen  changed:

   What|Removed |Added

 CC||m...@junc.eu

--- Comment #9 from Benny Pedersen  ---
header TEST_AS1234  X-ASN =~ /^1234$/

not X-Spam-ASN ?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 6473] Making Bayes Learn RelayCountry Metadata

2018-02-21 Thread bugzilla-daemon
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6473

Kevin A. McGrail  changed:

   What|Removed |Added

 CC||kmcgr...@apache.org

--- Comment #5 from Kevin A. McGrail  ---
RW, any chance we can get an ICLA https://www.apache.org/licenses/icla.pdf to
consider this patch?

-- 
You are receiving this mail because:
You are the assignee for the bug.