On 23/08/2012 12:58, soumya tr wrote:
I meant all the details in cbpolicyd.log [with debug mode]
These are policyd's logs. Debug mode just prints some extra useful information for debugging purposes.
Also what is the difference between 1 and 2: ----------------------- 1. smtpd_recipient_restrictions = check_policy_service inet:127.0.0.1:10032 <http://127.0.0.1:10032>, permit_mynetworks, reject_unauth_destination 2. smtpd_recipient_restrictions = permit_mynetworks, check_policy_service inet:127.0.0.1:10032 <http://127.0.0.1:10032>, reject_unauth_destination -----------------------
permit_mynetworks tells postfix to permit the request based on what is defined in $mynetworks. See http://www.postfix.org/postconf.5.html#permit_mynetworks
As when I use rule 2 the quota_tracking dosent work. Is it necessary that check_policy_service inet:127.0.0.1:10032 <http://127.0.0.1:10032> has to be always put before permit_mynetworks?
It really depends on the set up but we recommend check_policy_service being first.
If rule 2 is used, isn't it like the mails from the ips as listed in permit_mynetworks will be allowed, then policyd policies will be applied on that , and if the policy is satisfied then if any mail has unauth destination it will be rejected. This is what I understood about the postfix rules after googl-ing. Is my this interpretation wrong? Note: permit_mynetworks has the IP ranges of the those servers which relay mail via the postfix+policyd server.
If permit_mynetworks is first and its matched in mynetworks, it won't reach check_policy_service because it's permitted.
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
