similar to: New feature: HTTP API

> On April 5, 2016 at 12:24 PM aki.tuomi at dovecot.fi wrote: > > > > > On April 5, 2016 at 9:57 AM Tom Sommer <mail at tomsommer.dk> wrote: > > > > > > 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-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 all, It seems that setting userMask in the doveadm http api's "user" command to anything involving wildcards ?s or *s causes the API to fail. When using the API with a userMask set to the fully qualified email address, I get the expected fields back. From a python shell, with an asterisk causes the following behaviour (note that doveadm is a python module that wrappers the

Trying to limit the API calls to doveadm-http-api by configure allowed commands, but once the commands added to the list, the RestAPI no longer work. 1) Return correct reply when doveadm_allowed_commands is empty # curl -k -H "Content-Type: application/json" -H "Authorization: X-Dovecot-API <base64 api key>" https://localhost:9088/doveadm/v1

> 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

Thanks for the new HTTP API. I get the API with some commands up and running, but I'm still not able to create folder. curl -k -H "Content-Type: application/json" -H "Authorization: Basic secret" -d '[["mailboxCreate",{"user":"user at example.org","mailbox":["INBOX/TEST"]},c01]]'

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

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

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

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

I have Poolmon (https://github.com/brandond/poolmon) set up. When it does all the checks concurrently, obviously there are locking issues on each mailserver it tests: "Warning: Locking transaction log file xxxx/indexes/dovecot.list.index.log took 60 seconds (syncing)" It's just an empty mailbox. Is there any way to do a login test, without locking the index files? Hence

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 29 Jun 2018, at 15.05, Tom Sommer <mail at tomsommer.dk> wrote: > > On 2018-06-29 14:51, Timo Sirainen wrote: > >> v2.3.2 is mainly a bugfix release. It contains all the changes in >> v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only >> bugs). Binary packages are already in https://repo.dovecot.org/ > > A simple "yum update"

I could use an example of how to use curl to save a new message to a user?s INBOX using the Doveadm HTTP API. https://wiki2.dovecot.org/Design/DoveadmProtocol/HTTP <https://wiki2.dovecot.org/Design/DoveadmProtocol/HTTP> Do I really use the -d option and inline the entire new message in the command-line? Or, should I create a temporary .json file with the message wrapped in JSON and pass

I know, but I'm changing the quota in dict:sql so running commands on the mailserver itself it something I would like to avoid. --- Tom On 2017-02-06 14:29, Urban Loesch wrote: > You can flush the cache with: "doveadm auth cache flush $USER" > > Regards > Urban > > > Am 06.02.2017 um 13:59 schrieb Tom Sommer: >> I have my quota limits stored in userdb

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

> On May 1, 2017 at 8:26 PM Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > > > On May 1, 2017 at 8:21 PM Tom Sommer <mail at tomsommer.dk> wrote: > > > > > > I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg > > and /var/log/messages are getting flooded by these errors: > > > > lmtp[45758]: segfault at

Hello Tom On 02.05.2017 11:19, Timo Sirainen wrote: > On 2 May 2017, at 10.41, Tom Sommer <mail at tomsommer.dk> wrote: >> >> (gdb) bt full >> #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298 >> _stream = <value optimized out> >> #1 0x00007fe98391ff32 in i_stream_concat_read_next (stream=0x1efe6c0) at istream-concat.c:77 >>

On 2017-05-02 09:35, Aki Tuomi wrote: > On 2017-05-02 10:20, Tom Sommer wrote: >> On 2017-05-01 19:26, Aki Tuomi wrote: >>>> On May 1, 2017 at 8:21 PM Tom Sommer <mail at tomsommer.dk> wrote: >>>> >>>> >>>> I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my >>>> dmesg >>>> and /var/log/messages