You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Birta Levente <bl...@gmail.com> on 2015/04/30 13:09:16 UTC
TxRep $msgscore warning
Hi
I saw the bug report about TxRep warning:
_WARN: Use of uninitialized value $msgscore in addition (+) at
/usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line 1415.
_WARN: Use of uninitialized value $msgscore in subtraction (-)
I just wonder if there is any workaroung for that or if exists any
effect of this warning?
Thanks
--
Levi
Re: TxRep $msgscore warning
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 5/5/2015 1:54 PM, Carlos Velasco wrote:
> Yes, spamc/spamd.
Ahh. What MTA are you using?
And if you are getting the uninitialized warnings, can you send me an
example email off list?
regards,
KAM
Re: TxRep $msgscore warning
Posted by Carlos Velasco <ca...@nimastelecom.com>.
Yes, spamc/spamd.
Regards
-------- Original Message --------
Subject: Re: TxRep $msgscore warning
From: Kevin A. McGrail <KM...@PCCC.com>
To: Carlos Velasco <ca...@nimastelecom.com>,
users@spamassassin.apache.org <us...@spamassassin.apache.org>
Date: 5/5/2015 19:53:00
> On 5/5/2015 7:59 AM, Carlos Velasco wrote:
>> Hi,
>>
>> After activating TxRep I always receive these warnings.
>> I use mysql for TxRep and I see a lot of "xxxxxxxx@sa_generated"
>> entries in the database, don't know if they are right.
>>
>> I have activated all spamd debugs and included your block in TxRep.
>> This is the output:
> Are you using spamc/spamd for your spamassassin testing?
>
> Regards,
> KAM
Re: TxRep $msgscore warning
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 5/5/2015 7:59 AM, Carlos Velasco wrote:
> Hi,
>
> After activating TxRep I always receive these warnings.
> I use mysql for TxRep and I see a lot of "xxxxxxxx@sa_generated"
> entries in the database, don't know if they are right.
>
> I have activated all spamd debugs and included your block in TxRep.
> This is the output:
Are you using spamc/spamd for your spamassassin testing?
Regards,
KAM
Re: Re: TxRep $msgscore warning
Posted by Carlos Velasco <ca...@nimastelecom.com>.
Hi,
After activating TxRep I always receive these warnings.
I use mysql for TxRep and I see a lot of "xxxxxxxx@sa_generated" entries
in the database, don't know if they are right.
I have activated all spamd debugs and included your block in TxRep. This
is the output:
===
rules: running one_line_body tests; score so far=-2.601
rules: running head tests; score so far=-2.601
rules: running body tests; score so far=-2.601
rules: running uri tests; score so far=-2.601
rules: running rawbody tests; score so far=-2.601
rules: running full tests; score so far=-2.601
rules: running meta tests; score so far=-2.601
check: running tests for priority: 1000
rules: running one_line_body tests; score so far=-2.601
rules: running head tests; score so far=-2.601
rules: running head_eval tests; score so far=-2.601
learn: auto-learn: currently using scoreset 3, recomputing score based
on scoreset 1
learn: auto-learn: not considered head or body scores: -0.7
learn: auto-learn: message score: -2.601, computed score for autolearn: -0.7
dbiplugin: dbi:mysql:spam:1.1.1.1 need ping? yes
dbiplugin: Creating new database handle to
'spam:1.1.1.1_spam_xxxxxx_AutoCommit=1_PrintError=0_Username=yyyyyyyyy'
auto-whitelist: sql-based connected to DBI:mysql:spam:1.1.1.1
auto-whitelist: sql-based using username: xxxxxxxxxx
TxRep: Parameters: self:
Mail::SpamAssassin::Plugin::TxRep=HASH(0x2ac2918) storage: pms:
Mail::SpamAssassin::PerMsgStatus=HASH(0x4690360), key: MSG_ID, id:
34a82b329b230df129b3b12a5bf6cc7e2ab93cd2@sa_generated, ip: , signedby:
1430826824, msgscore:
TxRep: weight: 1
TxRep: undefined - Caller Info: Package:
Mail::SpamAssassin::Plugin::TxRep - Filename:
/usr/lib/perl5/site_perl/5.16.2/Mail/SpamAssassin/Plugin/TxRep.pm -
Line: 1371
auto-whitelist: sql-based get_addr_entry: no entries found for
34a82b329b230df129b3b12a5bf6cc7e2ab93cd2@sa_generated|1430826824
auto-whitelist: sql-based
34a82b329b230df129b3b12a5bf6cc7e2ab93cd2@sa_generated|1430826824 scores
0, count 0
check: tagrun - tag TXREP_MSG_ID is now ready, value: 0.0
check: tagrun - tag TXREP_MSG_ID_COUNT is now ready, value: 0.0
check: tagrun - tag TXREP_MSG_ID_PRESCORE is now ready, value: -2.6
TxRep: reputation: none, count: 0, weight: 1.0, delta: 0.000, MSG_ID:
34a82b329b230df129b3b12a5bf6cc7e2ab93cd2@sa_generated
auto-whitelist: sql-based add_score/insert score 0:
xxxxxxx|34a82b329b230df129b3b12a5bf6cc7e2ab93cd2@sa_generated|none|1|0|1430826824
TxRep: message 34a82b329b230df129b3b12a5bf6cc7e2ab93cd2@sa_generated
already scanned, using old data; post-TxRep score: -2.368
rules: running body tests; score so far=-2.368
rules: running uri tests; score so far=-2.368
rules: running rawbody tests; score so far=-2.368
rules: running full tests; score so far=-2.368
rules: running meta tests; score so far=-2.368
===
TxRep.pm - Line: 1371
===
sub check_reputations {
###########################################################################
my $self = shift;
my $delta;
if ($self->open_storages()) {
if ($self->{conf}->{txrep_user2global_ratio} &&
$self->{user_storage} != $self->{global_storage}) {
my $user = $self->check_reputation('user_storage', @_);
my $global = $self->check_reputation('global_storage',@_);
$delta = (defined $user && $user==$user) ?
( $self->{conf}->{txrep_user2global_ratio} * $user + $global
) / ( 1 + $self->{conf}->{txrep_user2global_ratio} ) :
$global;
} else {
1371: ==> $delta = $self->check_reputation(undef,@_);
}
}
return $delta;
}
===
Regards,
Carlos Velasco
-------- Original Message --------
Subject: Re: TxRep $msgscore warning
From: Kevin A. McGrail <KM...@PCCC.com>
To: J.J. Day <da...@hotmail.com>, Joe Quinn <jq...@pccc.com>
Cc: "users@spamassassin.apache.org" <us...@spamassassin.apache.org>,
Date: Thu, 30 Apr 2015 13:15:07 -0400
> On 4/30/2015 11:44 AM, J.J. Day wrote:
>> FWIW, I switched to TxRep several months ago. Every message generates
>> both error lines. I have added a test to initialize $msgscore to
>> avoid filling my log files. Spam messages seem to all generate a
>> negative offset of ~1/3 the total. I copied a sample to the end.
>>
>> My setup is:
>> FreeBSD 10.0
>> Sendmail 8.14.7
>> Mimedefang 2.75
>> SpamAssassin 3.4.0
>> Cyrus 2.4.17
>>
>> I hope this helps.
> Interesting. So you are using the API. On your same box if you run
> spamassassin -t with your sample, can you recreate the issue?
>
> Otherwise, the sample doesn't help us because we can't recreate the
> issue, unfortunately.
>
>
> DFS, with MD calling SA as an API, how do you turn on a debug
> channel? Happen to know?
>
>
> Can you add this block of code above line 1386 in the current
> TxRep.pm? Then we'll try and figure out how to enable the TxRep debug
> channel from MD so you can log the info and relay it. It also should
> hide the informat
>
>
> {
> #Bug 7164, trying to find out reason for these: _WARN: Use of
> uninitialized value $msgscore in addition (+) at
> /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line 1415.
> no warnings;
>
> unless (defined $msgscore) {
> #Output some params and the calling function so we can identify
> more about this bug
> dbg("TxRep: Parameters: self: $self storage: $storage pms: $pms,
> key: $key, id: $id, ip: $ip, signedby: $signedby, msgscore: $msgscore");
> dbg("TxRep: weight: $weight");
>
> my ($package, $filename, $line) = caller();
>
> chomp($package);
> chomp($filename);
> chomp($line);
>
> dbg("TxRep: $msgscore undefined - Caller Info: Package: $package
> - Filename: $filename - Line: $line");
>
> #Define $msgscore as a triage to hide warnings while we find the
> root cause
> $msgscore = 0;
> }
> }
>
> Here's more detail about where it needs to be:
>
> sub check_reputation {
> ###########################################################################
>
> my ($self, $storage, $pms, $key, $id, $ip, $signedby, $msgscore) = @_;
>
> my $delta = 0;
> my $weight = ($key eq 'MSG_ID')? 1 :
> eval('$pms->{main}->{conf}->{txrep_weight_'.lc($key).'}');
>
> --> Block here
>
> if (defined $weight && $weight) {
>
> Regards,
> KAM
Re: TxRep $msgscore warning
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 4/30/2015 4:51 PM, J.J. Day wrote:
> I may have done something wrong. Mimedefang is dying with an error.
> I attached the defang log portion and the diffs for TxRep and mimedefang.
Sorry JJ,
My lack of clarity.
For MD, I didn't want you to add an entire line, just the parameter to
your SpamAssassin object call.
I assume you removed that so you were back to mail flow. The change to
txrep should hide the issue at least. Have the errors in your logs gone
away?
Can you share your mimedefang-filter (offlist is fine)? I'll try and
figure out with your filter how to enable SA Debugging for the TxRep
channel.
I very much appreciate your willingness to help!
Regards,
KAM
Re: TxRep $msgscore warning
Posted by "J.J. Day" <da...@hotmail.com>.
>> On Apr 30, 2015, at 1:29 PM, Kevin A. McGrail <KM...@PCCC.com> wrote:
>>
>> On 4/30/2015 1:15 PM, Kevin A. McGrail wrote:
>> Can you add this block of code above line 1386 in the current TxRep.pm? Then we'll try and figure out how to enable the TxRep debug channel from MD so you can log the info and relay it. It also should hide the informat
> Can you try this in your milter? Untested but based on discussions with DFS from MD: $SASpamTester = Mail::SpamAssassin->new( debug=>"TxRep" )
>
> Regards,
> KAM
I may have done something wrong. Mimedefang is dying with an error.
I attached the defang log portion and the diffs for TxRep and mimedefang.
Regards,
Mimedefang log extract:
Apr 30 14:51:22 mailsys mimedefang-multiplexor[12711]: started;
minSlaves=2, maxSlaves=10, maxRequests=500, maxIdleTime=300, busyTim
eout=600, clientTimeout=10
Apr 30 14:51:22 mailsys mimedefang-multiplexor[12711]: Starting slave 0
(pid 12713) (1 running): Bringing slaves up to minSlaves (2)
Apr 30 14:51:22 mailsys mimedefang[12727]: IP validation header is
X-MIMEDefang-Relay-b2b825afac8a3d1ce58c1f997293ee3a75854c05
Apr 30 14:51:22 mailsys mimedefang[12727]: MIMEDefang alive.
slavesReservedForLoopback=-1 AllowNewConnectionsToQueue=0 doRelayCheck=
0 doHeloCheck=1 doSenderCheck=1 doRecipientCheck=1
Apr 30 14:51:22 mailsys mimedefang[12727]: Multiplexor alive - entering
main loop
Apr 30 14:51:22 mailsys mimedefang-multiplexor[12711]: Slave 0 stderr:
Can't locate object method "new" via package "Mail::SpamAssas
sin" at /usr/local/etc/mimedefang/mimedefang-filter line 66.
Apr 30 14:51:22 mailsys mimedefang-multiplexor[12711]: Slave 0 stderr:
Compilation failed in require at /usr/local/bin/mimedefang.pl
line 5279.
Apr 30 14:51:22 mailsys mimedefang-multiplexor[12711]: Reap: slave 0 (pid
12713) exited normally with status 255 (SLAVE DIED UNEXPEC
TEDLY)
Apr 30 14:51:22 mailsys mimedefang-multiplexor[12711]: Slave 0 resource
usage: req=0, scans=0, user=0.337, sys=0.031, nswap=0, majfl
t=0, minflt=1966, maxrss=10788, bi=0, bo=0
TxRep diff:
#diff TxRep.original
/usr/local/lib/perl5/site_perl/5.16/Mail/SpamAssassin/Plugin/TxRep.pm
1384a1385,1406
> {
> #Bug 7164, trying to find out reason for these: _WARN: Use of
uninitialized value $msgscore in addition (+) at
/usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line 1415.
> no warnings;
>
> unless (defined $msgscore) {
> #Output some params and the calling function so we can identify
more about this bug
> dbg("TxRep: Parameters: self: $self storage: $storage pms: $pms,
key: $key, id: $id, ip: $ip, signedby: $signedby, msgscore: $msgscore");
> dbg("TxRep: weight: $weight");
>
> my ($package, $filename, $line) = caller();
>
> chomp($package);
> chomp($filename);
> chomp($line);
>
> dbg("TxRep: $msgscore undefined - Caller Info: Package: $package
- Filename: $filename - Line: $line");
>
> #Define $msgscore as a triage to hide warnings while we find the
root cause
> $msgscore = 0;
> }
> }
>
Mimedefang diff:
#diff /usr/local/etc/mimedefang/mimedefang-filter
/usr/local/etc/mimedefang/mimedefang-filter.before.patch
63,68d62
< # TxRep $msgscore debug patch activation
< # per KAM email 4/30/2015 @ 13:29
< #***********************************************************************
< $SASpamTester = Mail::SpamAssassin->new(debug=>"TxRep");
<
< #***********************************************************************
Re: TxRep $msgscore warning
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 4/30/2015 1:15 PM, Kevin A. McGrail wrote:
> Can you add this block of code above line 1386 in the current
> TxRep.pm? Then we'll try and figure out how to enable the TxRep debug
> channel from MD so you can log the info and relay it. It also should
> hide the informat
Can you try this in your milter? Untested but based on discussions with
DFS from MD: $SASpamTester = Mail::SpamAssassin->new( debug=>"TxRep" )
Regards,
KAM
Re: TxRep $msgscore warning
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 5/5/2015 10:12 AM, J.J. Day wrote:
> It seemed simpler so I selected Choice A. This is the diff of
Diff looks good.
> and restarted mimedefang. But the logs still look the same.
Wherever you normally get the unintialized errors prior...
> This and the patch to TxRep are currently the only code changes made for
> the $msgscore warning. Is there more that I need to do somewhere else? Or,
> am I looking in the wrong place for the debug output?
It's possible I patched it too well and the warnings is turned off for
more than the block I intended. You can try removing the no warnings in
TxRep.pm.
Sorry, this bug is hard because I can't duplicate on any of the systems
I control.
regards,
KAM
Re: TxRep $msgscore warning
Posted by "J.J. Day" <da...@hotmail.com>.
Hi KAM,
It seemed simpler so I selected Choice A. This is the diff of
mimeassassin.pl:
6839a6840,6856
#***********************************************************************
> # %spam_assassin_init debug channel mod
> # From: "Kevin A. McGrail" <KM...@PCCC.com>
> # Subject: Re: TxRep $msgscore warning
> # Date: Mon, 4 May 2015 10:47:58 -0500
> # From more discussins, there are two ways with MD to
activate the TxRep
> # debug channel if you using spam_assassin_init in your
filter.
> # Choice A)
> my $sa_args = {
> local_tests_only => $SALocalTestsOnly,
> dont_copy_prefs => 1,
> userprefs_filename => $config,
> user_dir =>
$Features{'Path:QUARANTINEDIR'},
> debug => 'TxRep'
> };
#***********************************************************************
I then ran a reload but didn't see any changes in the logs so I stopped
and restarted mimedefang. But the logs still look the same.
This and the patch to TxRep are currently the only code changes made for
the $msgscore warning. Is there more that I need to do somewhere else? Or,
am I looking in the wrong place for the debug output?
Regards,
JJ
> On May 4, 2015, at 10:48 AM, Kevin A. McGrail <KM...@PCCC.com> wrote:
>
> From more discussins, there are two ways with MD to activate the TxRep debug channel if you using spam_assassin_init in your filter.
>
> Choice A) modify mimedefang.pl directly, i.e. spam_assassin_init to add the debug channel:
>
> my $sa_args = {
> local_tests_only => $SALocalTestsOnly,
> dont_copy_prefs => 1,
> userprefs_filename => $config,
> user_dir => $Features{'Path:QUARANTINEDIR'},
> debug => 'TxRep'
> };
>
> And run md-mx-ctrl reread to pick up the change
>
> or
>
> Choice B) you can define your own SASpamTester object at the top of your filter something like this though you'll have to define the variables $SALocaltestsOnly, $config, and possibly $Features.
>
> my $sa_args = {
> local_tests_only => $SALocalTestsOnly,
> dont_copy_prefs => 1,
> userprefs_filename => $config,
> user_dir => $Features{'Path:QUARANTINEDIR'},
> debug => 'TxRep'
> };
>
> use vars qw($SASpamTester);
> $SASpamTester = Mail::SpamAssassin->new( $sa_args );
>
> And run md-mx-ctrl reread to pick up the change
>
>
>
> Since this is for a quick debug, you might find A) easier.
>
> regards,
> KAM
>
>
>
>> Can you add this block of code above line 1386 in the current TxRep.pm? Then we'll try and figure out how to enable the TxRep debug channel from MD so you can log the info and relay it. It also should hide the informat
>>
>>
>> {
>> #Bug 7164, trying to find out reason for these: _WARN: Use of uninitialized value $msgscore in addition (+) at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line 1415.
>> no warnings;
>>
>> unless (defined $msgscore) {
>> #Output some params and the calling function so we can identify more about this bug
>> dbg("TxRep: Parameters: self: $self storage: $storage pms: $pms, key: $key, id: $id, ip: $ip, signedby: $signedby, msgscore: $msgscore");
>> dbg("TxRep: weight: $weight");
>>
>> my ($package, $filename, $line) = caller();
>>
>> chomp($package);
>> chomp($filename);
>> chomp($line);
>>
>> dbg("TxRep: $msgscore undefined - Caller Info: Package: $package - Filename: $filename - Line: $line");
>>
>> #Define $msgscore as a triage to hide warnings while we find the root cause
>> $msgscore = 0;
>> }
>> }
>>
>> Here's more detail about where it needs to be:
>>
>> sub check_reputation {
>> ###########################################################################
>> my ($self, $storage, $pms, $key, $id, $ip, $signedby, $msgscore) = @_;
>>
>> my $delta = 0;
>> my $weight = ($key eq 'MSG_ID')? 1 : eval('$pms->{main}->{conf}->{txrep_weight_'.lc($key).'}');
>>
>> --> Block here
>>
>> if (defined $weight && $weight) {
>>
>> Regards,
>> KAM
>
>
Re: TxRep $msgscore warning
Posted by Mark Martinec <Ma...@ijs.si>.
> my $sa_args = {
> local_tests_only => $SALocalTestsOnly,
> dont_copy_prefs => 1,
> userprefs_filename => $config,
> user_dir => $Features{'Path:QUARANTINEDIR'},
> debug => 'TxRep'
> };
> amavisd.conf:
> $sa_debug = 1;
> Is there a way to tighten that to just show TxRep debug messages?
The:
$sa_debug = 'TxRep';
is the equivalent of the above debug=>'TxRep'.
A comma-separated list of SpamAssassin debug facilities can
be provided and is passed to the 'debug' argument of SA.
Mark
Re: TxRep $msgscore warning
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
From more discussins, there are two ways with MD to activate the TxRep
debug channel if you using spam_assassin_init in your filter.
Choice A) modify mimedefang.pl directly, i.e. spam_assassin_init to add
the debug channel:
my $sa_args = {
local_tests_only => $SALocalTestsOnly,
dont_copy_prefs => 1,
userprefs_filename => $config,
user_dir => $Features{'Path:QUARANTINEDIR'},
debug => 'TxRep'
};
And run md-mx-ctrl reread to pick up the change
or
Choice B) you can define your own SASpamTester object at the top of your
filter something like this though you'll have to define the variables
$SALocaltestsOnly, $config, and possibly $Features.
my $sa_args = {
local_tests_only => $SALocalTestsOnly,
dont_copy_prefs => 1,
userprefs_filename => $config,
user_dir => $Features{'Path:QUARANTINEDIR'},
debug => 'TxRep'
};
use vars qw($SASpamTester);
$SASpamTester = Mail::SpamAssassin->new( $sa_args );
And run md-mx-ctrl reread to pick up the change
Since this is for a quick debug, you might find A) easier.
regards,
KAM
> Can you add this block of code above line 1386 in the current
> TxRep.pm? Then we'll try and figure out how to enable the TxRep debug
> channel from MD so you can log the info and relay it. It also should
> hide the informat
>
>
> {
> #Bug 7164, trying to find out reason for these: _WARN: Use of
> uninitialized value $msgscore in addition (+) at
> /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line 1415.
> no warnings;
>
> unless (defined $msgscore) {
> #Output some params and the calling function so we can identify
> more about this bug
> dbg("TxRep: Parameters: self: $self storage: $storage pms: $pms,
> key: $key, id: $id, ip: $ip, signedby: $signedby, msgscore: $msgscore");
> dbg("TxRep: weight: $weight");
>
> my ($package, $filename, $line) = caller();
>
> chomp($package);
> chomp($filename);
> chomp($line);
>
> dbg("TxRep: $msgscore undefined - Caller Info: Package: $package
> - Filename: $filename - Line: $line");
>
> #Define $msgscore as a triage to hide warnings while we find the
> root cause
> $msgscore = 0;
> }
> }
>
> Here's more detail about where it needs to be:
>
> sub check_reputation {
> ###########################################################################
>
> my ($self, $storage, $pms, $key, $id, $ip, $signedby, $msgscore) = @_;
>
> my $delta = 0;
> my $weight = ($key eq 'MSG_ID')? 1 :
> eval('$pms->{main}->{conf}->{txrep_weight_'.lc($key).'}');
>
> --> Block here
>
> if (defined $weight && $weight) {
>
> Regards,
> KAM
Re: TxRep $msgscore warning
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 4/30/2015 11:44 AM, J.J. Day wrote:
> FWIW, I switched to TxRep several months ago. Every message generates
> both error lines. I have added a test to initialize $msgscore to avoid
> filling my log files. Spam messages seem to all generate a negative
> offset of ~1/3 the total. I copied a sample to the end.
>
> My setup is:
> FreeBSD 10.0
> Sendmail 8.14.7
> Mimedefang 2.75
> SpamAssassin 3.4.0
> Cyrus 2.4.17
>
> I hope this helps.
Interesting. So you are using the API. On your same box if you run
spamassassin -t with your sample, can you recreate the issue?
Otherwise, the sample doesn't help us because we can't recreate the
issue, unfortunately.
DFS, with MD calling SA as an API, how do you turn on a debug channel?
Happen to know?
Can you add this block of code above line 1386 in the current TxRep.pm?
Then we'll try and figure out how to enable the TxRep debug channel from
MD so you can log the info and relay it. It also should hide the informat
{
#Bug 7164, trying to find out reason for these: _WARN: Use of
uninitialized value $msgscore in addition (+) at
/usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line 1415.
no warnings;
unless (defined $msgscore) {
#Output some params and the calling function so we can identify
more about this bug
dbg("TxRep: Parameters: self: $self storage: $storage pms: $pms,
key: $key, id: $id, ip: $ip, signedby: $signedby, msgscore: $msgscore");
dbg("TxRep: weight: $weight");
my ($package, $filename, $line) = caller();
chomp($package);
chomp($filename);
chomp($line);
dbg("TxRep: $msgscore undefined - Caller Info: Package: $package
- Filename: $filename - Line: $line");
#Define $msgscore as a triage to hide warnings while we find the
root cause
$msgscore = 0;
}
}
Here's more detail about where it needs to be:
sub check_reputation {
###########################################################################
my ($self, $storage, $pms, $key, $id, $ip, $signedby, $msgscore) = @_;
my $delta = 0;
my $weight = ($key eq 'MSG_ID')? 1 :
eval('$pms->{main}->{conf}->{txrep_weight_'.lc($key).'}');
--> Block here
if (defined $weight && $weight) {
Regards,
KAM
Re: TxRep $msgscore warning
Posted by "J.J. Day" <da...@hotmail.com>.
FWIW, I switched to TxRep several months ago. Every message generates both error lines. I have added a test to initialize $msgscore to avoid filling my log files. Spam messages seem to all generate a negative offset of ~1/3 the total. I copied a sample to the end.
My setup is:
FreeBSD 10.0
Sendmail 8.14.7
Mimedefang 2.75
SpamAssassin 3.4.0
Cyrus 2.4.17
I hope this helps.
JJ Day
>> On Apr 30, 2015, at 8:36 AM, Joe Quinn <jq...@pccc.com> wrote:
>>
>>> On 4/30/2015 9:22 AM, Joe Quinn wrote:
>>>> On 4/30/2015 9:10 AM, Birta Levente wrote:
>>>>> On 30/04/2015 15:55, Joe Quinn wrote:
>>>>> On 4/30/2015 7:09 AM, Birta Levente wrote:
>>>>> Hi
>>>>>
>>>>> I saw the bug report about TxRep warning:
>>>>> _WARN: Use of uninitialized value $msgscore in addition (+) at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line 1415.
>>>>> _WARN: Use of uninitialized value $msgscore in subtraction (-)
>>>>>
>>>>>
>>>>> I just wonder if there is any workaroung for that or if exists any effect of this warning?
>>>>>
>>>>> Thanks
>>>> We know about the issue but have been having trouble reproducing it in a way we can experiment on to find where the bug is.
>>>>
>>>> Can you generate a reproduction or post samples and relevant txrep rows to this bug?
>>>> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7164
>>>
>>> I will, but only next week.
>>> What you mean in samples? Full email with body or just headers?
>> Full email would be best. It can be something contrived if it can reproduce the issue on your system. And since we're not sure what causes it, your TxRep configuration and any rows of your txrep table that match will be helpful too.
>>
>> The warning should be harmless and won't affect your mail flow in the meantime.
> Can you also include how you call spamassassin? Are you using built-in glue from a milter like MD, or spamassassin, or spamc/spamd?
Sample spam
> From: "Evgeniya" <yo...@okloksp.com.br>
> Date: April 25, 2015 at 12:07:46 AM CDT
> To: yoko@........
> Subject: Hello yoko
> Reply-To: yokorsuq@okloksp.com.br
>
> Hello yoko!!! My name is Evgeniya, to me of 25 years. I live in Russia.
> I saw your your profile and you interested me very much!
> I want to find the man of my dream.
>
> I would like to get acquainted with the person who might appreciate my care, tenderness and love.
> I want, that you would be responsible, capable to give a hand of the help and to sympathize with me in any problems.
>
> If you agree with me write to me, I shall be glad. I shall answer you soon. In my turn I shall try be the offer, loving, devoted, responsible woman.
>
> If you decide to write to me, I wait for your answer very much !!!
>
> My Email al.buloychick2015@yandex.ru
>
> Spam detection software, running on the system "........",
> has identified this incoming email as possible spam. The original
> message has been attached to this so you can view it or label
> similar future email. If you have any questions, see
> The administrator of that system for details.
>
> Content preview: Hello yoko!!! My name isEvgeniya, to me of 25 years. I live
> in Russia. I saw your your profile and you interested me very much! I want
> to find the man of my dream. I would like to get acquainted with the person
> who might appreciate my care,tenderness and love. I want, that you would
> be responsible, capable to give a hand of the help and tosympathize with me
> in any problems. [...]
>
> Content analysis details: (10.3 points, 4.7 required)
>
> pts rule name description
> ---- ---------------------- --------------------------------------------------
> 1.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
> [Blocked - see <http://www.spamcop.net/bl.shtml?115.167.70.173>]
> 1.6 RCVD_IN_BRBL_LASTEXT RBL: No description available.
> [115.167.70.173 listed in bb.barracudacentral.org]
> 0.7 RCVD_IN_XBL RBL: Received via a relay in Spamhaus XBL
> [115.167.70.173 listed in zen.spamhaus.org]
> 3.6 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL
> 1.3 RCVD_IN_RP_RNBL RBL: Relay in RNBL,
> https://senderscore.org/blacklistlookup/
> [115.167.70.173 listed in bl.score.senderscore.com]
> 2.7 RCVD_IN_PSBL RBL: Received via a relay in PSBL
> [115.167.70.173 listed in psbl.surriel.com]
> 3.0 RCVD_IN_MSPIKE_L5 RBL: Very bad reputation (-5)
> [115.167.70.173 listed in bl.mailspike.net]
> 0.0 HTML_MESSAGE BODY: HTML included in message
> 0.0 RCVD_IN_MSPIKE_BL Mailspike blacklisted
> 1.3 RDNS_NONE Delivered to internal network by a host with no rDNS
> 0.0 HELO_MISC_IP Looking for more Dynamic IP Relays
> -5.2 TXREP TXREP: Score normalizing based on sender's reputation
>
>
Re: TxRep $msgscore warning
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 5/4/2015 10:12 AM, Birta Levente wrote:
> I see messages in the log by the added code in TxRep.pm with:
>
> amavisd.conf:
> $sa_debug = 1;
Is there a way to tighten that to just show TxRep debug messages?
Regards,
KAM
Re: TxRep $msgscore warning
Posted by Birta Levente <bl...@gmail.com>.
On 04/05/2015 16:51, Kevin A. McGrail wrote:
> On 5/4/2015 9:03 AM, Birta Levente wrote:
>> On 30/04/2015 18:08, Kevin A. McGrail wrote:
>>> On 4/30/2015 9:56 AM, Birta Levente wrote:
>>>> Spamassassin called through amavisd as a content filter in postfix.
>>>>
>>>> I just see, if I send an emtpy mail (just the subject is "test")
>>>> through my server, fire the warning.
>>>> The mail is sent as an authenticated user, in amavis I have special
>>>> policy bank for authenticated users.
>>>> But the warnings I saw when mails coming from outside too.
>>>>
>>> OK, well that error means msgscore isn't defined in check_reputation
>>> and there is at least one call to that function without a message
>>> score such as this call with only 6 parameters (msgscore is #8)
>>>
>>> my $msg_rep = $self->check_reputations($pms, 'MSG_ID', $msg_id,
>>> undef, $date, undef);
>>>
>>> Overall, I checked and we use spamc/spamd and have never seen the
>>> scenario you are having.
>>>
>>> My thoughts are to have you edit your TxRep.pm, restart amavisd and
>>> look at the logs for the next time it happens and give us the log
>>> out from the dbg and the errors.
>>>
>>> Not sure how you turn on debugging with amavis so hoping someone on
>>> list can say how to turn on --debug=TxRep so we can log the TxRep
>>> log issues?
>>>
>>> Can you add this block of code above line 1386 in the current TxRep.pm?
>>>
>>> {
>>> #Bug 7164, trying to find out reason for these: _WARN: Use of
>>> uninitialized value $msgscore in addition (+) at
>>> /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line
>>> 1415.
>>> no warnings;
>>>
>>> dbg("TxRep: Parameters: self: $self storage: $storage pms: $pms,
>>> key: $key, id: $id, ip: $ip, signedby: $signedby, msgscore:
>>> $msgscore");
>>> dbg("TxRep: weight: $weight");
>>> }
>>>
>>>
>>> Here's more detail about where it needs to be:
>>>
>>> sub check_reputation {
>>> ###########################################################################
>>>
>>> my ($self, $storage, $pms, $key, $id, $ip, $signedby, $msgscore) =
>>> @_;
>>>
>>> my $delta = 0;
>>> my $weight = ($key eq 'MSG_ID')? 1 :
>>> eval('$pms->{main}->{conf}->{txrep_weight_'.lc($key).'}');
>>>
>>> --> Block here
>>>
>>> if (defined $weight && $weight) {
>>>
>>>
>>> regards,
>>> KAM
>>
>> I added the above, installed the final 3.4.1 today, 6-7 hours ago.
>> Make sa-update, sa-compile, restart amavis and the warning
>> disappearedso far.
>> IIRC when I updated to 3.4.1. rc2 I do only amavis reload. Could be
>> this the problem? Or changed something in the final version?
> No, it's an issue that's been known without the ability to replicate.
> I don't think we've found it and it's just hiding again.
>
>> I was without internet in a past few days, so if I missed something
>> or could be/need to do something please let me know.
>
> If you are having the $msgscore issue, please edit txrep.pm to modify
> check_reputation (see below) AND figure out how to turn on
> --debug="TxRep" in your amavisd setup. Even if you can't turn on the
> debug, this should hide the issue (not ideal)...
>
> Mark, I've never been able to recreate the issue but it appears to
> only show up in the API interface. How can we turn on the TxRep debug
> channel in Amavisd?
>
>
I see messages in the log by the added code in TxRep.pm with:
amavisd.conf:
$sa_debug = 1;
--
Levi
Re: TxRep $msgscore warning
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 5/4/2015 9:03 AM, Birta Levente wrote:
> On 30/04/2015 18:08, Kevin A. McGrail wrote:
>> On 4/30/2015 9:56 AM, Birta Levente wrote:
>>> Spamassassin called through amavisd as a content filter in postfix.
>>>
>>> I just see, if I send an emtpy mail (just the subject is "test")
>>> through my server, fire the warning.
>>> The mail is sent as an authenticated user, in amavis I have special
>>> policy bank for authenticated users.
>>> But the warnings I saw when mails coming from outside too.
>>>
>> OK, well that error means msgscore isn't defined in check_reputation
>> and there is at least one call to that function without a message
>> score such as this call with only 6 parameters (msgscore is #8)
>>
>> my $msg_rep = $self->check_reputations($pms, 'MSG_ID', $msg_id,
>> undef, $date, undef);
>>
>> Overall, I checked and we use spamc/spamd and have never seen the
>> scenario you are having.
>>
>> My thoughts are to have you edit your TxRep.pm, restart amavisd and
>> look at the logs for the next time it happens and give us the log out
>> from the dbg and the errors.
>>
>> Not sure how you turn on debugging with amavis so hoping someone on
>> list can say how to turn on --debug=TxRep so we can log the TxRep log
>> issues?
>>
>> Can you add this block of code above line 1386 in the current TxRep.pm?
>>
>> {
>> #Bug 7164, trying to find out reason for these: _WARN: Use of
>> uninitialized value $msgscore in addition (+) at
>> /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line
>> 1415.
>> no warnings;
>>
>> dbg("TxRep: Parameters: self: $self storage: $storage pms: $pms,
>> key: $key, id: $id, ip: $ip, signedby: $signedby, msgscore: $msgscore");
>> dbg("TxRep: weight: $weight");
>> }
>>
>>
>> Here's more detail about where it needs to be:
>>
>> sub check_reputation {
>> ###########################################################################
>>
>> my ($self, $storage, $pms, $key, $id, $ip, $signedby, $msgscore) = @_;
>>
>> my $delta = 0;
>> my $weight = ($key eq 'MSG_ID')? 1 :
>> eval('$pms->{main}->{conf}->{txrep_weight_'.lc($key).'}');
>>
>> --> Block here
>>
>> if (defined $weight && $weight) {
>>
>>
>> regards,
>> KAM
>
> I added the above, installed the final 3.4.1 today, 6-7 hours ago.
> Make sa-update, sa-compile, restart amavis and the warning
> disappearedso far.
> IIRC when I updated to 3.4.1. rc2 I do only amavis reload. Could be
> this the problem? Or changed something in the final version?
No, it's an issue that's been known without the ability to replicate. I
don't think we've found it and it's just hiding again.
> I was without internet in a past few days, so if I missed something or
> could be/need to do something please let me know.
If you are having the $msgscore issue, please edit txrep.pm to modify
check_reputation (see below) AND figure out how to turn on
--debug="TxRep" in your amavisd setup. Even if you can't turn on the
debug, this should hide the issue (not ideal)...
Mark, I've never been able to recreate the issue but it appears to only
show up in the API interface. How can we turn on the TxRep debug
channel in Amavisd?
Regards,
KAM
{
#Bug 7164, trying to find out reason for these: _WARN: Use of
uninitialized value $msgscore in addition (+) at
/usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line 1415.
no warnings;
unless (defined $msgscore) {
#Output some params and the calling function so we can identify
more about this bug
dbg("TxRep: Parameters: self: $self storage: $storage pms: $pms,
key: $key, id: $id, ip: $ip, signedby: $signedby, msgscore: $msgscore");
dbg("TxRep: weight: $weight");
my ($package, $filename, $line) = caller();
chomp($package);
chomp($filename);
chomp($line);
dbg("TxRep: $msgscore undefined - Caller Info: Package: $package
- Filename: $filename - Line: $line");
#Define $msgscore as a triage to hide warnings while we find the
root cause
$msgscore = 0;
}
}
Here's more detail about where it needs to be:
sub check_reputation {
###########################################################################
my ($self, $storage, $pms, $key, $id, $ip, $signedby, $msgscore) = @_;
my $delta = 0;
my $weight = ($key eq 'MSG_ID')? 1 :
eval('$pms->{main}->{conf}->{txrep_weight_'.lc($key).'}');
--> Block here
if (defined $weight && $weight) {
Re: TxRep $msgscore warning
Posted by Birta Levente <bl...@gmail.com>.
On 30/04/2015 18:08, Kevin A. McGrail wrote:
> On 4/30/2015 9:56 AM, Birta Levente wrote:
>> Spamassassin called through amavisd as a content filter in postfix.
>>
>> I just see, if I send an emtpy mail (just the subject is "test")
>> through my server, fire the warning.
>> The mail is sent as an authenticated user, in amavis I have special
>> policy bank for authenticated users.
>> But the warnings I saw when mails coming from outside too.
>>
> OK, well that error means msgscore isn't defined in check_reputation
> and there is at least one call to that function without a message
> score such as this call with only 6 parameters (msgscore is #8)
>
> my $msg_rep = $self->check_reputations($pms, 'MSG_ID', $msg_id, undef,
> $date, undef);
>
> Overall, I checked and we use spamc/spamd and have never seen the
> scenario you are having.
>
> My thoughts are to have you edit your TxRep.pm, restart amavisd and
> look at the logs for the next time it happens and give us the log out
> from the dbg and the errors.
>
> Not sure how you turn on debugging with amavis so hoping someone on
> list can say how to turn on --debug=TxRep so we can log the TxRep log
> issues?
>
> Can you add this block of code above line 1386 in the current TxRep.pm?
>
> {
> #Bug 7164, trying to find out reason for these: _WARN: Use of
> uninitialized value $msgscore in addition (+) at
> /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line 1415.
> no warnings;
>
> dbg("TxRep: Parameters: self: $self storage: $storage pms: $pms,
> key: $key, id: $id, ip: $ip, signedby: $signedby, msgscore: $msgscore");
> dbg("TxRep: weight: $weight");
> }
>
>
> Here's more detail about where it needs to be:
>
> sub check_reputation {
> ###########################################################################
>
> my ($self, $storage, $pms, $key, $id, $ip, $signedby, $msgscore) = @_;
>
> my $delta = 0;
> my $weight = ($key eq 'MSG_ID')? 1 :
> eval('$pms->{main}->{conf}->{txrep_weight_'.lc($key).'}');
>
> --> Block here
>
> if (defined $weight && $weight) {
>
>
> regards,
> KAM
I added the above, installed the final 3.4.1 today, 6-7 hours ago.
Make sa-update, sa-compile, restart amavis and the warning disappearedso
far.
IIRC when I updated to 3.4.1. rc2 I do only amavis reload. Could be this
the problem? Or changed something in the final version?
I was without internet in a past few days, so if I missed something or
could be/need to do something please let me know.
Thanks
--
Levi
Re: TxRep $msgscore warning
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 4/30/2015 9:56 AM, Birta Levente wrote:
> Spamassassin called through amavisd as a content filter in postfix.
>
> I just see, if I send an emtpy mail (just the subject is "test")
> through my server, fire the warning.
> The mail is sent as an authenticated user, in amavis I have special
> policy bank for authenticated users.
> But the warnings I saw when mails coming from outside too.
>
OK, well that error means msgscore isn't defined in check_reputation and
there is at least one call to that function without a message score such
as this call with only 6 parameters (msgscore is #8)
my $msg_rep = $self->check_reputations($pms, 'MSG_ID', $msg_id, undef,
$date, undef);
Overall, I checked and we use spamc/spamd and have never seen the
scenario you are having.
My thoughts are to have you edit your TxRep.pm, restart amavisd and look
at the logs for the next time it happens and give us the log out from
the dbg and the errors.
Not sure how you turn on debugging with amavis so hoping someone on list
can say how to turn on --debug=TxRep so we can log the TxRep log issues?
Can you add this block of code above line 1386 in the current TxRep.pm?
{
#Bug 7164, trying to find out reason for these: _WARN: Use of
uninitialized value $msgscore in addition (+) at
/usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line 1415.
no warnings;
dbg("TxRep: Parameters: self: $self storage: $storage pms: $pms,
key: $key, id: $id, ip: $ip, signedby: $signedby, msgscore: $msgscore");
dbg("TxRep: weight: $weight");
}
Here's more detail about where it needs to be:
sub check_reputation {
###########################################################################
my ($self, $storage, $pms, $key, $id, $ip, $signedby, $msgscore) = @_;
my $delta = 0;
my $weight = ($key eq 'MSG_ID')? 1 :
eval('$pms->{main}->{conf}->{txrep_weight_'.lc($key).'}');
--> Block here
if (defined $weight && $weight) {
regards,
KAM
Re: TxRep $msgscore warning
Posted by Birta Levente <bl...@gmail.com>.
On 30/04/2015 16:35, Joe Quinn wrote:
> On 4/30/2015 9:22 AM, Joe Quinn wrote:
>> On 4/30/2015 9:10 AM, Birta Levente wrote:
>>> On 30/04/2015 15:55, Joe Quinn wrote:
>>>> On 4/30/2015 7:09 AM, Birta Levente wrote:
>>>>> Hi
>>>>>
>>>>> I saw the bug report about TxRep warning:
>>>>> _WARN: Use of uninitialized value $msgscore in addition (+) at
>>>>> /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm
>>>>> line 1415.
>>>>> _WARN: Use of uninitialized value $msgscore in subtraction (-)
>>>>>
>>>>>
>>>>> I just wonder if there is any workaroung for that or if exists any
>>>>> effect of this warning?
>>>>>
>>>>> Thanks
>>>>>
>>>> We know about the issue but have been having trouble reproducing it
>>>> in a way we can experiment on to find where the bug is.
>>>>
>>>> Can you generate a reproduction or post samples and relevant txrep
>>>> rows to this bug?
>>>> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7164
>>>
>>> I will, but only next week.
>>> What you mean in samples? Full email with body or just headers?
>>>
>> Full email would be best. It can be something contrived if it can
>> reproduce the issue on your system. And since we're not sure what
>> causes it, your TxRep configuration and any rows of your txrep table
>> that match will be helpful too.
>>
>> The warning should be harmless and won't affect your mail flow in the
>> meantime.
> Can you also include how you call spamassassin? Are you using built-in
> glue from a milter like MD, or spamassassin, or spamc/spamd?
Spamassassin called through amavisd as a content filter in postfix.
I just see, if I send an emtpy mail (just the subject is "test") through
my server, fire the warning.
The mail is sent as an authenticated user, in amavis I have special
policy bank for authenticated users.
But the warnings I saw when mails coming from outside too.
--
Levi
Re: TxRep $msgscore warning
Posted by Joe Quinn <jq...@pccc.com>.
On 4/30/2015 9:22 AM, Joe Quinn wrote:
> On 4/30/2015 9:10 AM, Birta Levente wrote:
>> On 30/04/2015 15:55, Joe Quinn wrote:
>>> On 4/30/2015 7:09 AM, Birta Levente wrote:
>>>> Hi
>>>>
>>>> I saw the bug report about TxRep warning:
>>>> _WARN: Use of uninitialized value $msgscore in addition (+) at
>>>> /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line
>>>> 1415.
>>>> _WARN: Use of uninitialized value $msgscore in subtraction (-)
>>>>
>>>>
>>>> I just wonder if there is any workaroung for that or if exists any
>>>> effect of this warning?
>>>>
>>>> Thanks
>>>>
>>> We know about the issue but have been having trouble reproducing it
>>> in a way we can experiment on to find where the bug is.
>>>
>>> Can you generate a reproduction or post samples and relevant txrep
>>> rows to this bug?
>>> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7164
>>
>> I will, but only next week.
>> What you mean in samples? Full email with body or just headers?
>>
> Full email would be best. It can be something contrived if it can
> reproduce the issue on your system. And since we're not sure what
> causes it, your TxRep configuration and any rows of your txrep table
> that match will be helpful too.
>
> The warning should be harmless and won't affect your mail flow in the
> meantime.
Can you also include how you call spamassassin? Are you using built-in
glue from a milter like MD, or spamassassin, or spamc/spamd?
Re: TxRep $msgscore warning
Posted by Joe Quinn <jq...@pccc.com>.
On 4/30/2015 9:10 AM, Birta Levente wrote:
> On 30/04/2015 15:55, Joe Quinn wrote:
>> On 4/30/2015 7:09 AM, Birta Levente wrote:
>>> Hi
>>>
>>> I saw the bug report about TxRep warning:
>>> _WARN: Use of uninitialized value $msgscore in addition (+) at
>>> /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line
>>> 1415.
>>> _WARN: Use of uninitialized value $msgscore in subtraction (-)
>>>
>>>
>>> I just wonder if there is any workaroung for that or if exists any
>>> effect of this warning?
>>>
>>> Thanks
>>>
>> We know about the issue but have been having trouble reproducing it
>> in a way we can experiment on to find where the bug is.
>>
>> Can you generate a reproduction or post samples and relevant txrep
>> rows to this bug?
>> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7164
>
> I will, but only next week.
> What you mean in samples? Full email with body or just headers?
>
Full email would be best. It can be something contrived if it can
reproduce the issue on your system. And since we're not sure what causes
it, your TxRep configuration and any rows of your txrep table that match
will be helpful too.
The warning should be harmless and won't affect your mail flow in the
meantime.
Re: TxRep $msgscore warning
Posted by Birta Levente <bl...@gmail.com>.
On 30/04/2015 15:55, Joe Quinn wrote:
> On 4/30/2015 7:09 AM, Birta Levente wrote:
>> Hi
>>
>> I saw the bug report about TxRep warning:
>> _WARN: Use of uninitialized value $msgscore in addition (+) at
>> /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line
>> 1415.
>> _WARN: Use of uninitialized value $msgscore in subtraction (-)
>>
>>
>> I just wonder if there is any workaroung for that or if exists any
>> effect of this warning?
>>
>> Thanks
>>
> We know about the issue but have been having trouble reproducing it in
> a way we can experiment on to find where the bug is.
>
> Can you generate a reproduction or post samples and relevant txrep
> rows to this bug?
> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7164
I will, but only next week.
What you mean in samples? Full email with body or just headers?
--
Levi
Re: TxRep $msgscore warning
Posted by Joe Quinn <jq...@pccc.com>.
On 4/30/2015 7:09 AM, Birta Levente wrote:
> Hi
>
> I saw the bug report about TxRep warning:
> _WARN: Use of uninitialized value $msgscore in addition (+) at
> /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/TxRep.pm line 1415.
> _WARN: Use of uninitialized value $msgscore in subtraction (-)
>
>
> I just wonder if there is any workaroung for that or if exists any
> effect of this warning?
>
> Thanks
>
We know about the issue but have been having trouble reproducing it in a
way we can experiment on to find where the bug is.
Can you generate a reproduction or post samples and relevant txrep rows
to this bug?
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7164