Sure. That feature was added in v4.0.0.773. The release notes are below.

Please do note however that we implemented our own "flavor" of greylisting, and we're not following the "standards" for geylisting as they seem too strict for us. While the "standard" greylisting considers the sender's and the recipient's email address in the delaying of emails, SpamFilter will only consider the sender's IP address. This usually allows an entire ISP to be greyslited only for a few minutes, causing a nearly imperceptible delay to just one of your users - the first one who receives an email from that domain. From then on, once the email is received, the ISP will always pass the greylisting test. While this does allow a few more spammers to go thru, it virtually eliminates any delays and side-effects of greylisting. And furthermore... SpamFilter has awesome filtering abilities :-) so the few extra spam emails will likely be blocked by our other filters.

// New to VersionNumber = '4.0.0.773';
{TODO -cNew : Allowed to specify future dates in the GreyListAllowed.txt files so that IPs can be stored in the list for years without expiring}



Edited by LogSat - 04 May 2008 at 8:31am

The greylist (and the cached IP blacklist) work on a TCP level before any SMTP commands are given, and thus will take precedence over any other whitelist/blacklist. So adding an IP to the IP whitelist will not override those two filters. The order in which the filters are applied is available at:
http://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=5171#11418


Edited by LogSat - 04 May 2008 at 10:31am

Rifleman wrote: Will this eventiually be also placed in the DB?

It's very unlikely. During the greylisting alpha testing stages, we soon found that databases were often not able to sustain the large amount of queries (inserts/deletes) per second needed to handle the incoming flow of connections. All the greylisting lookups/updates are thus performed in RAM by SpamFilter.

The greylisting file is only read when SpamFilter starts, it's not auto-loaded when changes to it are made. As a matter of fact, SpamFilter will overwrite any external changes made to that file when the greylisted IPs are flushed from RAM to the file.