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
