Re: check_policy_service does not work as expected: protocol_state=RCPT, even under smtpd_client_restrictions

mig schrieb: I wrote a policy server (that do RBL checks and dynamically disable slow RBL servers). I supposed the right place is the smptd_client_restrictions: postfwd does asynchronous dnsbl lookups and allows to disable non-responding lists automatically. it also has an integrated cache

check_policy_service does not work as expected: protocol_state=RCPT, even under smtpd_client_restrictions

Hello, I wrote a policy server (that do RBL checks and dynamically disable slow RBL servers). I supposed the right place is the smptd_client_restrictions: smtpd_client_restrictions = check_policy_service unix:/opt/mailfilter/client_restrictions smtpd_helo_required = yes

Re: check_policy_service does not work as expected: protocol_state=RCPT, even under smtpd_client_restrictions

mig: Hello, I wrote a policy server (that do RBL checks and dynamically disable slow RBL servers). I supposed the right place is the smptd_client_restrictions: smtpd_client_restrictions = check_policy_service unix:/opt/mailfilter/client_restrictions smtpd_helo_required = yes

Re: check_policy_service does not work as expected: protocol_state=RCPT, even under smtpd_client_restrictions

On Sat, 28 Mar 2009, mig wrote: I wrote a policy server (that do RBL checks and dynamically disable slow RBL servers). I supposed the right place is the smptd_client_restrictions: smtpd_client_restrictions = check_policy_service unix:/opt/mailfilter/client_restrictions

Re: check_policy_service does not work as expected: protocol_state=RCPT, even under smtpd_client_restrictions

Thanks for reply, But I'm still a bit confused about the SMTPD_ACCESS_README.html: Restriction lists are still evaluated in the proper order of (client, helo, etrn) or (client, helo, sender, recipient, data, or end-of-data) restrictions. I agree, all restriction lists are evaluated on the

Re: check_policy_service does not work as expected: protocol_state=RCPT, even under smtpd_client_restrictions

On Sun, 29 Mar 2009, mig wrote: Thanks for reply, Please, don't top-post. But I'm still a bit confused about the SMTPD_ACCESS_README.html: Restriction lists are still evaluated in the proper order of (client, helo, etrn) or (client, helo, sender, recipient, data, or end-of-data)