similar to: v2.2.25 released

Displaying 20 results from an estimated 10000 matches similar to: "v2.2.25 released"

2016 Jun 30
5
v2.2.25 release candidate released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.25.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.25.rc1.tar.gz.sig Quite a lot of changes. Please test out before the final v2.2.25 release, which I'm planning for tomorrow. Especially the new lib-dcrypt might have compiling problems with some OpenSSL versions. * lmtp: Start tracking lmtp_user_concurrency_limit and reject already
2016 Jun 30
5
v2.2.25 release candidate released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.25.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.25.rc1.tar.gz.sig Quite a lot of changes. Please test out before the final v2.2.25 release, which I'm planning for tomorrow. Especially the new lib-dcrypt might have compiling problems with some OpenSSL versions. * lmtp: Start tracking lmtp_user_concurrency_limit and reject already
2017 Oct 13
3
v2.2.33 released
try with 2.2.33.1 ---Aki TuomiDovecot oy -------- Original message --------From: Odhiambo Washington <odhiambo at gmail.com> Date: 13/10/2017 10:42 (GMT+02:00) To: Dovecot Mailing List <dovecot at dovecot.org> Cc: dovecot-news at dovecot.org Subject: Re: v2.2.33 released On 10 October 2017 at 18:28, Timo Sirainen <tss at iki.fi> wrote: >
2016 Jul 01
2
v2.2.25 released
On 01 Jul 2016, at 19:09, Juan C. Blanco <jcblanco at fi.upm.es> wrote: > > I Haven't had the time to check the sha1.h error with the new fixes but I've just done so after de 2.2.25 release was out and I'm having the same error: > > gcc -DHAVE_CONFIG_H -I. -I. -I../.. -std=gnu99 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
2019 Feb 05
3
Release notify (2.2.36.1 and 2.3.4.1)
Due to DMARC issues some people have failed to receive the latest security information, so here it is repeated for both releases: 2.3.4.1 https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz.sig <https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig> Binary packages in https://repo.dovecot.org/ * CVE-2019-3814: If
2019 Feb 05
3
Release notify (2.2.36.1 and 2.3.4.1)
Due to DMARC issues some people have failed to receive the latest security information, so here it is repeated for both releases: 2.3.4.1 https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz.sig <https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig> Binary packages in https://repo.dovecot.org/ * CVE-2019-3814: If
2019 Feb 05
4
Release notify (2.2.36.1 and 2.3.4.1)
On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo Washington via dovecot wrote: > On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot <dovecot at dovecot.org> > wrote: > > > Due to DMARC issues some people have failed to receive the latest security > > information, so here it is repeated for both releases: > > > > 2.3.4.1 > > > >
2019 Feb 05
4
Release notify (2.2.36.1 and 2.3.4.1)
On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo Washington via dovecot wrote: > On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot <dovecot at dovecot.org> > wrote: > > > Due to DMARC issues some people have failed to receive the latest security > > information, so here it is repeated for both releases: > > > > 2.3.4.1 > > > >
2019 Feb 05
2
Release notify (2.2.36.1 and 2.3.4.1)
pull the patches from the port..... On Tue, Feb 5, 2019 at 2:28 PM Odhiambo Washington via dovecot < dovecot at dovecot.org> wrote: > Oh, so manual compile should NOT work and it's okay or am I missing > something? > > On Tue, 5 Feb 2019 at 23:26, The Doctor <doctor at doctor.nl2k.ab.ca> wrote: > >> On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo
2018 Nov 23
3
v2.3.4 released
On Fri, Nov 23, 2018 at 04:06:53PM +0300, Odhiambo Washington wrote: > On Fri, 23 Nov 2018 at 15:29, Timo Sirainen <tss at iki.fi> wrote: > > > https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz > > https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz.sig > > Binary packages in https://repo.dovecot.org/ > > > > * The default postmaster_address is now
2019 Feb 05
2
Release notify (2.2.36.1 and 2.3.4.1)
the patches are already in git master. I've pulled them into the mail/dovecot port. The dovecot guys/gals will release it eventually, but the port works TODAY. On Tue, Feb 5, 2019 at 2:33 PM Odhiambo Washington <odhiambo at gmail.com> wrote: > I have always been able to compile manually, even from RCs so I believe I > should be able to compile from the tarball as well. >
2019 Feb 05
2
Release notify (2.2.36.1 and 2.3.4.1)
2.3.4 had the same compile issues.... On Tue, Feb 5, 2019 at 2:44 PM Odhiambo Washington <odhiambo at gmail.com> wrote: > Noted. > > I will wait for dovecot-2.3.4.2 tarball then. > > In all the servers I listed (+2 more), I never use the mail/dovecot port. > > I rely on mail/dovecot port on my own prototype (FreeBSD 12) which I have > built in preparation for the
2016 Jul 02
4
Dovecot 2.2.25 compiling error
Hello. I cant build 2.2.25, but I can build fine version 2.2.24 with same options: RedHat based customized distro, 2.6.28.10 kernel Build options: export CPPFLAGS export LDFLAGS CPPFLAGS=-I/usr/local/ssl/include LDFLAGS=-L/usr/local/ssl/lib ./configure \ --prefix=/usr \ --with-ssl=openssl \ --with-ssldir=/etc/ssl \ --sysconfdir=/etc \
2018 Mar 29
2
Release 2.3.1
On 28.03.2018 22:14, Odhiambo Washington wrote: > > > On 27 March 2018 at 20:06, <aki.tuomi at dovecot.fi > <mailto:aki.tuomi at dovecot.fi>> wrote: > > Hi! > > We are releasing v2.3.1, which mostly consists of bug fixes for > 2.3.0, and few improvements. This is also available via > https://repo.dovecot.org if you want packages. libsodium
2016 Mar 30
5
v2.2.23 released
http://dovecot.org/releases/2.2/dovecot-2.2.23.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.23.tar.gz.sig This is a bugfix-only release with various important fixes on top of v2.2.22. - Various fixes to doveadm. Especially running commands via doveadm-server was broken. - director: Fixed user weakness getting stuck in some situations - director: Fixed a situation where directors keep
2016 Mar 30
5
v2.2.23 released
http://dovecot.org/releases/2.2/dovecot-2.2.23.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.23.tar.gz.sig This is a bugfix-only release with various important fixes on top of v2.2.22. - Various fixes to doveadm. Especially running commands via doveadm-server was broken. - director: Fixed user weakness getting stuck in some situations - director: Fixed a situation where directors keep
2018 Mar 29
2
Release 2.3.1
On 29.03.2018 10:36, Odhiambo Washington wrote: > > > On 29 March 2018 at 09:43, Aki Tuomi <aki.tuomi at dovecot.fi > <mailto:aki.tuomi at dovecot.fi>> wrote: > > > > On 28.03.2018 22:14, Odhiambo Washington wrote: >> >> >> On 27 March 2018 at 20:06, <aki.tuomi at dovecot.fi >> <mailto:aki.tuomi at dovecot.fi>>
2018 Mar 29
2
Release 2.3.1
On 29.03.2018 13:14, Odhiambo Washington wrote: > > > On 29 March 2018 at 13:04, Aki Tuomi <aki.tuomi at dovecot.fi > <mailto:aki.tuomi at dovecot.fi>> wrote: > > > > On 29.03.2018 10:36, Odhiambo Washington wrote: >> >> >> On 29 March 2018 at 09:43, Aki Tuomi <aki.tuomi at dovecot.fi >> <mailto:aki.tuomi at
2018 Nov 23
9
v2.3.4 released
https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz.sig Binary packages in https://repo.dovecot.org/ * The default postmaster_address is now "postmaster@<user domain or server hostname>". If username contains the @domain part, that's used. If not, then the server's hostname is used. * "doveadm stats
2018 Nov 23
9
v2.3.4 released
https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz.sig Binary packages in https://repo.dovecot.org/ * The default postmaster_address is now "postmaster@<user domain or server hostname>". If username contains the @domain part, that's used. If not, then the server's hostname is used. * "doveadm stats