AFAIU Courier's global filtering mechanism starts working only after receiving message in its entirety. At the same time main advantage of greylisting is handling "triplets" at the very early stage of SMTP dialog and hence avoiding significant volume of spam traffic (at least for highly loaded mail servers).
I'm not worried about traffic myself. If the filter reduces the amount of spam that gets to users, then my primary goals are met (although I don't really like this particular hack of a mechanism).
So this filtering concept could work efficiently only being implemented as integral part of ESMTP daemon (submit program) along with other antispam measures as HELO check suggested recently by Roland Schneider, and used _before_ accepting SMTP DATA command.
I'd suggest that you adapt the code to Courier's localmailfilter API, but that doesn't seem to allow you to do a soft reject (4xx).
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
