[Logwatch-Devel] amavis spam assassin timeout handling recommendation

Who Knows quien-sabe at metaorg.com
Wed Dec 7 07:22:34 MST 2005


*A spam assassin timeout message really addes lots of "garbage" in my opinion to the report with
its backtrace. This patch will mask the unknown message and provide count of timeouts.
Anyone wanting to troubleshoot the timeouts can easily grep the backtraces out of the log.

--- logwatch/scripts/services/amavis  2005-11-16 19:00:31.000000000 -0700*
*+++ logwatch/scripts/services/amavis  2005-12-07 06:13:10.000000000 -0700*
@@ -25,6 +25,7 @@
 $NoQuarantine = 0;
 $Whitelisted = 0;
 $Blacklisted = 0;
+$SATimedout  = 0;

 # Parse logfile
 while (defined($ThisLine = <STDIN>)) {
@@ -179,6 +180,8 @@
       $BadHeaders++;
       $InfectedMsgs++;
       $BannedNames++;
+   } elsif ( $ThisLine =~ /^SA TIMED OUT,/ ) {
+      $SATimedout++;
    } elsif (($ThisLine =~ /^white_black_list: whitelisted sender/ )
      or ( $ThisLine =~ /.* WHITELISTED/) ) {
      $Whitelisted++;
@@ -228,6 +231,10 @@
    print "$NoQuarantine messages destined for quarantine intentially not quarantined (spam level exceeds quarantine cutoff level).\n";
 };

+if($SATimedout > 0) {
+   print "$SATimedout messages caused SpamAssassin to timeout during message processing.\n";
+};
+
 if ($Whitelisted > 0 && $Detail >= 5) {
    print "$Whitelisted messages were whitelisted.\n";
 };



More information about the Logwatch-Devel mailing list