Bug 7045 - "insecure dependency" and "can't locate object method"
Summary: "insecure dependency" and "can't locate object method"
Status: RESOLVED INVALID
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Libraries (show other bugs)
Version: 3.3.2
Hardware: PC Linux
: P2 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-28 15:43 UTC by Art Werschulz
Modified: 2014-05-28 23:14 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Art Werschulz 2014-05-28 15:43:55 UTC 
logrotate sends the following within the "Unmatched Entries" subsection of the SpamAssassin section:

 **Unmatched Entries**
    ): 864 Time(s)
     (Insecure dependency in eval while running setuid at /usr/share/perl5/vend\
or_perl/Mail/SpamAssassin/Plugin/HTMLEval.pm line 68.: 420 Time(s)
     (Can't locate object method "check_https_http_mismatch" via package "Mail:\
 [...]:SpamAssassin::PerMsgStatus" at (eval 1243) line 299.: 193 Time(s)
     (Can't locate object method "check_https_http_mismatch" via package "Mail:\
 [...]:SpamAssassin::PerMsgStatus" at (eval 1245) line 299.: 193 Time(s)
     (Can't locate object method "check_https_http_mismatch" via package "Mail:\
 [...]:SpamAssassin::PerMsgStatus" at (eval 1244) line 299.: 31 Time(s)
     (Can't locate object method "check_https_http_mismatch" via package "Mail:\
 [...]:SpamAssassin::PerMsgStatus" at (eval 1247) line 299.: 27 Time(s)
Comment 1 Karsten Bräckelmann 2014-05-28 23:14:04 UTC 
(In reply to Art Werschulz from comment #0)
> Can't locate object method "check_https_http_mismatch" via package

Your SA installation seems to be broken. That's stock code:

  $ grep -rl check_https_http_mismatch .
  Mail/SpamAssassin/Plugin/HTTPSMismatch.pm

I don't think this is a SA bug, closing RESOLVED INVALID, aka "not a bug". Please don't hesitate to re-open, if you strongly believe this to be a bug with SA, rather than a local issue.

If you need help, please tend to the users@ mailing-list.