similar to: v2.2.22 released

http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz.sig There are some larger changes here, especially to doveadm to make it support HTTP API. There's still time to do smaller tweaks to the API, so let us know if you have some improvement ideas. Note that the API was designed to look mostly like JMAP, which we're

http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz.sig There are some larger changes here, especially to doveadm to make it support HTTP API. There's still time to do smaller tweaks to the API, so let us know if you have some improvement ideas. Note that the API was designed to look mostly like JMAP, which we're

In future release we will add master authentication too. Now you can use api key or doveadm password which are essentially same thing. ---Aki TuomiDovecot oy-------- Alkuper?inen viesti --------L?hett?j?: Peter Chiochetti <pch at myzel.net> P?iv?m??r?: 4.3.2016 20.20 (GMT+02:00) Saaja: dovecot at dovecot.org Aihe: Re: v2.2.22 release candidate released Am 2016-03-04 um 14:33 schrieb Timo

Always I have the following lines in my mail.log (at startup and service restart) dovecot: master: Warning: Killed with signal 15 (by pid=3156 uid=0 code=kill) dovecot: log: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) dovecot: master: Dovecot v2.2.22 (fe789d2) starting up for imap, pop3 (core dumps disabled) dovecot -n output is below: # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf

Hi. Always the below log appraring log under /var/log/mail.log Is this right or How to resolve it. Ubuntu 16.04.2 LTS server edition Mar 13 06:13:20 home dovecot: master: Dovecot v2.2.22 (fe789d2) starting up for imap, pop3 (core dumps disabled) Mar 13 06:13:30 home postfix/master[1495]: daemon started -- version 3.1.0, configuration /etc/postfix dovecot -n output

So after about 4 hours struggling with Try and TryCatch I am throwing in the towel. I have a more complicated function that used logspline through iterative distributions and at some point the logspline doesnt function correctly for some subsets but is fine with others so I need to be able to identify when the error occurs and stop curtailing the distribution and I think this Try or TryCatch

Hello Dovecot users, Pigeonhole v0.4.12 still compiles against Dovecot v2.2.22.rc1, but only with warnings. That is the primary reason for this new release. However, there are also a few significant changes as listed below. When no significant problems are reported, a definitive release will follow closely after Dovecot v2.2.22 is released. Changelog v0.4.13: * redirect action: Added the

Hello Dovecot users, Pigeonhole v0.4.12 still compiles against Dovecot v2.2.22.rc1, but only with warnings. That is the primary reason for this new release. However, there are also a few significant changes as listed below. When no significant problems are reported, a definitive release will follow closely after Dovecot v2.2.22 is released. Changelog v0.4.13: * redirect action: Added the

Hello Dovecot users, Here is the final v0.4.13 release of Pigeonhole for Dovecot v2.2.22. Nothing changed since the RC. Changelog v0.4.13: * redirect action: Added the list-id header to the duplicate ID for mail loop prevention. This means that the message sent directly to the user and the message coming through the mailing list itself are treated as different messages by the loop

Hello Dovecot users, Here is the final v0.4.13 release of Pigeonhole for Dovecot v2.2.22. Nothing changed since the RC. Changelog v0.4.13: * redirect action: Added the list-id header to the duplicate ID for mail loop prevention. This means that the message sent directly to the user and the message coming through the mailing list itself are treated as different messages by the loop

Hi Aki, thank your for responding that fast. aki.tuomi at dovecot.fi <aki.tuomi at dovecot.fi> (Mo 30 Mai 2016 17:49:53 CEST): ? > Hi! This has been fixed in 2.2.24. There was a bug in user passing. Ok, thus at least your answer saves me hours of debugging. We upgraded old Ubuntu Boxes (14.04/LTS) to 16.04 to get around some Dovecot limitations/problems. And now we got new ones :( We

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

Hi, I think that using more than one userdb with setting the result actions doesn't work as expected from the documentation. The goal would be to set user-specific quotas for a few users with a specific passwd-file like this : cat /etc/dovecot/quotas foo:x::::::userdb_quota_rule=*:storage=2G The first userdb is passwd (with pam passwd): userdb { driver = passwd result_failure =

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 stable in 2.2.34 please? The wiki says it is "considered experimental in v2.2.22" so I thought I'd check before writing API calls rather than a wrapper around doveadm! -- James Beck Andrews & Arnold Ltd Tel: 03333 400999

I'm trying to understand autoexpunge, but the documentation is just not clear. Hopefully, someone can clear up a few questions. http://wiki.dovecot.org/MailboxSettings says the following: autoexpunge=<time>: (v2.2.20+) Automatically at user deinitialization expunge all mails in this mailbox whose saved-timestamp is older than <time> (e.g. autoexpunge=30d). This removes the

Hi, I'm doing quota checks from a remote machine (the real setup is a bit more complex, if necessary I can explain it in more detail, but I just extracted the bits that are easily reproduceable) # nc backend1 24245 VERSION doveadm-server 1 0 PLAIN agrVMDvHgz0ya2HHzax5svwB2ZHS? + heiko quota get But since the backend is upgraded to 2.2.22 it's not

Dear All, I'm using version 2.1.7 which currently ships with debian stable. I'd like to use userdb { driver = passwd-file args = username_format=%n /etc/dovecot/users default_fields = uid=vmail gid=vmail override_fields = skip = never result_failure = continue result_internalfail = continue result_success = return-ok } from [1]. The error message is: Jan 25

> On 16 Nov 2016, at 13:32, soumitri at iitk.ac.in wrote: > > Hi, > > Thanks for the reply. I guess RHEL choose v2.2.10 <http://dovecot.org/list/dovecot-news/2013-December/000268.html> as it is a good release with all the things working. > > My source of confusion are from > 1) http://dovecot.org/oldnews.html <http://dovecot.org/oldnews.html> > I have

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

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