On Thu, 2006-11-02 at 20:44 -0700, Gary V wrote:
> Hans wrote:
> > mail:/etc/amavis/conf.d# grep sa_spam_report_header *
> > 30-user:#$sa_spam_report_header = 0; # insert X-Spam-Report header
> > field? default false
> > 30-user:$sa_spam_report_header = 1;
> 
> 
> > In /var/lib/amavis/.spamassassin/user_prefs I have:
> 
> > report_header 1
>
> This detailed report is only applied to messages at or above tag2
> level. There is a way to also apply it to messages that score below
> tag2, but it requires a hack:
> 
> http://marc.theaimsgroup.com/?l=amavis-user&m=113985038223442
> 
> I have to make the assumption you are not confusing this verbose
> report with the typical X-Spam type headers that are written when spam
> scores above tag level and the recipient is local. BTW, if you have just
> installed the Debian version of amavisd-new, spamassassin is disabled
> by default. See 15-content_filter_mode.

I have enabled  spam and virus scanning in 15-content_filter_mode -
wasted a lot of time bumping my head before I discovered that - I really
prefer the single file setup....

I'm looking for this:

X-Spam-Status: No, hits=-2.545 tagged_above=-2200 required=4
tests=BAYES_00, DSPAM_HAM, MIME_BOUND_NEXTPART, MIME_SUSPECT_NAME,
MSGID_FROM_MTA_HEADER

For almost a year now, I've run greylisting and some RBL checks in
postfix only, and only yesterday did the first spam (one of these gif
ones) come through.  At this time I don't want any action to be taken by
amavisd-new, just to tag it and give me thorough information on why it
thinks the mail is spam or not.

I have this in my dconfig:

# default values, customarily used in the @spam_*_level_maps as the last
entry
$sa_tag_level_deflt = -100;   # add spam info headers if at, or above
that level;
                   undef is interpreted as lower than any spam level
$sa_tag2_level_deflt = 6.31;  # add 'spam detected' headers at that
level to
                  # passed mail (e.g. when $final_spam_destiny=D_PASS
                  # or for spam_lovers or when below kill_level)
$sa_kill_level_deflt = 100; # triggers spam evasive actions
                         # at or above that level: bounce/reject/drop,
                         # quarantine, and adding mail address extension
$sa_dsn_cutoff_level = 150;  # spam level beyond which a DSN is not
sent,
               # effectively turning D_BOUNCE into D_DISCARD;
               # undef disables this feature and is a default;

I thought $sa_tag_level_deflt will just give me the output of
spamassassin, regardless of the outcome? The "add spam info headers if
at" bit.

Thanks
Hans

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to