cbpolicyd

[uxbod]

Is anybody using it yet ? Is it ready for prime time ? I am guessing if you have two MTAs it will need to be enabled on both; therefore for the greylisting to be effective is the SQLite3 database replicated between nodes ?

[drwho18]

I've been using policyd with zimbra for a few years, I just upgraded to Zimbra 7.1.4 from the 5.x.x series and used the same instance, didn't install the one that came with Zimbra, just made sure the new GUI entry for policyd was pointed at the right location.

Zimbra needs to integrate the controls for policyD into the GUI, maybe even down to the COS level type of settings. I think solutions like PolicyD should be really basic functionality in any mail system these days.

[bjron.mork]

Hi,

I installed Zimbra 7.1.4, and enabled the user policyd via below mentioned link.

[HowTo] Enabling CBPolicyD in Zimbra 7.1.1

I enabled Policyd WEBUI, but i don't see any logs being process by Policyd Server. It seems that Zimbra Server is not allowing policyd to check any of its feature

My Server is listening on 10031 port.

[root@mail ~]# netstat -natp | grep 10031
tcp 0 0 127.0.0.1:10031 0.0.0.0:* LISTEN 4450/perl

And /opt/zimbra/postfix/conf/main.cf configurations file is as below...

[root@mail ~]# grep restrictions /opt/zimbra/postfix/conf/main.cf
smtpd_recipient_restrictions = check_policy_service inet:127.0.0.1:10031, reject_non_fqdn_recipient, permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination, reject_unlisted_recipient, reject_invalid_hostname, reject_non_fqdn_hostname, reject_non_fqdn_sender, reject_unknown_client, reject_unknown_hostname, reject_unknown_sender_domain, reject_rbl_client relays.mail-abuse.org reject_rbl_client dnsbl.njabl.org reject_rbl_client cbl.abuseat.org reject_rbl_client bl.spamcop.net reject_rbl_client sbl.spamhaus.org, permit
smtpd_data_restrictions = reject_unauth_pipelining
smtpd_sender_restrictions =
smtpd_client_restrictions = reject_unauth_pipelining
smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10031

And

[root@mail ~]# cat /opt/zimbra/conf/postfix_recipient_restrictions.cf
%%contains VAR:zimbraServiceEnabled cbpolicyd, check_policy_service inet:127.0.0.1:10031%%
reject_non_fqdn_recipient
permit_sasl_authenticated
permit_mynetworks
reject_unauth_destination
reject_unlisted_recipient
%%contains VAR:zimbraMtaRestriction reject_invalid_hostname%%
%%contains VAR:zimbraMtaRestriction reject_non_fqdn_hostname%%
%%contains VAR:zimbraMtaRestriction reject_non_fqdn_sender%%
%%contains VAR:zimbraMtaRestriction reject_unknown_client%%
%%contains VAR:zimbraMtaRestriction reject_unknown_hostname%%
%%contains VAR:zimbraMtaRestriction reject_unknown_sender_domain%%
%%explode reject_rbl_client VAR:zimbraMtaRestrictionRBLs%%
%%contains VAR:zimbraMtaRestriction check_policy_service unixrivate/policy%%
permit

Any clue to enable cbpolicyd will be appreciated.

Regards
B~Mork.

[bjron.mork]

Can anyone please help. Its much critical for me before moving to production environment.

My requirements are:

(1) Each User should not be able to send 200 emails per day (based on user@domain.com)
(2) Each user should not send more than 50MB attachment

Can this be achieved through zimbra only????????

I have to ensure these limits within zimbra or either using policyd.

Please help.