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

            Bug ID: 8116
           Summary: Perl-Module: Rules fired using $status->got_hit () are
                    not listed in get_report() with 4.0.0
           Product: Spamassassin
           Version: 4.0.0
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: spamassassin
          Assignee: dev@spamassassin.apache.org
          Reporter: erh...@wor.net
  Target Milestone: Undefined

While testing the new 4.0.0 Release, we found the following mis-behaviour when
using SA via the Perl module.

We have some special-rules that are fired externally using the Perl interface
of SA. However with 4.0.0 the checks which have been fired using got_hit() are
not showing up in the report output produced by get_report(). Besides that the
checks are correctly listed in $status->get_names_of_tests_hit_with_scores().
So it seems as SA is half-aware of those got_hit() fired checks somehow.

Additionally we found the score displayed in the report output was sometimes
variing. In some cases the score of the got_hit() rules were included in the
get_report() score sum, sometimes not. We don't see this behaviour with SA
3.4.x, but we haven't managed to built a clean reproduction code snippet yet.

Here is a short sample code to reproduce the got_hit() bug:

<--- CODE --->

require Mail::SpamAssassin;
my $spamtest = Mail::SpamAssassin->new();

open(my $message, '<', "test-mail.txt")
  or die "Could not open file '$filename' $!";

my $mail = $spamtest->parse($message);
my $status = $spamtest->check($mail);

$status->got_hit("MY_TEST_CHECK", "This is a test", score => 100);

print("\$status->get_report()\n");
print($status->get_report());

$status->finish();
$mail->finish();
$spamtest->finish();

<--- END-OF-CODE --->


Thanks in advance for looking into this!
Let me know if you have any questions or need more information.

Cheers,
Andreas

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

Reply via email to