Re: Amavis how to handle?

MrC wrote:
> 
> 
> 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
>>
>>
> 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

I was afraid of something like that. Thanks for clearing it up.

-Mike