dovecot - May 2017 - No doveadm-save in wiki2?

> On May 10, 2017, at 9:50 AM, Sami Ketola <sami.ketola at dovecot.fi>
wrote:
> 
> 
>> On 9 May 2017, at 19.26, KT Walrus <kevin at my.walr.us> wrote:
>> 
>> Is ?doveadm save? an undocumented feature? Or, just well-hidden?
>> 
>> https://wiki2.dovecot.org/Tools/Doveadm
<https://wiki2.dovecot.org/Tools/Doveadm>
> 
> That wikipage is autogenerated from the doveadm manpage? which
unfortunately lags behind on the features. We?ll try to update the manpage
eventually some day.
How long does this usually take? Googling the topic seems to indicate that this
feature was implemented several years ago.

I?m looking to use the Doveadm HTTP API for new message delivery (thus needing
to use the ?doveadm save? feature). Is the Doveadm HTTP API still experimental?
The wikipage doesn?t seem to have adequate documentation on using this API with
just a single ?fetch? example using curl.

Kevin

> On 10 May 2017, at 15.06, KT Walrus <kevin at my.walr.us> wrote:
> 
> 
>> On May 10, 2017, at 9:50 AM, Sami Ketola <sami.ketola at
dovecot.fi> wrote:
>> 
>> 
>>> On 9 May 2017, at 19.26, KT Walrus <kevin at my.walr.us>
wrote:
>>> 
>>> Is ?doveadm save? an undocumented feature? Or, just well-hidden?
>>> 
>>> https://wiki2.dovecot.org/Tools/Doveadm
<https://wiki2.dovecot.org/Tools/Doveadm>
>> 
>> That wikipage is autogenerated from the doveadm manpage? which
unfortunately lags behind on the features. We?ll try to update the manpage
eventually some day.
> 
> How long does this usually take? Googling the topic seems to indicate that
this feature was implemented several years ago.
Seems that we have been quite busy on working on more important issues. Also
it?s possible that we just forgot to update the manpage.

> I?m looking to use the Doveadm HTTP API for new message delivery (thus
needing to use the ?doveadm save? feature). Is the Doveadm HTTP API still
experimental? The wikipage doesn?t seem to have adequate documentation on using
this API with just a single ?fetch? example using curl.
It is already widely used so ?experimental? is probably incorrect wording here.

Sami

> On May 10, 2017, at 10:18 AM, Sami Ketola <sami.ketola at dovecot.fi>
wrote:
> 
>> 
>> On 10 May 2017, at 15.06, KT Walrus <kevin at my.walr.us> wrote:
>> 
>> 
>>> On May 10, 2017, at 9:50 AM, Sami Ketola <sami.ketola at
dovecot.fi> wrote:
>>> 
>>> 
>>>> On 9 May 2017, at 19.26, KT Walrus <kevin at my.walr.us>
wrote:
>>>> 
>>>> Is ?doveadm save? an undocumented feature? Or, just
well-hidden?
>>>> 
>>>> https://wiki2.dovecot.org/Tools/Doveadm
<https://wiki2.dovecot.org/Tools/Doveadm>
>>> 
>>> That wikipage is autogenerated from the doveadm manpage? which
unfortunately lags behind on the features. We?ll try to update the manpage
eventually some day.
>> 
>> How long does this usually take? Googling the topic seems to indicate
that this feature was implemented several years ago.
> 
> Seems that we have been quite busy on working on more important issues.
Also it?s possible that we just forgot to update the manpage.
Thanks. I don?t mean to have you change your priorities, but it is difficult to
really understand how to set up and use Dovecot with incomplete user
documentation. For example, I had to search for a half hour to figure out how to
set an API key to use with the Doveadm HTTP API. I finally noticed the single
reference to ?doveadm_api_key? in the Design.DoveadmProtocol.HTTP.txt file. I
should have noticed it much sooner, but I was looking in the example-config
files for how to configure doveadm and couldn?t find its settings there. In
fact, there should be a ?How to configure doveadm? page.

I also have plans to deploy using 3 server clusters. Maybe it isn?t a good idea,
but I haven?t really found much on how to set up a 3 server cluster that keeps
the local storage sync?d between all 3 servers. Maybe this is obvious to most,
but the documentation only really goes into depth on how to dsync 2 servers. I
guess it is natural to expect to just set up 3 servers with each server
dsync?ing to the 2 other servers in the cluster, but I worry that this might not
work best in production and I should look into using converged storage so each
server in the cluster has read/write access to the converged storage and I make
sure that no 2 servers access the same mailbox at the same time.

I want to deploy in 3 server clusters since this is the way we deploy MySQL
database clusters and this works well in production. But, maybe, for Dovecot, 2
server clusters is enough for production and going to 3 servers is just a waste
of money. We do not use RAID storage on our local servers preferring to use
replication to 3 separate servers in 3 separate racks to take care of the
occasional hardware failures. So, the general rule is that all persistent data
is replicated 3 times. Maybe, for Dovecot, we should deploy 2 server clusters
with btrfs/rsync backup to a third backup only server.

Anyway, I?m highjacking my own thread in discussing these production issues, but
maybe you and your team could consider bumping up the priority on documentation
just a bit in the future?

Thanks again,

Kevin