You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2018/02/21 19:18:24 UTC

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

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: darkshad9999@gmail.com
  Target Milestone: Undefined

Package: Spamassassin
Version: 3.4.1
Severity: <Important>

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, <DATA> 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, <DATA> line
717.
Feb 21 11:05:33.649 [4736] warn: Compilation failed in require at (eval 158)
line 1, <DATA> 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, <DATA> line
717.
Feb 21 11:20:34.562 [5100] warn: Compilation failed in require at (eval 158)
line 1, <DATA> 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 to fail well when the module is run directly. 

perl -c /usr/share/perl5/Mail/SpamAssassin/Plugin/URILocalBL.pm
Experimental each on scalar is now forbidden at
/usr/share/perl5/Mail/SpamAssassin/Plugin/URILocalBL.pm line 353, <DATA> line
717.

Now line 353 of /usr/share/perl5/Mail/SpamAssassin/Plugin/URILocalBL.pm is 

   while (my($host, $domain) = each $info->{hosts}) {


This is more of the code in the same area in URILocalBL.pm

    # look for W3 links only
    next unless (defined $info->{types}->{a});

    while (my($host, $domain) = each $info->{hosts}) {

      # skip if the domain name was matched
      if (exists $rule->{exclusions} && exists $rule->{exclusions}->{$domain})
{
        dbg("check: uri_local_bl excludes %s as *.%s\n", $host, $domain);
        next;
      }

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

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

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7560

Kevin A. McGrail <km...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |INVALID

--- Comment #6 from Kevin A. McGrail <km...@apache.org> ---
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

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7560

Bill Cole <sa...@billmail.scconsult.com> changed:

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

--- Comment #2 from Bill Cole <sa...@billmail.scconsult.com> ---
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

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7560

Jamie <da...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |darkshad9999@gmail.com

--- Comment #1 from Jamie <da...@gmail.com> ---
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] Spamassassin 3.4.1 plugin: failed to parse plugin

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7560

--- Comment #3 from Jamie <da...@gmail.com> ---
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

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7560

Kevin A. McGrail <km...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kmcgrail@apache.org

--- Comment #4 from Kevin A. McGrail <km...@apache.org> ---
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

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7560

Jamie <da...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|DUPLICATE                   |---
             Status|RESOLVED                    |REOPENED

--- Comment #5 from Jamie <da...@gmail.com> ---
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.