Re: Amavis how to handle?

Mike Tremaine wrote:
> I'm getting an unmatched entry for every email. List so
> 
> May 12 11:44:32 kraken amavis[6728]: (06728-17) Passed, 
> <[email protected]> -> <[email protected]>, quarantine 2Q2nUslMB2Fz, 
> Message-ID: 
> <[email protected]>, Hits: -2.106
> May 12 11:44:32 kraken amavis[6728]: (06728-17) Passed CLEAN, 
> <[email protected]> -> <[email protected]>, Hits: -2.106, tag=4, tag2=6.3, 
> kill=6.3, L/0/0/0
> 
> 
> The first log line is unmatched the second is. But I think that it is 
> just extra info I do not think it needs to be counted. This patch seems 
> to tack care of it
> 
> [mgt@dwarfstar services]$ cvs diff amavis
> Index: amavis
> ===================================================================
> RCS file: /var/cvs/logwatch/scripts/services/amavis,v
> retrieving revision 1.54
> diff -r1.54 amavis
> 565a566
>  >         or ($p1 =~ /^(Passed|Blocked),.*Hits: ([-+.\d]+)$/)
> 
> 
> But since I do not have much experience with amavis I wanted to check 
> before I commit this.
> 

Mike,

This isn't the correct change unfortunately.

The problem is that the user has enabled additional per-user log 
entries, but has not disabled the original, generic log entry, so there 
are duplicate entries.

This change will ignore log lines from older amavis versions, or for 
those users using per-user log entries.

I recently responded to a user's question about this same question:

----
It is advised to disable the per-message entry when you enable 
per-recipient entries.  From amavis' Release Notes:

- added $log_recip_templ variable, which is similar to $log_templ,
   but gets called for every recipient (the $log_templ is evaluated
   only once per message). Normally one or the other log template should
   be disabled by assigning undef or an empty string to the corresponding
   variable;

Mike