Bug 865 - Mail::SpamAssassin::PerMsgStatus (DIFFERENT_REPLY_TO) error
Summary: Mail::SpamAssassin::PerMsgStatus (DIFFERENT_REPLY_TO) error
Status: RESOLVED INVALID
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: 2.31
Hardware: PC FreeBSD
: P2 minor
Target Milestone: ---
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-09-09 21:01 UTC by jim arnold
Modified: 2002-12-13 11:16 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 jim arnold 2002-09-09 21:01:40 UTC 
Spamassassin is generating the following error in my mail log:

Failed to run DIFFERENT_REPLY_TO SpamAssassin test, skipping:
        (Can't locate object method "check_for_spam_reply_to" via package 
"Mail::SpamAssassin::PerMsgStatus" (perhaps you forgot to load 
"Mail::SpamAssassin::PerMsgStatus"?) at /usr/local/lib/perl5/site_perl/5.6.1/Mail/
SpamAssassin/PerMsgStatus.pm line 1701.
)

on line 1701 of the above referenced file I have this:
$result = $self->$evalsub(@args);

When I checked cpan I find that Mail::SpamAssassin::PerMsgStatus is up to date.

SA is still tagging spam correctly. Another FreeBSD box at work is showing
the same errors. I'm running the lastest SA, procmail and postfix from the ports.

Thanks for any clues on how to fix this. A thorough Google search didn't
turn up any answers.
Comment 1 Justin Mason 2002-09-19 05:41:10 UTC 
your config files do not match the lib files perl is finding.
Investigate @INC for old SA versions.
Comment 2 Duncan Findlay 2002-12-13 20:16:01 UTC 
Common config problem. Not a bug.