Displaying 20 results from an estimated 8000 matches similar to: "v2.2.33 released"
2017 Oct 13
0
v2.2.33 released
I have just made an attempt at compiling 2.2.33.1 and it fails on one of my
servers - FreeBSD 8.4 where 2.2.32 has been running happily:
This is where I am going to start the tests before I move to the other
servers (FreeBSD 9.3, 10.3, 11):
mv -f .deps/maildir-settings.Tpo .deps/maildir-settings.Plo
/bin/bash ../../../../libtool --tag=CC --mode=compile gcc
-DHAVE_CONFIG_H -I. -I../../../..
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 01
5
v2.2.25 released
http://dovecot.org/releases/2.2/dovecot-2.2.25.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.25.tar.gz.sig
Some minor fixes and (mainly logging) improvements since rc1.
* lmtp: Start tracking lmtp_user_concurrency_limit and reject already
at RCPT TO stage. This avoids MTA unnecessarily completing DATA only
to get an error.
* doveadm: Previously only mail settings were read from
2016 Jul 01
5
v2.2.25 released
http://dovecot.org/releases/2.2/dovecot-2.2.25.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.25.tar.gz.sig
Some minor fixes and (mainly logging) improvements since rc1.
* lmtp: Start tracking lmtp_user_concurrency_limit and reject already
at RCPT TO stage. This avoids MTA unnecessarily completing DATA only
to get an error.
* doveadm: Previously only mail settings were read from
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)
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
2017 Oct 10
1
v2.2.33 released
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
2017 Oct 10
1
v2.2.33 released
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
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
> >
> >
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 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 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
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
2017 Dec 22
1
Fwd: v2.3.0 release candidate released
Okay, I was hoping it has something to do with where I am stuck compiling.
Could you kindly share your configure options? Mine which has always worked
with Dovecot versions prior to 2.3 is refusing to work on FreeBSD i386.
<cut>
mv -f .deps/test_auth_cache-test-auth-cache.Tpo
.deps/test_auth_cache-test-auth-cache.Po
clang -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-auth
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
2017 Dec 22
2
Fwd: v2.3.0 release candidate released
Hi Goetz,
I don't seem to understand what you mean by 'remove the last entry'. Do you
mind clarifying please?
On 18 December 2017 at 23:12, Goetz Schultz <email at suelze.de> wrote:
> Found the guide .... Can you remove last entry please ... works with TLSv1.
>
>
> Thanks and regards
>
> Goetz R. Schultz
>
> On 18/12/17 20:05, Goetz Schultz wrote:
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