On Thu, Aug 23, 2012 at 12:26 PM, Robert Anderson <[email protected]>wrote:
> It's possible that you could try with a sort of negate specification, > !%internal_ips, %those_internal_ips where %those_internal_ips is where > those internal mails are from. Perhaps make a testing DB based on the > current DB and alter accordingly? > > Okay will do. > To which details are you referring? > > I meant all the details in cbpolicyd.log [with debug mode] Also what is the difference between 1 and 2: ----------------------- 1. smtpd_recipient_restrictions = check_policy_service inet: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, reject_unauth_destination ----------------------- As when I use rule 2 the quota_tracking dosent work. Is it necessary that check_policy_service inet:127.0.0.1:10032 has to be always put before permit_mynetworks? 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. Thanks in advance. -- Regards, Soumya
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
