similar to: v2.2.26 release candidate released

> On October 21, 2016 at 6:27 AM Tamsy <dovecot-list at mohtex.net> wrote: > > > Timo Sirainen wrote on 20.10.2016 04:01: > > http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz > > http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz.sig > > > > There are quite a lot of changes since v2.2.25. Please try out this RC so we can get a good

Timo Sirainen wrote on 20.10.2016 04:01: > http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz > http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz.sig > > There are quite a lot of changes since v2.2.25. Please try out this RC so we can get a good and stable v2.2.26 out. > > * master: Removed hardcoded 511 backlog limit for listen(). The kernel > should

On 10/20/2016 10:34 PM, Aki Tuomi wrote: >> On October 21, 2016 at 6:27 AM Tamsy <dovecot-list at mohtex.net> wrote: >> >> >> Timo Sirainen wrote on 20.10.2016 04:01: >>> http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz >>> http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz.sig >>> >>> There are quite a lot of

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

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

http://dovecot.org/releases/2.2/dovecot-2.2.26.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.26.tar.gz.sig There were some changes since rc1: https://github.com/dovecot/core/commit/54d654098032d96975b70749b505fae538e97f7a Mainly there are quite a lot of director fixes and improvements. Here's the full list of changes: * master: Removed hardcoded 511 backlog limit for listen(). The

http://dovecot.org/releases/2.2/dovecot-2.2.26.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.26.tar.gz.sig There were some changes since rc1: https://github.com/dovecot/core/commit/54d654098032d96975b70749b505fae538e97f7a Mainly there are quite a lot of director fixes and improvements. Here's the full list of changes: * master: Removed hardcoded 511 backlog limit for listen(). The

Compiled on CentOS 6 and CentOS 7 successfully. On 10/19/2016 3:01 PM, Timo Sirainen wrote: > http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz > http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz.sig > > There are quite a lot of changes since v2.2.25. Please try out this RC so we can get a good and stable v2.2.26 out. > > * master: Removed hardcoded 511

Hi, Do you plan on inclinding the following patch in the final release? http://www.dovecot.org/list/dovecot/2016-October/105734.html I have some tests in place and can backport the patch if necessary. Regards, On 10/19/2016 11:01 PM, Timo Sirainen wrote: > http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz > http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz.sig

Hello, Here is a Panic that happened while doing some testing with two servers both running Dovecot v2.2.26 on CentOS 7. These are test servers owning 32 accounts whose data were copied from our production server. What I've done is: server01# doveadm force-resync -A '*' server01# doveadm replicator replicate -f '*' For 5 accounts I obtained the following crash:

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

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

On 27.10.2016 16:39, Arkadiusz Mi?kiewicz wrote: > On Thursday 27 of October 2016, Timo Sirainen wrote: >> http://dovecot.org/releases/2.2/dovecot-2.2.26.tar.gz >> http://dovecot.org/releases/2.2/dovecot-2.2.26.tar.gz.sig > Please merge to 2.2 branch this fix. I'm hitting that problem on 2.2.25: > > From 6c969ac21a43cc10ee1f1a91a4f39e4864c886cb Mon Sep 17 00:00:00 2001

I built from dovecot-2.2.25.tar.gz on Mac OSX 10.11.15 (El Capitan) the usual way: CFLAGS=-I/usr/local/ssl/include LDFLAGS=-L/usr/local/ssl/lib ./configure make sudo make install sudo /usr/local/sbin/dovecot It consistently crash on startup with the following entries in /var/log/mail.log (edited backtrace): Jul 27 07:39:26 macbook-pro dovecot[70234]: master: Dovecot v2.2.25

27.10.2016 16:39, Arkadiusz Mi?kiewicz wrote: > On Thursday 27 of October 2016, Timo Sirainen wrote: >> http://dovecot.org/releases/2.2/dovecot-2.2.26.tar.gz >> http://dovecot.org/releases/2.2/dovecot-2.2.26.tar.gz.sig > Please merge to 2.2 branch this fix. I'm hitting that problem on 2.2.25: > > From 6c969ac21a43cc10ee1f1a91a4f39e4864c886cb Mon Sep 17 00:00:00 2001

I worked out why valgrind wasn't being applied to nbdkit when run by many of the tests (patches 1-2). Unfortunately I'm not able to make it actually fail tests when valgrind fails. Although the situation is marginally improved in that you can now manually examine the *.log files and find valgrind failures that way. Also adds valgrinding of the Python plugin (patch 3). Along the way I

Hello llvmdev, I would like to propose and discuss yet another dynamic tool, which we call MemorySanitizer (msan). The main goal of the tool is to detect uses of uninitialized memory (the major feature of Valgrind/Memcheck not covered by AddressSanitizer). It will also find use-after-destruction-but-before-free in C++. The algorithm of the tool is similar to that of Memcheck (

Hi, only one letter got to valgrind-developers mailing list. I'll quote the first message of the thread so that those who do not read llvmdev knew what's this discusssion about. === Begin of the first message === > Hi, > > I've seen on the LLVM's Open Projet Page [1] an idea about using LLVM to > generate native code in Valgrind. For what I know, Valgrind uses libVEX

Currently I'm having massive problems with LMTP delivery into dovcot. dovecot/lmtp processes are piling up, eas using considerable amounts of CPU: # ps auxwww|fgrep dove root 20537 0.0 0.0 18124 1196 ? Ss 15:18 0:00 /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf dovecot 20541 0.0 0.0 9620 1084 ? S 15:18 0:00 dovecot/anvil root 20542 0.0 0.0 9752

I think I am using objects according to the man page. This seems to be a valid regular expression. But whether I know what I'm doing or no, it still shouldn't be doing what valgrind seems to be saying it's doing. (IMHO) ---------- start of script ---------- Script started on Mon 01 Aug 2005 02:09:00 PM PDT linux$ printenv VALGRIND_OPTS --tool=3Dmemcheck linux$ cat bar.R foo <- 1