Policyd v2 Cluebringer – Quotas Message Cumulative Size

emailpolicydpostfix

I have installed Policyd Cluebringer v2.0.10 from Ubuntu 12.04 packages.
I have configured it for email quotas but the quota doesn't increase when I send mails.
Here is the mail.log :

09:06:15 policyd postfix/smtpd[14991]: connect from unknown[192.168.64.168]
09:06:15 policyd cbpolicyd[14898]: module=Quotas, mode=update, host=192.168.64.168, helo=EDCADMV0012, from=joe@mydomain.local, to=bob@mydomain.local, reason=quota_update, policy=6, quota=3, limit=4, track=Sender:joe@mydomain.local, counter=MessageCumulativeSize, **quota=0/300000 (0.0%)**
09:06:15 policyd postfix/smtpd[14991]: 8EAEF42E74: client=unknown[192.168.64.168]
09:06:16 policyd postfix/cleanup[14995]: 8EAEF42E74: message-id=<037e01ce6d84$a42a4f70$ec7eee50$@mydomain.local>
09:06:16 policyd postfix/qmgr[13333]: 8EAEF42E74: from=<joe@mydomain.local>, **size=6792**, nrcpt=1 (queue active)
09:06:16 policyd postfix/smtp[14997]: 8EAEF42E74: to=<bob@mydomain.local>, relay=10.0.0.10[10.0.0.10]:25, delay=1.2, delays=1.1/0.03/0/0.02, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 6C82B2C7190)
09:06:16 policyd postfix/qmgr[13333]: 8EAEF42E74: removed
09:06:19 policyd postfix/smtpd[14991]: disconnect from unknown[192.168.64.168]

We can see that the quota doesn't change whereas the size of the email is 6792 byte.

Someone can bring me light?

Thanks!

Edit : the cluebringer.conf file :

[server]
protocols=<<EOT
Postfix
Bizanga
EOT

modules=<<EOT
Core
AccessControl
CheckHelo
CheckSPF
Greylisting
Quotas
EOT

user=cluebringer
group=cluebringer

pid_file=/var/run/cluebringer/cbpolicyd.pid

log_level=4
log_mail=mail@syslog:native
log_detail= policies, tracking

host=127.0.0.1
port=10031

[database]
DSN=DBI:mysql:database=policyd;host=localhost
DB_Type=mysql
DB_Host=localhost
DB_Port=3306
DB_Name=policyd
Username=root
Password=mypass

bypass_mode=tempfail

bypass_timeout=30

[AccessControl]
enable=1

[Greylisting]
enable=1    

[CheckHelo]
enable=1

[CheckSPF]
enable=1

[Quotas]
enable=1

Best Answer

I have made a mistake in the /etc/postfix/main.cf file. I didn't set 'smtpd_end_of_data_restrictions=check_policy_service inet:127.0.0.1:10031'.

Related Solutions

How to restrict postfix send limited email with policyd v2

That is all you need to do with Postfix but you need to fill up mysql database used by Policyd.

Copy web files from webui dir to web accessible dir. Open the page and set up what you want (quotas, limits etc.).

Do not forget to create some kind of user/pass access control (for example via .htaccess/.htpasswd file...

Zimbra 8 policyd failed SMTP login increments quota counter

Introduction

Zimbra is email and collaborative suits. It uses postfix as MTA. You can optionally enable policyd to provide limiting features such as quota or throttle.

Every configuration can be altered by web interface or CLI. Direct editing to configuration file / database shouldn't be done. Zimbra could overwrite it when upgrading or restarting.

Enabling policyd

According to this page, we can enable policyd by executing two command lines only.

In the background, zimbra will altered postfix configuration. Here the postconf -n output before and after policyd enabled.

smtpd_client_restrictions = reject_unauth_pipelining
smtpd_data_restrictions = reject_unauth_pipelining
smtpd_end_of_data_restrictions =
smtpd_etrn_restrictions =
smtpd_helo_restrictions =
smtpd_recipient_restrictions = yreject_non_fqdn_recipient, permit_sasl_authenticated, permit_mynetworks, reject_unlisted_recipient, reject_invalid_helo_hostname,  reject_non_fqdn_sender, permit
smtpd_relay_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination
smtpd_restriction_classes =
smtpd_sender_restrictions =

After

smtpd_client_restrictions = reject_unauth_pipelining
smtpd_data_restrictions = reject_unauth_pipelining
smtpd_end_of_data_restrictions = check_policy_services 127.0.0.1:10031
smtpd_etrn_restrictions =
smtpd_helo_restrictions =
smtpd_recipient_restrictions = check_policy_services 127.0.0.1:10031, reject_non_fqdn_recipient, permit_sasl_authenticated, permit_mynetworks, reject_unlisted_recipient, reject_invalid_helo_hostname,  reject_non_fqdn_sender, permit
smtpd_relay_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination
smtpd_restriction_classes =
smtpd_sender_restrictions = check_policy_services 127.0.0.1:10031

Analysis

The behavior that happened in your zimbra can be explained after analyze the output of postconf -n. At smtpd_sender_restrictions stage, zimbra already contacts policyd (by check_policy_services). In that stage, the counter was already incrementing. In smtpd_relay_restrictions stage, postfix reject the email by emitting error message 'authorization failed'.

Solution

Based on analysis above, the behavior can be prevented by removing check_policy_services in smtpd_sender_restrictions. Postfix still call check_policy_services in smptd_recipient_restrictions.

Disclaimer:

This applied to zimbra version 8.0.7. Other version maybe doesn't get this bug.
As stated above, direct editing to configuration file doesn't officially supported. Maybe there is design reason why Zimbra put policyd earlier and direct editing could breaks it. For the safety, you can post it in zimbra support and discuss it with zimbra developers.

Related Topic