"report_safe" does not work

[Helmut Schneider <ju...@gmx.de>]

Hi,

I use amavisd-new 2.52 and SA3.21 chroot'ed.

[root@BSDHelmut ~]# grep -ir report_safe 
/var/amavis/usr/local/etc/mail/spamassassin/local.cf
# report_safe 1
report_safe 2
[root@BSDHelmut ~]# spamassassin --lint -d
[...]
[15632] dbg: config: read file /usr/local/etc/mail/spamassassin/local.cf
[...]
[root@BSDHelmut ~]#

I do not use any user_prefs.

Nevertheless the email is delivered unchanged to my inbox. It is tagged so 
SA seems to work.
Is there a setting that only mail with a hit greater than X is modified? Or 
did I miss anything else?

Thanks, Helmut 

Re: "report_safe" does not work

[Helmut Schneider <ju...@gmx.de>]

From: "Wolfgang Zeikat" <wo...@desy.de>

> On 07/12/07 15:47, Helmut Schneider wrote:
>> Hi,
>> I use amavisd-new 2.52 and SA3.21 chroot'ed.
>> Is there a setting that only mail with a hit greater than X is modified? 
>> Or did I miss anything else?
> AFAIK, amavisd-new has it's own ways of using SA, and that includes 
> ignoring some local.cf options. You can try and put them into the amavisd 
> config file with something like
> $sa_report_safe = 1;
> I don't have amavisd-new installed, but learned lately that the $sa_* way 
> works with some options, see the sample / default cf files in the 
> documentation.


$defang_spam

> HTH,

Yes.

Thanks, Helmut 

Re: "report_safe" does not work

[Wolfgang Zeikat <wo...@desy.de>]

Hi,

On 07/12/07 15:47, Helmut Schneider wrote:
> Hi,
> 
> I use amavisd-new 2.52 and SA3.21 chroot'ed.
> 

> Is there a setting that only mail with a hit greater than X is modified? 
> Or did I miss anything else?

AFAIK, amavisd-new has it's own ways of using SA, and that includes 
ignoring some local.cf options. You can try and put them into the 
amavisd config file with something like

$sa_report_safe = 1;

I don't have amavisd-new installed, but learned lately that the $sa_* 
way works with some options, see the sample / default cf files in the 
documentation.

HTH,

wolfgang