Dave,
> I'm not talking about the addition of
> headers to messages, I'm talking about the logging (to syslog,
> in my case) of each message as amavisd processes it.
The list of SpamAssassin test names which triggered
is available in macro %T, which can be added to a logging
template (or to notif
Dave McGuire wrote:
> On Dec 6, 2007, at 12:39 PM, MrC wrote:
>>>Hey folks. It looks to me like amavisd-new isn't logging the
>>> SpamAssassin rules summary for messages that *don't* get tagged
>>> as spam. I can't believe I've never noticed this before, but
>>> sitting here staring
On Dec 6, 2007, at 12:39 PM, MrC wrote:
>>Hey folks. It looks to me like amavisd-new isn't logging the
>> SpamAssassin rules summary for messages that *don't* get tagged
>> as spam. I can't believe I've never noticed this before, but
>> sitting here staring at a log file, this seems
Dave McGuire wrote:
>Hey folks. It looks to me like amavisd-new isn't logging the
> SpamAssassin rules summary for messages that *don't* get tagged as
> spam. I can't believe I've never noticed this before, but sitting
> here staring at a log file, this seems to be the case.
>
Lower th
Hey folks. It looks to me like amavisd-new isn't logging the
SpamAssassin rules summary for messages that *don't* get tagged as
spam. I can't believe I've never noticed this before, but sitting
here staring at a log file, this seems to be the case.
Basically I have a spam message th
