search for: bytes_current

...e default rule value). In my sample 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...

...3,8 @@ static void quota_warnings_execute(struct quota_transaction_context *ctx, &count_current, &count_limit) < 0) return; + quota_root_recalculate_relative_rules(root->set, bytes_limit, count_limit); + bytes_before = bytes_current - ctx->bytes_used; count_before = count_current - ctx->count_used; for (i = 0; i < count; i++) {

...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 ----- I think it could be as simpl...

...nsaction_context *ctx, >> &count_current, &count_limit) < 0) >> return; >> >> + quota_root_recalculate_relative_rules(root->set, bytes_limit, >> count_limit); >> + >> bytes_before = bytes_current - ctx->bytes_used; >> count_before = count_current - ctx->count_used; >> for (i = 0; i < count; i++) { > Hi, > this patch realy fix the bug in quota_warning. Is it possible to add > this patch to the next release ? > Hi, I saw that new dovecot was r...

...ecute(struct > quota_transaction_context *ctx, > &count_current, &count_limit) < 0) > return; > > + quota_root_recalculate_relative_rules(root->set, bytes_limit, > count_limit); > + > bytes_before = bytes_current - ctx->bytes_used; > count_before = count_current - ctx->count_used; > for (i = 0; i < count; i++) { Hi, this patch realy fix the bug in quota_warning. Is it possible to add this patch to the next release ? -- Pozdrawiam / Best Regards Micha? Gi?y?ski

...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're using Dovecot 1.2.9 (U...