search for: bytes_limit

...mple a 50% limit returned a value of 25 bytes for the limit instead of 5,120. The other problem is when checking the limits to execute the scripts, the "quota_warnings_execute" function is checking if the warning limit is reached with this comparison: if ((bytes_current < warnings[i].bytes_limit && bytes_current + ctx->bytes_used >= warnings[i].bytes_limit) || ... My debug have reported that at the point of the execution of this function the "bytes_current" variable already includes the size of the current transaction (at least it was in all my tests)...

...The bug arises when both of the following are used: 1. percentage-based quota warnings, i.e.: quota_warning = storage=1%% quota-warning 1 %u 2. filesystem quota backend (and probably others, except for quotas configured directly in dovecot config) Percentage-based quota warnings have rule.bytes_limit recalculated based on root_set->default_rule.bytes_limit, however this value is zero when FS quotas are in use. Real quota values (from quotactl) are fetched very late, in quota_warnings_execute() but at that point no recalculation happens. As the warning rules have bytes_limit==0, they'...

...ercentage-based quota warnings, i.e.: >> >> quota_warning = storage=1%% quota-warning 1 %u >> >> 2. filesystem quota backend (and probably others, except for quotas >> configured directly in dovecot config) >> >> Percentage-based quota warnings have rule.bytes_limit recalculated >> based on root_set->default_rule.bytes_limit, however this value is >> zero when FS quotas are in use. Real quota values (from quotactl) are >> fetched very late, in quota_warnings_execute() but at that point no >> recalculation happens. As the warning...

...ing are used: > > 1. percentage-based quota warnings, i.e.: > > quota_warning = storage=1%% quota-warning 1 %u > > 2. filesystem quota backend (and probably others, except for quotas > configured directly in dovecot config) > > Percentage-based quota warnings have rule.bytes_limit recalculated > based on root_set->default_rule.bytes_limit, however this value is > zero when FS quotas are in use. Real quota values (from quotactl) are > fetched very late, in quota_warnings_execute() but at that point no > recalculation happens. As the warning rules have bytes...

dovecot v2.2.16 I've found a few bugs in Trash plugin. 1. If Quota set only messages limit (without storage limit) then Trash plugin does not expunge any message because Quota plugin sets too_large_r=TRUE. It's because quota_default_test_alloc function does not check if bytes_limit is set. /* if size is bigger than any limit, then it is bigger than the lowest limit */ - if (size > bytes_limit) { + if (bytes_limit > 0 && size > bytes_limit) { *too_large_r = TRUE;...

...ges if a person is over his/her quota limit. Although this can be accomplished using a quota_warning script, I can't find how to accomplish the reverse. Has anyone tried to do something like this? By looking at the source code: ---- quote ---- if ((bytes_before < (uint64_t)warnings[i].rule.bytes_limit && bytes_current >= (uint64_t)warnings[i].rule.bytes_limit) || (count_before < (uint64_t)warnings[i].rule.count_limit && count_current >= (uint64_t)warnings[i].rule.count_limit)) { quota_warning_execute(root, warnings[i].command); break; } ----- /quote -----...

...e warning event twice. When getting from e.g. 50% to 79% and when the usage is lowered from 87% to 70%. I have the feeling this is either not the correct behavior, or I'm misinformed. When looking at the source, this shouldn't be happening: if ((bytes_before < (uint64_t)warnings[i].rule.bytes_limit && bytes_current >= (uint64_t)warnings[i].rule.bytes_limit) || (count_before < (uint64_t)warnings[i].rule.count_limit && count_current >= (uint64_t)warnings[i].rule.count_limit)) { quota_warning_execute(root, warnings[i].command); break; } We...

On 24.01.2017 11:31, Tom Sommer wrote: > On 2017-01-24 10:25, Aki Tuomi wrote: >> On 24.01.2017 11:13, Tom Sommer wrote: >>> On 2017-01-18 15:27, mkliewe at gmx.de wrote: >>> >>>> dovecot crashes when I switch the quota tracking from dict to count. >>> >>> I have the same problem, but I use 'dict:file' as quota backend - >>>