On Tue, 4 Mar 2008, rupert wrote: > On Thu, Feb 28, 2008 at 6:03 PM, rupert <[EMAIL PROTECTED]> wrote: >> Hello, >> how do I have to arrange the recipeint_restrictions to prevent >> spambots, not authentificated user but >> use policyd and other restrictions? >> My line looks like this now >> smtpd_recipient_restrictions = permit_mynetworks, >> permit_sasl_authenticated, reject_unauth_destination, >> reject_unlisted_recipient, check_policy_service inet:127.0.0.1:12525, >> check_policy_service inet:127.0.0.1:10031 >> >> I had policyd more in the front but than i got thousands of tawain >> logins in my logfiles and it flooded the policyd DB, so how can I get >> the best results?
FWIW I tend to put the policyd check after the postfix checks and after authentication checks, something like this. I put policyd after as much basic checking as I can just to reduce its load, but I put it before the rbl checks to be able to whitelist the odd server that may occasionally end up in an rbl, but from which some client must receive email. Others may have a different arrangement; mostly it is a matter of understanding your particular situation and arranging the order appropriately. smtpd_recipient_restrictions = reject_unlisted_recipient permit_mynetworks reject_unknown_reverse_client_hostname reject_non_fqdn_sender reject_non_fqdn_recipient reject_invalid_hostname reject_unauth_pipelining reject_unknown_sender_domain reject_unauth_destination policyd rbl checks -- Michael ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users