similar to: Dovecot 2.2.25 test failure

Displaying 20 results from an estimated 700 matches similar to: "Dovecot 2.2.25 test failure"

2016 Aug 04
2
Dovecot 2.2.25 test failure
On 08/04/2016 06:13 AM, Aki Tuomi wrote: > > > On 04.08.2016 16:11, Michael A. Peters wrote: >> Operating system - 64 bit CentOS 7 >> gcc-4.8.5-4.el7.x86_64 >> >> Building against LibreSSL which has been fine for other releases, but >> it is a crypto test that is fails. >> >> Tried with LibreSSL 2.4.2 and 2.3.6 - both the build completes but
2016 Aug 04
2
Dovecot 2.2.25 test failure
On 08/04/2016 06:50 AM, aki.tuomi at dovecot.fi wrote: > >> On August 4, 2016 at 4:19 PM "Michael A. Peters" <mpeters at domblogger.net> wrote: >> >> >> On 08/04/2016 06:13 AM, Aki Tuomi wrote: >>> >>> >>> On 04.08.2016 16:11, Michael A. Peters wrote: >>>> Operating system - 64 bit CentOS 7 >>>>
2016 Oct 21
3
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
2010 Jul 07
1
post 2.0rc1 compilation issue
Hi, I was just updating dovecot to nightly snapshot for Fedora rawhide, but got following issue: fts-backend-solr.c: In function 'fts_box_name_get_root': fts-backend-solr.c:60: error: 'NAMESPACE_FLAG_INBOX' undeclared (first use in this function) fts-backend-solr.c:60: error: (Each undeclared identifier is reported only once and once again on line 750 seems the change
2018 Sep 09
3
make check (pigeonhole)
Hello list, During the 'make check' (pigeonhole) portion of a building (rpmbuild) a dovecot.spec file I'm getting the following error: testsuite(root): Fatal: Couldn't drop privileges: User is missing UID (see mail_uid setting) I'm not sure how to resolve this, and any help would be appreciated to help me finish the creating the rpm -- Eric Broch White Horse Technical
2018 Sep 10
1
make check (pigeonhole)
Dovecot list, 1) I downloaded latest dovecot and pigeonhole tar balls and extracted on latest updated CentOS 7 : dovecot-2.3.2.1.tar.gz and dovecot-2.3-pigeonhole-0.5.2.tar.gz 2) I moved pigeonhole (dovecot-2.3-pigeonhole-0.5.2) directory into dovecot (dovecot-2.3.2.1) directory 3) built dovecot with following config and paramerters: patch -p1 <
2016 Oct 19
14
v2.2.26 release candidate released
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 limit this as needed. * doveadm import: Source user is now initialized
2016 Oct 19
14
v2.2.26 release candidate released
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 limit this as needed. * doveadm import: Source user is now initialized
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
2016 Nov 15
2
Crashing when run against OpenSSL 1.1.0c
Hi, I am running Dovecot 2.2.26.0 compiled against OpenSSL 1.1 and, since upgrading to OpenSSL 1.1.0c, the "lmtp" process has been crashing with SIGSEGV whenever it receives SIGINT. This always happens a minute or so after the lmtp process handles a message. It can also be manually reproduced by sending SIGINT to one of the running lmtp processes. I am compiling and running on an
2018 Aug 15
1
error while compiling dovecot
hello my server is centos 6 64 bit while installing dovecot i get this error Failed to run: ./test-compression what could be the reason. could someone guide me please Version dovecot-ce-2.3.0-1 0 / 7 tests failed ==21130== Conditional jump or move depends on uninitialised value(s) ==21130== at 0x349B00ACB2: ??? (in /usr/lib64/liblzma.so.0.0.0) ==21130== by 0x349B00AEA9: ??? (in
2016 Oct 21
0
v2.2.26 release candidate released
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
2014 May 23
1
Conditional jump or move depends on uninitialised value
Hi, My Server runs on Ubuntu Server 12.04 LTS 32 bits. I'm getting the following error messages when I run "make check" during the compilation of dovecot-2.2.13. <snip> ==2058== Conditional jump or move depends on uninitialised value(s) ==2058==??? at 0x4049DD8: inflateReset2 (in /lib/i386-linux-gnu/libz.so.1.2.3.4) ==2058==??? by 0x4049EC7: inflateInit2_ (in
2016 Oct 21
0
v2.2.26 release candidate released
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
2016 Oct 26
1
(build) crash in dcrypt when "-Bsymbolic-functions" is used on linking
On 26.10.2016 13:48, Christian Ehrhardt wrote: > Hi, > I was wondering about a crash when building dovecot 2.2.25 on latest > Ubuntu. > I wondered as I've had the same source building on Debian just fine. > > Some debugging led me to this weird behavior: > Using this gdb command file called autoreportissue in my case: > break dcrypt_initialize > commands >
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
2018 Mar 01
5
Make fails with 2.3.0.1 & 2.2.34 on Mac OS X 10.7.5
> On 1 Mar 2018, at 5:56 pm, Aki Tuomi <aki.tuomi at dovecot.fi <mailto:aki.tuomi at dovecot.fi>> wrote: > > > > On 01.03.2018 07:34, James Brown wrote: >> On 1 Mar 2018, at 4:09 pm, Aki Tuomi <aki.tuomi at dovecot.fi <mailto:aki.tuomi at dovecot.fi>> wrote: >>> >>> >>> What SSL library and version? >>> ---
2014 Oct 25
3
v2.2.15 released
http://dovecot.org/releases/2.2/dovecot-2.2.15.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.15.tar.gz.sig Some small fixes and changes to v2.2.14. This release is mainly in the hope that it could still make it into the next Debian stable instead of v2.2.14 - mainly because of a couple of new assert crashes that started happening in v2.2.14 and should be fixed now. * Plugins can now print