similar to: Heads-up regarding non-replication of Sieve scripts?

Hi, Now that we have a new Dovecot v2.3 release, I've created a new Xi builder that follows the git master branch to automatically produce Debian packages for the future Dovecot v2.4. The existing v2.3 repository now follows the master-2.3 branch, meaning that this will only follow developments/fixes ported to the v2.3 stable release series. This was already true for the v2.2 oldstable

On 03/11/2017 11:48, Stephan Bosch wrote: > Hi, > > Sorry, we're in a bit of a v2.3 merge frenzy. Much of the LMTP code will be > replaced in v2.3, but I'll give the? older code a look as well. > > This can take a while though. Thank you very much for getting back to me, I can appreciate it can get hectic, and I don't wish to appear ungrateful, I wholeheartedly

Two items I forgot to mention in my initial post: (A) I am running the sync command on the new v2.3 server. (B) To get sync to work, I had to add the following to the old v2.2 server: auth_socket_path = /var/run/dovecot/auth-master I think this relates to what I said in my initial post about AWS linux installing all of the sockets into a non-standard location. I say this because when I was

The git master branch starts tracking Dovecot v2.3 development from now on. There are soon going to be several API changes there that might break plugins. If you wish to keep tracking latest v2.2.x development instead, switch to master-2.2 branch. The nightly releases at http://dovecot.org/nightly/ will also track v2.3 tree.

The git master branch starts tracking Dovecot v2.3 development from now on. There are soon going to be several API changes there that might break plugins. If you wish to keep tracking latest v2.2.x development instead, switch to master-2.2 branch. The nightly releases at http://dovecot.org/nightly/ will also track v2.3 tree.

So, I'm still planning on getting v2.2.0 out Really Soon now. Unfortunately I've had to quickly develop some rather large features still at this stage. I was initially planning on leaving them for v2.3, but they were a requirement for one project and implementing them now to v2.2 was the least amount of trouble for me. (And yes, I'm aware I haven't replied to a lot of emails in

On Tuesday 08 of December 2015, Gerhard Wiesinger wrote: > On 07.12.2015 20:13, Timo Sirainen wrote: > > http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz > > http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig > > > > This could be (one of) the last v2.2.x release. We're starting v2.3 > > development soon. > > Great! > > What's on

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"

Op 3/1/2018 om 2:07 PM schreef Philipp Berger: > Dear all, > > I have a working setup with Postfix + Dovecot, storing users in a MySQL > table. > > I ran into problems setting up and using a mail address like > a"@"b at mydomain.tld, which by RFC should be valid, but leads to problems > in Dovecot. From my debugging, I can see that on the lookup, Dovecot >

On 29 Jun 2018, at 15.28, Tom Sommer <mail at tomsommer.dk> wrote: > > On 2018-06-29 15:20, Timo Sirainen wrote: >> 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

http://dovecot.org/releases/2.2/dovecot-2.2.2.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.2.tar.gz.sig It's been a while since v2.2.1. I think all of the bad bugs in v2.2 series should be fixed by now, so here's a new release. I think there are still some small URLAUTH bugs left though, so you might want to wait before enabling it in production (imap_urlauth_host is empty by

http://dovecot.org/releases/2.2/dovecot-2.2.2.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.2.tar.gz.sig It's been a while since v2.2.1. I think all of the bad bugs in v2.2 series should be fixed by now, so here's a new release. I think there are still some small URLAUTH bugs left though, so you might want to wait before enabling it in production (imap_urlauth_host is empty by

Op 6-3-2018 om 14:34 schreef Philipp Berger: > I upgraded to Dovecot 2.3.0.1 as advised, but it still seems broken. In > the Postfix log I now see: > > Mar? 6 13:49:03 myhost amavis[7165]: (07165-10) K00VtLRHdrYw FWD from > <admin at mydomain.tld> -> <"@"@mydomain.tld>, BODY=7BIT 250 2.0.0 from > MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as

https://dovecot.org/releases/2.2/dovecot-2.2.33.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.33.tar.gz.sig We're getting close to the last v2.2.x releases. Hopefully we'll have the first v2.3 beta releases out soon. * doveadm director commands wait for the changes to be visible in the whole ring before they return. This is especially useful in testing. * Environments listed

https://dovecot.org/releases/2.2/dovecot-2.2.33.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.33.tar.gz.sig We're getting close to the last v2.2.x releases. Hopefully we'll have the first v2.3 beta releases out soon. * doveadm director commands wait for the changes to be visible in the whole ring before they return. This is especially useful in testing. * Environments listed

I've been planning on adding these for years. Maybe it's about time soon. I guess they could be added already to v2.2, but enabled only by a new setting because it requires file format changes that old Dovecots can't then read. I could probably patch v2.1 also so it is able to at least read the new format without failing. For v2.3 this new format could then be made the default. And

My understanding of the man page description of --exclude vs. --include is that the list of these is kept in order, and file names are searched against these parameters in that order for the first that matches and that one makes the decision. It doesn't seem to be working exactly as expected. But there is a factor involved that's making it unclear, which is whether or not *'s should

Op 7-3-2018 om 13:46 schreef Philipp Berger: > I wrapped the LDA command in a script. I can see that Postfix passes > "@@mydomain.tld" as the -d argument, without quotes. > I then adapted the script to specifically replace this address with > "@"@mydomain.tld, but this results in the following error message by > Dovecot: > > ??? auth: Info: userdb(?):

http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig This could be (one of) the last v2.2.x release. We're starting v2.3 development soon. + Added mailbox { autoexpunge=<time> } setting. See http://wiki2.dovecot.org/MailboxSettings for details. + ssl_options: Added support for no_ticket + imap/pop3/managesieve-login:

http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig This could be (one of) the last v2.2.x release. We're starting v2.3 development soon. + Added mailbox { autoexpunge=<time> } setting. See http://wiki2.dovecot.org/MailboxSettings for details. + ssl_options: Added support for no_ticket + imap/pop3/managesieve-login: