OSEC

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 (postfixchrlx.com)
Date: Tue Jun 03 2003 - 21:12:36 CDT


I was going to suggest the same for getting headers into all mail.
However, i cannot figure out why they don't work on one of my domains
configured in mydestination of the main.cf file.
I set up Postfix with Amavisd and SA about 6 weeks ago, its extremely
stable and i'm very happy with it. I use it as a mail gateway, just to
filter spam.

I myself am still trying to figure out exactly how and in what sequence
are the different rules and configurations read and interpreted. I can't
figure out why my whitelists ( in local.cf) are not being honoured ?

What versions of each are you running ?

-Maciek

Robin Lynn Frank wrote:

>On Tuesday 03 June 2003 13:35, Noel Jones wrote:
>
>
>
>>>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 **
>>
>>
>
>Duh! And they told me over on the amavis list it couldn't be done. Thank
>you, thank you, thank you!!!
>
>