On 07.03.2017 11:08, Aki Tuomi wrote:
>
> On 07.03.2017 10:52, Nagy, Attila wrote:
>> On 03/06/2017 11:30 PM, Timo Sirainen wrote:
>>> On 6 Mar 2017, at 9.17, Tom Sommer wrote:
On 2017-02-24 14:34, Timo Sirainen wrote:
>
On 03/07/2017 02:41 PM, Robert L Mathews wrote:
> As a result, I
> end up using what seems to be a mostly stable version, plus "extra
> patches I grabbed from reading the mailing list".
Pretty sure that's what the dovecot enterprise repo is.
On 3/6/17 2:30 PM, Timo Sirainen wrote:
> I don't see anything critical. A couple of bugs that might or might
> not affect you. We'll have 2.2.29 soon enough, so no plans for other
> releases before that.
As a comment: When trying to choose which version of Dovecot to use in
production, I've
On 07.03.2017 10:52, Nagy, Attila wrote:
> On 03/06/2017 11:30 PM, Timo Sirainen wrote:
>> On 6 Mar 2017, at 9.17, Tom Sommer wrote:
>>>
>>> On 2017-02-24 14:34, Timo Sirainen wrote:
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz
On 03/06/2017 11:30 PM, Timo Sirainen wrote:
On 6 Mar 2017, at 9.17, Tom Sommer wrote:
On 2017-02-24 14:34, Timo Sirainen wrote:
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig
Are there any plans to do a
On 6 Mar 2017, at 9.17, Tom Sommer wrote:
>
>
> On 2017-02-24 14:34, Timo Sirainen wrote:
>> http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz
>> http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig
>
> Are there any plans to do a bugfix-release, that includes the
On 2017-02-24 14:34, Timo Sirainen wrote:
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig
Are there any plans to do a bugfix-release, that includes the few issues
seen in the mailing-list, or do you consider 2.2.28 safe to
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig
* director: "doveadm director move" to same host now refreshes user's
timeout. This allows keeping user constantly in the same backend by
just periodically moving the user there.
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig
* director: "doveadm director move" to same host now refreshes user's
timeout. This allows keeping user constantly in the same backend by
just periodically moving the user there.