Mail Scanner and Spam Assassin report generation

[brichter]

In MY situation being able to not feed the message back into the Bayes
engine is NOT an issue.

We would ONLY be turning on Spam report generation in the body for any NON
HIGH SCORING spam. High Scoring Spam would still be an immidiate DELETE.
We only would turn it on when we adjust Spam Scoring. (Old default score
for SPAM becomes High Scoring level) Like in my example, 7.0 is now
considered High Scoring DELETE right away.  5.0 becomes new score to be
SPAM (not high scoring) so the 5.0-6.99 would get delivered for a few
weeks (which meanwhile we would take feedback from users on false
positives)
So after a 3 week period we would go back to DELETE for SPAM
and DELETE for HIGH SCORING SPAM.

It's only a feature we would use ocassionaly here.  But very valuable..

Thanks for EVERYONE's help!



On Mon, 29 Mar 2004, Julian Field wrote:
>
> But if you put the report in the message then you can't feed it back into
> the Bayes engine in SpamAssassin. Do you really want that? You won't be
> able to manually teach SpamAssassin about any messages as you will have
> changed the message a lot.
>
> If you really are happy with that, let me know.
> --
> Julian Field
> www.MailScanner.info
> MailScanner thanks transtec Computers for their support
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
>