similar to: quota-service with Director - A workaround

On 2019-03-20 16:40, Sami Ketola via dovecot wrote: >> On 20 Mar 2019, at 17.13, Tom Sommer via dovecot <dovecot at dovecot.org> >> wrote: >> >> I realize quota-service on Director is not supported, which is a >> shame. >> >> As a workaround I'm thinking of setting up quota-service on one of my >> backend nodes, and have all my

On 2019-03-21 10:28, Sami Ketola via dovecot wrote: >> On 20 Mar 2019, at 18.17, Tom Sommer via dovecot <dovecot at dovecot.org> >> wrote: >> >> >> On 2019-03-20 16:40, Sami Ketola via dovecot wrote: >> >>>> On 20 Mar 2019, at 17.13, Tom Sommer via dovecot >>>> <dovecot at dovecot.org> wrote: >>>> I realize

> On 20 Mar 2019, at 17.13, Tom Sommer via dovecot <dovecot at dovecot.org> wrote: > > I realize quota-service on Director is not supported, which is a shame. > > As a workaround I'm thinking of setting up quota-service on one of my backend nodes, and have all my Postfix services ask this one node for the quota status. > > This sort of defeats the purpose of the

> On 20 Mar 2019, at 18.17, Tom Sommer via dovecot <dovecot at dovecot.org> wrote: > > > On 2019-03-20 16:40, Sami Ketola via dovecot wrote: > >>> On 20 Mar 2019, at 17.13, Tom Sommer via dovecot <dovecot at dovecot.org> wrote: >>> I realize quota-service on Director is not supported, which is a shame. >>> As a workaround I'm thinking of

On 2018-10-05 11:35, Timo Sirainen wrote: > On 4 Oct 2018, at 17.13, Tom Sommer <mail at tomsommer.dk> wrote: >> >> >> On 2018-10-04 15:55, Timo Sirainen wrote: >>> On 4 Oct 2018, at 14.39, Tom Sommer <mail at tomsommer.dk> wrote: >> >>>> Is this correct, and if so are there any plans to move dotlocks etc. >>>> to this

On 2018-10-04 15:55, Timo Sirainen wrote: > On 4 Oct 2018, at 14.39, Tom Sommer <mail at tomsommer.dk> wrote: >> Is this correct, and if so are there any plans to move dotlocks etc. >> to this directory? > > > What dotlocks? I guess mbox and Maildir have some locks that could be > moved there, but a better performance optimization for those > installations

On 07 Apr 2016, at 14:49, Tom Sommer <mail at tomsommer.dk> wrote: > > On 2016-04-06 21:09, Tom Sommer wrote: >> On 2016-04-06 20:38, Timo Sirainen wrote: >>> On 06 Apr 2016, at 13:43, Tom Sommer <mail at tomsommer.dk> wrote: >>>> I'm switching quota backend to redis (from maildir++), so all my current usages are reset. >>>> I get that

On 2016-04-06 20:38, Timo Sirainen wrote: > On 06 Apr 2016, at 13:43, Tom Sommer <mail at tomsommer.dk> wrote: >> >> I'm switching quota backend to redis (from maildir++), so all my >> current usages are reset. >> >> I get that I can do "doveadm quota recalc -A", but it takes forever >> (and auth processes time out/crash). >>

Hello, I'm trying to configure the quota-status service, but it seems I'm not successful with my director setup (2.2.9). I activate the quota-status service like this on my director server: $ cat 91-quota-status.conf ## ## Quota-Status configuration. ## # Load Module quota-status and listen on TCP/IP Port for connections. service quota-status { ? executable = quota-status -p postfix ?

Hi! quota-status is not supported in proxy configuration. You should use quota_warning and quota_over_flag scripts instead. Aki On 08.10.2016 03:51, Michael Kliewe wrote: > Hello, > any news on this topic? I tried it again with Dovecot 2.2.25, but it's > still not possible to run the quota-status services on the directors. > They try to access the mailbox of the user, which they

I'm switching quota backend to redis (from maildir++), so all my current usages are reset. I get that I can do "doveadm quota recalc -A", but it takes forever (and auth processes time out/crash). It would make much more sense to recalc the usage on login if the current usage is unset. Is there no way to do a recalc-quota-on-first-login? Thanks. -- Tom Sommer

Mar 19 16:54:37 lmtp(xxxx at xxx.xxx): Panic: file file-lock.c: line 269: unreached Mar 19 16:54:37 lmtp(xxxx at xxx.xxx): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x35f647e07a] -> /usr/lib/dovecot/libdovecot.so.0 [0x35f647e0e6] -> /usr/lib/dovecot/libdovecot.so.0 [0x35f647d4ac] -> /usr/lib/dovecot/libdovecot.so.0 [0x35f6481edf] ->

My director has started segfaulting since upgradeing to 2.3.2: # gdb /usr/libexec/dovecot/imap-login ./core.9757 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the

On 2016-04-06 20:27, Timo Sirainen wrote: > On 06 Apr 2016, at 16:54, Tom Sommer <mail at tomsommer.dk> wrote: >> >> Sometimes my redis connection times out, both for pop3, imap and lmtp. >> I have no idea why, when I do a "doveadm quota recalc -u" it works >> just fine? >> I'm thinking the connection is lost somehow and not retried? >>

Sometimes my redis connection times out, both for pop3, imap and lmtp. I have no idea why, when I do a "doveadm quota recalc -u" it works just fine? I'm thinking the connection is lost somehow and not retried? Apr 06 15:42:00 lmtp(xxx at xxx.com): Error: redis: Lookup timed out in 30.000 secs Apr 06 15:42:00 lmtp(xxx at xxx.com): Error: Internal quota calculation error Apr 06

On 2016-04-05 08:44, aki.tuomi at dovecot.fi wrote: >> On April 5, 2016 at 9:27 AM Tom Sommer <mail at tomsommer.dk> wrote: >> >> >> On 2016-04-04 20:22, aki.tuomi at dovecot.fi wrote: >> >> > Since the API is still a little beta, it will not return anything in >> > case >> > doveadm does not like the arguments (that is, calls

Hi I am seeing a lot of clients time out on my Director. I'm wondering if this is "normal" or there is some opportunity to tweak something? Log line: imap-login: Info: proxy(user at example.com): disconnecting 1.2.3.4 (Disconnected by client: read(size=433) failed: Connection timed out(37s idle, in=939, out=3083)): user=<user at example.com>, method=CRAM-MD5, rip=1.2.3.4,

On Mon, 22 Oct 2018 19:48:17 +0200 Tom Sommer <mail at tomsommer.dk> wrote: > On 2018-10-22 12:56, Mar?a Arrea wrote: > > > We use sabredav for caldav+cardav and roundcube+agendav for nice > > web ui :) > > > Is Sabre still maintained? http://sabre.io/ says 2018 is most recent version -- In modern fantasy (literary or governmental), killing people is the

> On May 2, 2016 at 9:56 AM Tom Sommer <mail at tomsommer.dk> wrote: > > > > On 2016-04-29 16:25, Matteo Gaito Test Account wrote: > > > i've search a lot in order to find a way to delete account by dovecot > > but i > > found only this way > > > > http://dovecot.org/list/dovecot/2011-November/079273.html > > > > It's

I upgraded to beta7 from alpha4, and got this error during the auth process: dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=0.0.0.0 rip=0.0.0.0 resp=<hidden> dovecot: auth-worker(default): sql(webmaster at example.com,0.0.0.0): query: SELECT username as user, NULL as password FROM users WHERE username = 'webmaster at example.com' AND