<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>Greylist</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Hi all,</FONT>
</P>
<P><FONT SIZE=2>I was wondering if anyone else would benefit from a feature that would add a greylist option to automatically consider matching messages as low scoring spam. This would effectively eliminate the "Definite Spam Is High Scoring" because you would have a blacklist option that would automatically treat matching messages as high scoring spam. </FONT></P>
<P><FONT SIZE=2>To keep consistent with the current config, you could change (from my config):</FONT>
</P>
<P><FONT SIZE=2>Is Definitely Not Spam = %rules-dir%/spam.whitelist.rules</FONT>
<BR><FONT SIZE=2>Is Definitely Spam = %rules-dir%/spam.greylist.rules</FONT>
<BR><FONT SIZE=2>Definite Spam Is High Scoring = %rules-dir%/spam.blacklist.rules</FONT>
</P>
<P><FONT SIZE=2>To:</FONT>
</P>
<P><FONT SIZE=2>Is Definitely Not Spam = %rules-dir%/spam.whitelist.rules</FONT>
<BR><FONT SIZE=2>Is Definitely Spam = %rules-dir%/spam.greylist.rules</FONT>
<BR><FONT SIZE=2>Is Definitely High Scoring Spam = %rules-dir%/spam.blacklist.rules</FONT>
</P>
<P><FONT SIZE=2>This seems more logical to me. I can emulate this by including a ruleset in Definite Spam Is High Scoring but that means it has to match both the greylist.rules and the blacklist.rules files for it to be considered high scoring spam. My greylist rules (formerly blacklist.rules) is something like 70K now, so managing a second list that HAS to contain similar matches will be a real pain. </FONT></P>
<P><FONT SIZE=2>(BTW: I can't wait until the 4.29.5 code is stable and I can have one list entry for *@*.* and *@*, nice job!)</FONT>
</P>
<P><FONT SIZE=2>Jason</FONT>
</P>
</BODY>
</HTML>