similar to: v2.2.17 release candidate released

Displaying 20 results from an estimated 2000 matches similar to: "v2.2.17 release candidate released"

2015 May 09
2
v2.2.17 release candidate released
On Sat, 9 May 2015 22:17:27 +0200, Michael Grimm stated: >Hi ? > >Timo Sirainen <tss at iki.fi> wrote: > >> Please test especially non-Linux systems as there are some larger >> configure/Makefile changes done since v2.2.16. > >2.2.17.rc1 will compile on FBSD 10.1 only, if bash has been installed (see ><554773D2.9060609 at dovecot.fi> from Teemu
2015 May 10
2
v2.2.17 release candidate released
> Michael Grimm <trashcan at odo.in-berlin.de> kirjoitti 9.5.2015 kello 23.17: > > Hi ? > > Timo Sirainen <tss at iki.fi> wrote: > >> Please test especially non-Linux systems as there are some larger configure/Makefile changes done since v2.2.16. > > 2.2.17.rc1 will compile on FBSD 10.1 only, if bash has been installed Dovecot hg requires bash
2016 Aug 31
2
2.2.25 dumps core with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)"
Hello Timo, from the maintainer of the OpenCSW package I got the below answer. As the newly build package yields another different commit hash (which I cannot find on GitHub too), I would ask, if you are sure that the commit hash-output in 'doveconf -n' is generated correctly? The headline of 'doveconf -n' with the newly build package is # 2.2.25 (68082dc):
2015 Apr 28
3
CVE-2015-3420
On 28 Apr 2015, at 11:35, Timo Sirainen <tss at iki.fi> wrote: > > On 28 Apr 2015, at 04:15, Edwardo Garcia <wdgarc88 at gmail.com> wrote: >> When can we expect 2.2.17 to resolve this? > > As far as I know this doesn't affect any of the major distributions where Dovecot is commonly used (Debian/Ubuntu/Redhat/CentOS). I've only heard it happening with some
2015 May 10
2
v2.2.17 release candidate released
On 10 May 2015, at 06:19, Reuben Farrelly <reuben-dovecot at reub.net> wrote: > > I'm now seeing these crashes in the indexing code: > > May 10 12:22:32 tornado.reub.net dovecot: master: Dovecot v2.2.17.rc1 (3903badc4ee0+) starting up for imap, lmtp, sieve > ... > May 10 13:07:50 tornado.reub.net dovecot: indexer: Error: Indexer worker disconnected, discarding 1
2015 May 10
5
Released Pigeonhole v0.4.8.rc1 for Dovecot v2.2.17.rc1
Hello Dovecot users, Here's the Pigeonhole RC that goes with the Dovecot RC. It includes a few small fixes and one new feature. Changelog v0.4.8.rc1: * LDA Sieve plugin: Dovecot changed the deliver_log_format setting to include %{delivery_time}. This prompted changes in Pigeonhole that make this release dependent on Dovecot v2.2.17. + Implemented magic to make sieve_default script
2015 May 10
5
Released Pigeonhole v0.4.8.rc1 for Dovecot v2.2.17.rc1
Hello Dovecot users, Here's the Pigeonhole RC that goes with the Dovecot RC. It includes a few small fixes and one new feature. Changelog v0.4.8.rc1: * LDA Sieve plugin: Dovecot changed the deliver_log_format setting to include %{delivery_time}. This prompted changes in Pigeonhole that make this release dependent on Dovecot v2.2.17. + Implemented magic to make sieve_default script
2015 May 09
0
v2.2.17 release candidate released
Hi ? Timo Sirainen <tss at iki.fi> wrote: > Please test especially non-Linux systems as there are some larger configure/Makefile changes done since v2.2.16. 2.2.17.rc1 will compile on FBSD 10.1 only, if bash has been installed (see <554773D2.9060609 at dovecot.fi> from Teemu Huovila). This is from my point of view regarding portability issues "suboptimal". Both,
2013 Sep 27
1
version 2.2.6 breaks compiling on Solaris 10 sparc
Hello, I maintain the dovecot package at opencsw.org. The latest release of dovecot verison 2.2.6 has some changes to lib-http which is breaking compiling on Solaris 10 sparc (though x86 builds successfully). Here is part of the compiler output while building: libtool: compile: /opt/SUNWspro/bin/cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-test
2015 May 12
2
v2.2.17 release candidate 2 released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc2.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc2.tar.gz.sig Changes since rc1: - Compiling fix for fs-compress in Solaris and maybe others. - Implemented Cassandra CQL support as lib-sql backend. This is mainly usable as dict-sql backend. - lib-fts fixes and improvements - Some other small random changes If no new issues are
2015 May 12
2
v2.2.17 release candidate 2 released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc2.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc2.tar.gz.sig Changes since rc1: - Compiling fix for fs-compress in Solaris and maybe others. - Implemented Cassandra CQL support as lib-sql backend. This is mainly usable as dict-sql backend. - lib-fts fixes and improvements - Some other small random changes If no new issues are
2015 May 10
1
v2.2.17 release candidate released
On 10 May 2015, at 11:47, Reuben Farrelly <reuben-dovecot at reub.net> wrote: > Ok we have some (well, lots actually) of coredumps now: > > Program terminated with signal SIGSEGV, Segmentation fault. > #0 0x00007f4834fcc222 in fts_user_get_data_lang (user=0x16c7900) > at fts-user.c:302 Thanks, this should fix it: http://hg.dovecot.org/dovecot-2.2/rev/fddd3dbdf987
2015 May 14
1
v2.2.17 Segfault
Hi, I'm using libexec/dovecot/imap via a ssh tunnel. 2.2.17 segfaults while accessing a NULL pointer. The following change fixes it for me: --- dovecot-2.2.17/src/lib-imap/imap-keepalive.c 2015-05-03 11:12:11.000000000 +0200 +++ dovecot-2.2.17/src/lib-imap/imap-keepalive.c 2015-05-14 20:06:29.490617405 +0200 @@ -11,6 +11,8 @@ { unsigned int addr; + if (!ip) + return FALSE; if
2015 May 10
0
v2.2.17 release candidate released
I'm now seeing these crashes in the indexing code: May 10 12:22:32 tornado.reub.net dovecot: master: Dovecot v2.2.17.rc1 (3903badc4ee0+) starting up for imap, lmtp, sieve ... May 10 13:07:50 tornado.reub.net dovecot: indexer: Error: Indexer worker disconnected, discarding 1 requests for reuben May 10 13:07:50 tornado.reub.net dovecot: indexer-worker(reuben): Fatal: master:
2015 Apr 28
3
CVE-2015-3420
When can we expect 2.2.17 to resolve this?
2015 May 13
1
v2.2.17 released
http://dovecot.org/releases/2.2/dovecot-2.2.17.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.17.tar.gz.sig A few director improvements since RC2, some fixes and a new plugin: http://wiki2.dovecot.org/Plugins/QuotaClone * Dovecot no longer checks or warns if a mountpoint is removed. This was causing more trouble than it was worth. Make sure that all the mountpoints that Dovecot
2015 May 13
1
v2.2.17 released
http://dovecot.org/releases/2.2/dovecot-2.2.17.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.17.tar.gz.sig A few director improvements since RC2, some fixes and a new plugin: http://wiki2.dovecot.org/Plugins/QuotaClone * Dovecot no longer checks or warns if a mountpoint is removed. This was causing more trouble than it was worth. Make sure that all the mountpoints that Dovecot
2015 May 10
0
v2.2.17 release candidate released
On May 9, 2015, at 19:13 , Jerry <jerry at seibercom.net> wrote: >> 2.2.17.rc1 will compile on FBSD 10.1 only, if bash has been installed (see >> <554773D2.9060609 at dovecot.fi> from Teemu Huovila).[...]. But, maybe it's worth >> solving this issue for those non-linux systems without bash installed per >> default before releasing dovecot v2.2.17, finally.
2015 May 11
1
Released Pigeonhole v0.4.8.rc1 for Dovecot v2.2.17.rc1
On 5/11/2015 6:24 PM, Brad Smith wrote: > On 05/10/15 18:42, Stephan Bosch wrote: >> Hello Dovecot users, >> >> Here's the Pigeonhole RC that goes with the Dovecot RC. It includes a >> few small fixes and one new feature. >> >> Changelog v0.4.8.rc1: >> >> * LDA Sieve plugin: Dovecot changed the deliver_log_format setting to >> include
2015 May 11
1
Released Pigeonhole v0.4.8.rc1 for Dovecot v2.2.17.rc1
On 5/11/2015 9:26 AM, Dominik Breu wrote: > Hello, > > did an test Install on my system get some nice SEGFAULT > wich backtrace here: https://dominikbreu.de/Stikked/view/8b6b7e5b > version is following: > aptitude versions dovecot-sieve i 2:2.2.17~rc1-1~auto+4 I cannot view that URL (some broken SSL error). You can just put the backtrace in the email itself. Regards,