search for: quota_domain

Hello, I'm in the process of moving users from an old dovecot setup with system users to a modern virtual user setup. I can't find good documentation on domain quota. It is mentioned in the docs as quota2 = dict:domain:%d:proxy::quota_domain but not much more. Searching the mailing list or Google doesn't reveal much more info. Searching the German mailing list at jpberlin finds mostly information where they say that it doesn't work. So, does it or does it not? And if it works, does it work like I'm used to? e.g. with sy...

Hi I just configure dovecot with the second dictionary for the domain quota dict { quotadict = mysql:/usr/local/etc/dovecot-quota.conf quota_domain = mysql:/usr/local/etc/dovecot-quota-domain.conf } plugin { quota = dict:user::proxy::quotadict quota2 = dict:domain:%d:proxy::quota_domain } and the dovecot-quota-domain.conf looks like this : connect = host=xxx dbname=xxx user=xxxx password=xxxx map { pattern = priv/quota/storag...

...es in *does* seem to work correctly. But if I run a recalc it all gets messed up. This has been reported a few times over time, so I guess it's not specific to my setup. So, here's the relevant bits again (and a bit more): dict { quota = mysql:/etc/dovecot/dovecot-dict-sql-user.conf quota_domain = mysql:/etc/dovecot/dovecot-dict-sql-domain.conf } mail_home = /var/vmail/%d/%n mail_location = maildir:/var/vmail/%d/%n/mail/ mail_plugins = " quota" plugin { quota = dict:user::proxy::quota quota2 = dict:domain:%d:proxy::quota_domain quota_rule = *:storage=100M quota_rule2 =...

I have dovecot version 2.1.7 and I have quota configured as: ----------------------------------- dict { quota_domain = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } mail_plugins = quota protocol imap { mail_plugins = quota quota imap_quota } plugin { quota = dict:domain:%d:proxy::quota_domain quota_rule = *:storage=1M quota_rule2 = Trash:storage=+100M } ----------------------------------- /etc/dovecot/do...

...ist of which of their users are using the most space. That is to be purely informative, and is not to be enforced. I would appreciate if there was a documented way to specify exact SQL queries to run for inserting, updating and selecting from the quota storage, something like this: -- CREATE VIEW quota_domain AS SELECT domain, sum(bytes), sum(messages) FROM quotas GROUP BY domain INSERT/UPDATE INTO quotas(username, domain, bytes, messages) SELECT bytes, messages from quota_domain WHERE domain = %d Is there such a possibility? If not, can you suggest a workaround to have a list of per-user quota usag...

...ntation, there could be possible, from the sample configuration file # Multiple quota roots are also possible, for example this gives each user # their own 100MB quota and one shared 1GB quota within the domain plugin { quota = dict:User quota::proxy::quota quota2 = dict:Group quota:%d:proxy::quota_domain quota_rule = *:storage=1024M quota2_rule = *:storage=2048M } But If I run [TEST] root at mail-store01.test.host.sk: /etc/dovecot # doveadm quota get -u '*' Username Quota name Type Value Limit % test01 at...

...wrote: > > > Hello, > > I'm in the process of moving users from an old dovecot setup with system > users to a modern virtual user setup. > > I can't find good documentation on domain quota. > It is mentioned in the docs as > quota2 = dict:domain:%d:proxy::quota_domain > but not much more. > Searching the mailing list or Google doesn't reveal much more info. > Searching the German mailing list at jpberlin finds mostly information > where they say that it doesn't work. > So, does it or does it not? > > And if it works, does it work...

....13 custom grsec kernel :Linux postfix 3.14.50-grsec-1 ########################## dovecot -n : # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.14.50-grsec-1 x86_64 Debian 8.1 nfs4 auth_mechanisms = plain login auth_verbose = yes dict { quota = mysql:/etc/dovecot/dovecot-dict-sql-user.conf quota_domain = mysql:/etc/dovecot/dovecot-dict-sql-domain.conf } lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_trusted_networks = XXXXXX/24 mail_location = maildir:/maildir/%d/%n/Maildir mail_plugins = " quota" managesieve_notify_capability = mailto managesieve_sieve_capability =...

...file >> >> # Multiple quota roots are also possible, for example this gives each user >> # their own 100MB quota and one shared 1GB quota within the domain >> >> plugin { >> quota = dict:User quota::proxy::quota >> quota2 = dict:Group quota:%d:proxy::quota_domain >> quota_rule = *:storage=1024M >> quota2_rule = *:storage=2048M >> } >> >> >> But If I run >> [TEST] root at mail-store01.test.host.sk: /etc/dovecot # doveadm quota get -u '*' >> Username Quota name Type Value Limit...

...vecot:/etc/dovecot# dovecot --version 2.2.13 root at cluster-dovecot:/etc/dovecot# dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.0 auth_debug_passwords = yes auth_mechanisms = plain login dict { quota = mysql:/etc/dovecot/dovecot-dict-sql-user.conf quota_domain = mysql:/etc/dovecot/dovecot-dict-sql-domain.conf } lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_debug = yes mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_plugins = quota fts fts_solr acl zlib mail_log notify managesieve_notify_capability = mailto managesieve_sieve_capabi...

...rom the sample configuration file > > # Multiple quota roots are also possible, for example this gives each user > # their own 100MB quota and one shared 1GB quota within the domain > > plugin { > quota = dict:User quota::proxy::quota > quota2 = dict:Group quota:%d:proxy::quota_domain > quota_rule = *:storage=1024M > quota2_rule = *:storage=2048M > } > > > But If I run > [TEST] root at mail-store01.test.host.sk: /etc/dovecot # doveadm quota get -u '*' > Username Quota name Type Value Limit...

...ser quota #quota = dict:User quota::proxy::quota #quota = fs:User quota } # Multiple quota roots are also possible, for example this gives each user # their own 100MB quota and one shared 1GB quota within the domain: plugin { #quota = dict:user::proxy::quota #quota2 = dict:domain:%d:proxy::quota_domain #quota_rule = *:storage=102400 #quota2_rule = *:storage=1048576 } Please help me with configuration. I really stuck with this thing. And yes i've tried to find solutions on mailing list, but no luck. I want per domain/user quota in mysql. Also space usage to be shown in roundcube. Hope to...

...t:User quota::proxy::quota #quota = fs:User quota quota = count:User quota # This is required - it uses "virtual sizes" rather than "physical sizes" for quota counting: quota_vsizes = yes } plugin { #quota = dict:user::proxy::quota #quota2 = dict:domain:%d:proxy::quota_domain #quota_rule = *:storage=102400 #quota2_rule = *:storage=1048576 } service quota-warning { executable = script /usr/local/bin/quota-warning.sh user = dovecot unix_listener quota-warning { user = vmail } } service quota-status { executable = quota-status -p postfix in...

...orage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u } plugin { #quota = dirsize:User quota #quota = maildir:User quota #quota = dict:User quota::proxy::quota #quota = fs:User quota } plugin { #quota = dict:user::proxy::quota #quota2 = dict:domain:%d:proxy::quota_domain #quota_rule = *:storage=102400 #quota2_rule = *:storage=1048576 } service quota-warning { executable = script /usr/local/bin/quota-warning.sh user = dovecot unix_listener quota-warning { user = vmail } } service quota-status { executable = quota-status -p postfix inet_listen...

I have been running Dovecot 1.2.5 since Sept 14. Beginning at about 03:28 on Sept 21 for no apparent (to me) reason and continuing through the present, I am seeing log messages like the following and am experiencing delays logging in. Sep 22 19:07:15 sbh16 dovecot: dovecot: Temporary failure in creating login processes, slowing down for now Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal:

...ng2 = storage=80%% quota-warning 80 %u > } > plugin { > #quota = dirsize:User quota > #quota = maildir:User quota > #quota = dict:User quota::proxy::quota > #quota = fs:User quota > } > plugin { > #quota = dict:user::proxy::quota > #quota2 = dict:domain:%d:proxy::quota_domain > #quota_rule = *:storage=102400 > #quota2_rule = *:storage=1048576 > } > service quota-warning { > executable = script /usr/local/bin/quota-warning.sh > user = dovecot > unix_listener quota-warning { > user = vmail > } > } > service quota-status { >...

...:sqlquota #quota = dict:User quota::proxy::quota #quota = fs:User quota } # Multiple quota roots are also possible, for example this gives each user # their own 100MB quota and one shared 1GB quota within the domain: plugin { #quota = dict:user::proxy::quota #quota2 = dict:domain:%d:proxy::quota_domain #quota_rule = *:storage=102400 #quota2_rule = *:storage=1048576 quota_status_success = DUNNO quota_status_nouser = DUNNO quota_status_overquota = "552 5.2.2 Mailbox is full" } -------------- next part -------------- connect = host=192.168.95.8 dbname=postfix_masterdb user=postfi...

..._rule = *:storage=1048576 # quota_rule2 = Trash:storage=102400 # User has now 1GB quota, but when saving to Trash mailbox the user gets # additional 100MB. # # Multiple quota roots are also possible, for example: # quota = dict:user::proxy::quota # quota2 = dict:domain:%d:proxy::quota_domain # quota_rule = *:storage=102400 # quota2_rule = *:storage=1048576 # Gives each user their own 100MB quota and one shared 1GB quota within # the domain. # # You can execute a given command when user exceeds a specified quota limit. # Each quota root has separate limits. Only the co...