|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: +/- of using amavisd-new to integrate SpamAssassin w/Postfix
From: MJM (postfix
chrlx.com)
Date: Tue Jun 03 2003 - 21:07:17 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
its the TAG2 value that changes the subject, correct ? for all domains
in $mydestination?
why are the values from the spamassassin/local.cf not read , rather
amavisd takes priority ?
i have : postfix - amavisdnew - sa on rh linux
-Maciek
Noel Jones wrote:
> At 01:20 PM 6/3/03 -0700, Robin Lynn Frank wrote:
>
>> > It is *not* pointless. It is incredibly fast, and quite flexible.
>> >
>> > However, for this small load, perhaps it is more than they need.
>>
>> We have similar load figures in each of our offices, but the way
>> amavisd-new
>> archives spam makes it our favorite means of implementing
>> spamassasin, and
>> while we also use it for our antivirus apps, we still find it the
>> fastest way
>> to go. The only down side is not having the spamassassin headers in
>> levels
>> below the trigger point.
>
>
>
> Which of course is configurable in amavisd-new by setting the
> $sa_tag_level_deflt to a low value, such as "-999". This adds the
> X-Spam-Status and X-Spam-Level headers without actually marking the
> message as ** SPAM **
>
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]