similar to: Feature request: additional commands for doveadm HTTP API

I have switched to global ACLs for public namespaces which eases their administration greately. Now while running housekeeping scripts (e.g. expunge old mails/archive mails etc.) this requires temporary overriding the global ACLs with mailbox specifix ACLs to expunge mails. The scripts would then revoke the temporary changes (delete flags) and the global ACL would take precedence again. Ideally I

Yeah. This is a bug, there is a fix pending. >From bb200128c83610d213b2ff2e59f1e0440ecbd2c9 Mon Sep 17 00:00:00 2001 From: Aki Tuomi <aki.tuomi at dovecot.fi> Date: Tue, 18 Sep 2018 20:37:38 +0300 Subject: [PATCH] doveadm: Fix doveadm user output when called from server Was forgotten in a13b1245bee0b6524b4aeb3c8fd9e34af648b746 --- src/doveadm/doveadm-auth-server.c | 6 +++++- 1 file

> On 10 May 2017, at 14.57, KT Walrus <kevin at my.walr.us> wrote: > > 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. > Here you go: doveadm mailbox save parameters: { "command": "save", "parameters": [ { "name": "allUsers",

> On 10 May 2017, at 16.26, KT Walrus <kevin at my.walr.us> wrote: >> >> # curl -v -X POST -u doveadm:hellodoveadm -H "Content-Type: application/json" -d '[["save",{"user":"samik","mailbox":"INBOX/myfoldertoo","file":"From: Joulu Pukki <joulu.pukki at korvatunturi.fi>\nSubject: plaa\n\nmail

While toying around with Doveadmin HTTP api I noticed, there is not much hype around it. Let's change that. Doveadmin REST API so to speak provides a web server. When doing /ajax/ requests, modern browsers block that, unless the response comes with a specific CORS header. Here how to work around with a proxy: > # /etc/dovecot/local.conf > doveadm_allowed_commands = fetch >

I?m trying out the the doveadm http api for the first time. When I do: $ curl -H "Authorization: Basic <base64 doveadm:doveadm_password>" http://localhost:8888 curl: (52) Empty reply from server In the logs, I see the following error: May 09 11:58:05 doveadm(10.0.0.17): Error: doveadm client not compatible with this server (mixed old and new binaries?) I am running Dovecot

> On May 10, 2017, at 5:16 PM, Sami Ketola <sami.ketola at dovecot.fi> wrote: > > >> On 10 May 2017, at 16.26, KT Walrus <kevin at my.walr.us> wrote: >>> >>> # curl -v -X POST -u doveadm:hellodoveadm -H "Content-Type: application/json" -d

> On May 10, 2017, at 11:06 AM, Sami Ketola <sami.ketola at dovecot.fi> wrote: > > >> On 10 May 2017, at 14.57, KT Walrus <kevin at my.walr.us> wrote: >> >> 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. >> > > Here you go: > > doveadm mailbox save > > parameters:

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

Hi, In case you are interested in testing the Doveadm HTTP API in a bit more simplified fashion I have written a client for it in Python. Feedback is always appreciated (pull requests more appreciated). https://github.com/hnsk/doveadm-http-cli <https://github.com/hnsk/doveadm-http-cli> -Hannu

> On Aug 23, 2018, at 8:14 AM, James Beck <james.beck at aa.net.uk> wrote: > >> On Wed, Aug 22, 2018 at 09:54:44AM -0400, Felipe Gasper wrote: >> If you don?t want to use the HTTP API, you can use the raw doveadm protocol. >> >> https://wiki.dovecot.org/Design/DoveadmProtocol >> >> -FG > > Thanks, I didn't know about that. I suppose

> On Aug 23, 2018, at 8:44 AM, Reio Remma <reio at mrstuudio.ee> wrote: > > On 23.08.18 15:35, Felipe Gasper wrote: >> >>> On Aug 23, 2018, at 8:14 AM, James Beck <james.beck at aa.net.uk> wrote: >>> >>>> On Wed, Aug 22, 2018 at 09:54:44AM -0400, Felipe Gasper wrote: >>>> If you don?t want to use the HTTP API, you can use the

On Wed, Aug 22, 2018 at 09:54:44AM -0400, Felipe Gasper wrote: > If you don?t want to use the HTTP API, you can use the raw doveadm protocol. > > https://wiki.dovecot.org/Design/DoveadmProtocol > > -FG Thanks, I didn't know about that. I suppose testing the HTTP API and then switching to the raw doveadm protocol over TCP if it turns out "crashy" wouldn't mean

On 23.08.18 15:35, Felipe Gasper wrote: > >> On Aug 23, 2018, at 8:14 AM, James Beck <james.beck at aa.net.uk> wrote: >> >>> On Wed, Aug 22, 2018 at 09:54:44AM -0400, Felipe Gasper wrote: >>> If you don?t want to use the HTTP API, you can use the raw doveadm protocol. >>> >>> https://wiki.dovecot.org/Design/DoveadmProtocol >>>

If you don?t want to use the HTTP API, you can use the raw doveadm protocol. https://wiki.dovecot.org/Design/DoveadmProtocol -FG > On Aug 22, 2018, at 5:55 AM, James Beck <james.beck at aa.net.uk> wrote: > > Hi, > > I'm running 2.2.34 in production (installed from Debian stretch > backports) and want to rework some scripts. Can the HTTP API be > considered

Does doveadm http api have high execution efficiency? I have a program that directly calls doveadm http api. Will there be an efficiency problem if a large number of users call it? hfh at cndns.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20201021/15923f8a/attachment.html>

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

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

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

Can someone please explain to me what do commands "doveadm replicator add" and "doveadm replicator remove" really do. According to https://wiki.dovecot.org/Tools/Doveadm/Replicator they "Add the specified user(s) to the replicator." and "Remove the specified user from replicator.". Do they really do that? Since the default list of users for replication