> So, as I understand it, there is no way to get a detailed report with
> amavisd-new for a "non-spam" mail.
>
> Al
>
>
why would you need such thing? you're not going to convert all your mail
into reports, would you?
If you need it for a given email, then just run spamassassin -t on that
mail (and if using Bayes, run this as the amavis user. see Gary's su
vscan -c ... example).
Al, can I assume you want to do this so you can debug and analyze how well
your system is working? If so, you can lower the spam threshold so you can
see these verbose reports. You can do this just for yourself by adding a
@spam_tag2_level_maps.
This example is modified from amavisd.conf-sample:
@spam_tag2_level_maps = (
{ '[EMAIL PROTECTED]' => -10.0, },
\$sa_tag2_level_deflt, # catchall default
);
Now anything that gets delivered to you that scores at -10.0 or higher will
be tagged as spam.
As long as you are not using procmail to dump your mail based on the
'X-Spam-Flag: YES' header, you will still get your mail, and you will get
your verbose report. If you don't want ***SPAM*** prefixed to your subject
line, you can turn that off for you too.
@spam_modifies_subj_maps = ( [qw( [EMAIL PROTECTED] . )] );
Then of course simply read the score in the header to determine if it would
have been tagged as spam if you were using the setting you would normally
use for $sa_tag2_level_deflt.
Gary V
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
