similar to: Question regarding reverse quota_warning

Hi all, I noticed that in some circumstances quota warnings are ignored. 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

On 17.02.2015 20:03, Micha? Gi?y?ski wrote: > > On 21.11.2014 20:04, Grzegorz Nosek wrote: >> Hi all, >> >> I noticed that in some circumstances quota warnings are ignored. 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 >>

Hello, We are using dovecot 1.0.8 with LDAP authentication and extra variebles (like quota limit) storage. Since some of our users are asking for warning of quota use I have been playing around with the quota rewrite patch for dovecot 1.0.8 and found that it does not work for us as it is now. I've applied the patch recompiled dovecot reconfigured using the new "quota_warning"

Hello everyone, I'm experimenting with the quota warning plugin. I have the following setting in Dovecot's general config: plugin { quota_warning = storage=75%% /var/www/contrib/doquotawarning.py 75 quota_warning2 = storage=90%% /var/www/contrib/doquotawarning.py 90 } The doquotawarning.py script is working okay -- meaning that the user gets a warning. My SQL backend uses the

On 21.11.2014 20:04, Grzegorz Nosek wrote: > Hi all, > > I noticed that in some circumstances quota warnings are ignored. 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

Having implemented a GC for HLVM, I am now turning my attention to implementing a GC that supports parallelism. To do this, I would like to use atomic instructions as well as mutexes. What is the status of LLVM's atomic instrinsics (e.g. CAS)? Is anyone using them in real projects? I realised that an obvious test would be to compile some simple example programs with llvm-g++ instead of

Hi, Today I was testing with dovecot 2.0 rc5 and experienced some odd behaviour with quota_warning rules. It's reproducable. When I set a rule (this one simply writes some message to a text file) and go over quota (2 messages in this case), it works as expected. But if I restart my client, remove one message, restart my client again and remove the last message from my inbox, it executes

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

Jon Harrop wrote: > Having implemented a GC for HLVM, I am now turning my attention to > implementing a GC that supports parallelism. To do this, I would like to use > atomic instructions as well as mutexes. What is the status of LLVM's atomic > instrinsics (e.g. CAS)? Is anyone using them in real projects? > > I realised that an obvious test would be to compile some

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 - >>>

Hello all, I'm trying to get dovecot read three different quota_warnings values directly from ldap. I configured correctly the quota_rule value, know I'm trying to override this values: quota_warning = storage=95%% /usr/local/bin/quota-warning.sh 95 quota_warning2 = storage=80%% /usr/local/bin/quota-warning.sh 80 quota_warning3 = storage=70%% /usr/local/bin/quota-warning.sh 70 reading

Hi, We've been using v1.0.5 +quota_warning patch, however quota_warning does't seem to be working properly. For example, in order to enable 80% over for quota warning, and we configured like following: ----------------------------------------------------------------------- plugin { quota_warning = storage=80%% /usr/local/path/to/plugin }

Hello. I'm reading http://wiki.dovecot.org/Quota/1.1 one last time before my upgrade, and I have a question about quota_warning option. Which type of script must we use for this example: quota_warning = storage=95%% /usr/local/bin/quota-warning.sh 95 What the script must doing? It sends an email? It deletes some emails? Thanks! -- -Nicolas.

hi everyone, i have dovecot 1.2.11 and postfix with virtual users and domains and mailscanner all is working fine but i cant made works the quota_warning i have in my script touch quota to see is the script run but never hapen i have in dovecot-sql.conf 'storage=10%% /etc/postfix/limit.sh' as quota_warning and in the log he show this but nothing happend, anyone have this same problem and

Hi, I am curious if Dovecot can add an empty file into a Maildir folder as soon as a mailbox has exceeded 100% capacity, and later when it detects the quota has fallen below 100% unlink the file. The idea is the Dovecot LDA would deliver the message and if this caused the mailbox to reach 100%+, add a file into the maibox say "username/Maildir/overquota". Interactions via Dovecot

Hi, # doveadm -Dv quota get -u pit doveadm(pit): Debug: auth input: pit system_groups_user=pit uid=500 gid=500 home=/home/pit doveadm(pit): Debug: Effective uid=500, gid=500, home=/home/pit doveadm(pit): Debug: Quota root: name=INBOX backend=fs args=mount=/var/spool/mail doveadm(pit): Debug: Quota rule: root=INBOX mailbox=* bytes=19922944 messages=0 doveadm(pit): Debug: Quota warning:

Having tried and failed to get 1.0.8 with quota-rewrite to send warnings, I removed the 1.0.8 and installed the latest 1.1 - however I still can't get the warnings! Can someone advise what might be wrong - it must be my configuration?? To compile 1.1 I used ./configure --with-deliver --with-mysql. I've chopped and changed my conf till I'm blue in the face. My dovecot-mysql.conf file

I'm using 1.2.6 with the managesieve patch and maildir++ quotas (via the maildirsite file). Again, I found that the quota warning is not bering triggered. Testing via: smtp-source -4 -f sender at charite.de -t recipient at charite.de -m 1 -l 1000000 -C 1 mail.charite.de:submission recipient at charite.de being a mailbox with a 10.0 MB limit. I attached dovecot -n and the quota warn script.

Hi, I created a dovecot resource script for pacemaker. I think it's done, but I wanted to ask if some people could examine it before I send it to the pacemaker people. Thanks in advance. Best regards, Jeoren Koekkoek -------------- next part -------------- A non-text attachment was scrubbed... Name: dovecot Type: application/x-shellscript Size: 9832 bytes Desc: not available URL: