Your message dated Wed, 06 Jan 2010 18:37:01 +0100
with message-id <[email protected]>
and subject line Re: mailgraph- no spam stats with amavisd-new and spamassassin 
again
has caused the Debian Bug report #418740,
regarding no spam stats with amavisd-new and spamassassin again
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
418740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418740
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mailgraph
Version: 1.12-2.1
Severity: normal
Tags: patch

No way to make mailgraph to see spam again (in etch too).
In mail.log I see SPAMMY now and not SPAM.

I think this patch is enough.

--- mailgraph~  2007-04-11 18:43:23.000000000 +0200
+++ mailgraph   2007-04-11 18:43:23.000000000 +0200
@@ -595,7 +595,7 @@
                }
        }
        elsif($prog eq 'amavis' || $prog eq 'amavisd') {
-               if(   $text =~ /^\([0-9-]+\) (Passed|Blocked) SPAM\b/) {
+               if(   $text =~ /^\([0-9-]+\) (Passed|Blocked) SPAM|SPAMMY\b/) {
                        event($time, 'spam'); # since amavisd-new-2004xxxx
                }
                elsif($text =~ /^\([0-9-]+\)
                (Passed|Not-Delivered)\b.*\bquarantine spam/) {


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)


--- End Message ---
--- Begin Message ---
Package: mailgraph
Version: 1.13-1
Followup-For: Bug #417840

> No way to make mailgraph to see spam again (in etch too).
> In mail.log I see SPAMMY now and not SPAM.
> 
> I think this patch is enough.
[...]

This issue was fixed by mailgraph 1.13, hence closing this bug

Cheers,
Julien




--- End Message ---

Reply via email to