On Sat, October 13, 2007 09:59, Tony Earnshaw wrote: > To my mind it should come last in smtpd_recipient_restrictions. What's > the point of greylisting stuff that Postfix would reject anyway?
this is true as long policyd cant use smtpd_restriction_classes as results policyd can be used with succes when this is an option, idear stolen from policyd-weight :-) another policy is to use maRBL to make rbl test, so postfix just get accept or reject, or smtpd_restriction_class as result then make future test there what i personly dont like is to change order of tests, eg dont end all test with reject on failed helo have policyd last after all postfix restrictions, and keep all sender test equal for any sender, eg no exceptions i use another policy daemond here, not becurse policyd is bad, it just me that are alpha tester on a python script :) the python can: check mx is sender ip check spf sender domains check rbl client ip check rbl sender domains make greylistning make spamtraping, with real users on catch all domains, hides what email is spamtrap and with is not can make pr recipient acl so all the above is with pr recipient scores goal is scalable all combined to a weight system, i love it it keeps my amavisd from heavy working -- This message was sent using 100% recycled spam mails. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
