<div class="gmail_quote">On Tue, Jun 9, 2009 at 3:33 AM, Scott Silva <span dir="ltr"><<a href="mailto:ssilva@sgvwater.com">ssilva@sgvwater.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
on 6-8-2009 12:54 AM Zaeem Arshad spake the following:<br>
<div><div></div><div class="h5">><br>
><br>
><br>
> Zaeem<br>
><br>
> The SpamAssassin Cache does part of this - keeps a hash of the emails<br>
> and scores for a short period, and doesn't scan the email again if it<br>
> matched the hash.<br>
><br>
><br>
> Yups. That's good!<br>
><br>
><br>
><br>
> For the storage (or rather not storing) if it hits the SpamAssassin<br>
> cache, interesting idea - what do other people think? Depends what you<br>
> do with the spam/highscoring spam first, not everyone stores the email<br>
> in the first place.<br>
><br>
><br>
> Or maybe, only store spam based on specific score ranges. It seems I<br>
> will have to write a perl custom function to handle that. Thanks anyway.<br>
><br>
</div></div>You can already do that now. I have the following in my Mailscanner.conf;<br>
SpamAssassin Rule Actions = SpamScore>25=>not-store<br>
<br>
That way spam that scores over 25 isn't stored. You could do a lot of<br>
different things. Spam that scores a certain range but didn't hit bayes_99<br>
could be sent to a different box for spam training. The rule actions stuff can<br>
do many amazing things!<br>
<br>
<br></blockquote></div>Sweet! Will try.<br><br><br>Regards<br><br>--<br>Zaeem<br>