After messing around with different versions of policyd I found an error on the default database structure generated for mysql.
This happens with versions 2.0.10 and 2.0.11, mysql database. The error is within the table quotas_tracking structure. The default structure for the field quotas_tracking.Counter is decimal(10,4). Since the MessageCumulative size limit in the quota module is in bytes this is easy to overflow, and the value stored in database ends being 999999.9999, which is roughly almost 1 MB only The quota update tries to setup for example a 5 MB quota usage, but the counter field get stalled at 1MB. By resetting the database structure in the field quotas_tracking.Counter to decimal(15,4) that gives a maximum of 99999999999.9999, or 93GB. And this solved the problem. Also, i would like to request a feature, it it possible to have another type of quota limit, RCPTCount, to avoid users sending a messages that contains 1000 TOs or BCCs each. Regards Juan.-
