[prev in list] [next in list] [prev in thread] [next in thread]
List: spamassassin-devel
Subject: [Bug 5841] New: AWL plugin prints function satus regardless debug option is set or not
From: bugzilla-daemon () issues ! apache ! org
Date: 2008-02-29 7:15:40
Message-ID: 5841.dev () spamassassin ! apache ! org
[Download RAW message or body]
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5841
Summary: AWL plugin prints function satus regardless debug option
is set or not
Product: Spamassassin
Version: 3.2.3
Platform: All
URL: http://www.nabble.com/Bug-or-by-design-behaviour-with-
Perl-interface.-to15704747.html
OS/Version: All
Status: NEW
Severity: major
Priority: P1
Component: Plugins
AssignedTo: dev@spamassassin.apache.org
ReportedBy: hcoscar@gmail.com
When using the Perl interface of SA, the following functions print the status of the
action taken despite debug option is not set:
$spam_assassin->add_all_addresses_to_whitelist ( $sa_message )
whitelist_address function in AWL Plugin; lines 456 to 459:
if ($whitelist->add_known_good_address($args->{address})) {
print "SpamAssassin auto-whitelist: adding address to whitelist: " . $args-
>{address} . "\n";
$status = 1;
}
$spam_assassin->add_all_addresses_to_blacklist ( $sa_message )
blacklist_address function in AWL Plugin; lines 420 to 423.
if ($whitelist->add_known_bad_address($args->{address})) {
print "SpamAssassin auto-whitelist: adding address to blacklist: " . $args-
>{address} . "\n";
$status = 0;
}
If I use these functions in a mail filter, them make the MTA interpret the print
command as a failure and by consecuence generating a delivery failure.
Enabling the print command along with the SA debug option would be better; most in
shared hosting environments when you do not have control over the code.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic