--Andrew Newton wrote on 05.03.03 22:05 -0500: > Is there a particular advantage to doing it this way rather than just using maildrop > and something like SpamAssassin?
Simplicity, and evaluation of dnsbl. Evaluate new dnsbl first with $BLOCK2, check your mailbox after a few weeks, whitelist those who cant afford a responsible provider, and change the entry to $BLOCK if you feel confident about. I dont see any reason why this feature should not be integrated into courier. Filtering via xfilter also has some other caveats because maildrop cant use the return value of Spamassassin (only bounce which is plain ugly), the message has already been accepted at that point. Filtering via .courier-dotfiles would allow for parsing the results of Spamassassin, but requires shell-privileges and some knowledge. Spamassassin consequently should be integrated into perlfilter, unless you users have a shell and wont mess up everything. But the code copied is just part of a more complex system where each user individually chooses wether to reject or tag suspicious sources based on what the per-user-api (maildropfilter) returned. Thus the final } was missed in the code ;) Roland ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
