search for: 2.2.30

Hello. I cant build 2.2.30*, but I can build fine version 2.2.29* 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 \

Andrey Jr. Melnikov wrote: > Mart Pirita <sysadmin at e-positive.ee> wrote: >> Hello. >> I cant build 2.2.30*, but I can build fine version 2.2.29* with same >> options: >> RedHat based customized distro, 2.6.28.10 kernel > [...] > >> Build error: >> ltest_lib-test-bits.o: In function `bits_required64': >>

Mart Pirita <sysadmin at e-positive.ee> wrote: > Hello. > I cant build 2.2.30*, but I can build fine version 2.2.29* with same > options: > RedHat based customized distro, 2.6.28.10 kernel [...] > Build error: > ltest_lib-test-bits.o: In function `bits_required64': > /usr/src/redhat/BUILD/dovecot-2.2.30/src/lib/bits.h:33: undefined > reference to

Timo Sirainen wrote: > On 21 Jun 2017, at 16.03, Mart Pirita <sysadmin at e-positive.ee> wrote: >>>> ltest_lib-test-bits.o: In function `bits_required64': >>>> /usr/src/redhat/BUILD/dovecot-2.2.30/src/lib/bits.h:33: undefined >>>> reference to `__builtin_clzll' > This can be fixed with the attached patch. Thanks, got this time new error, do

On 21 Jun 2017, at 16.03, Mart Pirita <sysadmin at e-positive.ee> wrote: > >>> ltest_lib-test-bits.o: In function `bits_required64': >>> /usr/src/redhat/BUILD/dovecot-2.2.30/src/lib/bits.h:33: undefined >>> reference to `__builtin_clzll' This can be fixed with the attached patch. -------------- next part -------------- A non-text attachment was

On 21 Jun 2017, at 16.42, Mart Pirita <sysadmin at e-positive.ee> wrote: > > Timo Sirainen wrote: >> On 21 Jun 2017, at 16.03, Mart Pirita <sysadmin at e-positive.ee> wrote: >>>>> ltest_lib-test-bits.o: In function `bits_required64': >>>>> /usr/src/redhat/BUILD/dovecot-2.2.30/src/lib/bits.h:33: undefined >>>>> reference to

Hi! On 04.09.2017 14:38, Harald Leithner wrote: > Hi, > > it seams that the lazy_expunge plugin doesn't work for me after the > upgrade... > > 2.2.32 cry's about > > plugin { lazy_expunge_only_last_instance=no } is most likely handled > as 'yes' - remove the setting completely to disable it. If this is > intentional, add quotes around the value: >

Ok thx for the info, anyway there are no mail copied to #EXPUNGED/ namespace. Am 04.09.2017 um 13:40 schrieb Aki Tuomi: > Hi! > > On 04.09.2017 14:38, Harald Leithner wrote: >> Hi, >> >> it seams that the lazy_expunge plugin doesn't work for me after the >> upgrade... >> >> 2.2.32 cry's about >> >> plugin {

Any idea why this doesn't setup work anymore in 2.2.32? thx Harald Am 04.09.2017 um 13:52 schrieb Harald Leithner: > Ok thx for the info, anyway there are no mail copied to #EXPUNGED/ > namespace. > > > > Am 04.09.2017 um 13:40 schrieb Aki Tuomi: >> Hi! >> >> On 04.09.2017 14:38, Harald Leithner wrote: >>> Hi, >>> >>> it

On Wed, Sep 6, 2017 at 2:01 AM, Harald Leithner <leithner at itronic.at> wrote: > Any idea why this doesn't setup work anymore in 2.2.32? > > thx > > Harald > > I just ran into the same thing myself. For me, when I added this to the "location" in the expunged namespace, it started working again: ...:LISTINDEX=expunged.list.index I can't tell you why

Am 2017-09-15 21:25, schrieb Mark Moseley: > On Wed, Sep 6, 2017 at 2:01 AM, Harald Leithner <leithner at itronic.at> > wrote: > >> Any idea why this doesn't setup work anymore in 2.2.32? >> >> thx >> >> Harald >> >> > > I just ran into the same thing myself. For me, when I added this to the > "location" in the

On Fri, Sep 15, 2017 at 1:42 PM, Harald Leithner <leithner at itronic.at> wrote: > Am 2017-09-15 21:25, schrieb Mark Moseley: > >> On Wed, Sep 6, 2017 at 2:01 AM, Harald Leithner <leithner at itronic.at> >> wrote: >> >> Any idea why this doesn't setup work anymore in 2.2.32? >>> >>> thx >>> >>> Harald >>>

https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz.sig * auth: Use timing safe comparisons for everything related to passwords. It's unlikely that these could have been used for practical attacks, especially because Dovecot delays and flushes all failed authentications in 2 second intervals. Also it could have worked only

https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz.sig * auth: Use timing safe comparisons for everything related to passwords. It's unlikely that these could have been used for practical attacks, especially because Dovecot delays and flushes all failed authentications in 2 second intervals. Also it could have worked only

Hello. I've searched through the list and saw this problem was reported several month ago, along with gdb traces, but in the end I don't see any solution or workaround suggested. I've recently build a file server on top of FreeBSD amd64 SMP: this is also a BDC and is working with an ldapsam_compat backend. The (secondary) LDAP server is on the same machine. Right now I've

On 06/05/2017 11:05 AM, Angel L. Mateo wrote: > I have updated my dovecot proxy servers from 2.2.28 to 2.2.30. Since the upgrade I'm having the error: > > Jun 5 10:54:51 musio12 dovecot: auth: Fatal: master: service(auth): child 63632 killed with signal 11 (core not dumped) > > Me too, with # 2.2.30.1 (eebd877): /opt/dovecot/etc/dovecot/dovecot.conf # Pigeonhole

Hi, it seams that the lazy_expunge plugin doesn't work for me after the upgrade... 2.2.32 cry's about plugin { lazy_expunge_only_last_instance=no } is most likely handled as 'yes' - remove the setting completely to disable it. If this is intentional, add quotes around the value: lazy_expunge_only_last_instance="no" I changed it to

Getting this error: > In file included from ../../src/lib/lib.h:6:0, > from auth-common.h:4, > from userdb-vpopmail.c:5: > ../../config.h:791:0: note: this is the location of the previous > definition > #define VERSION "2.2.30" > ^ > userdb-vpopmail.c: In function ?userdb_vpopmail_get_quota?: > userdb-vpopmail.c:72:6:

At least doveconf -n output would help. I guess related to authentication settings. Are there any errors in logs? > On 1 Jun 2017, at 12.14, Odhiambo Washington <odhiambo at gmail.com> wrote: > >> On 30 May 2017 at 21:16, Timo Sirainen <tss at iki.fi> wrote: >> >> https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz >>

https://dovecot.org/releases/2.2/rc/dovecot-2.2.30.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.30.rc1.tar.gz.sig There are a couple of changes still coming, but now would be a good time to make sure anything unexpected hasn't broken. The final release should be out early next week. * auth: Use timing safe comparisons for everything related to passwords. It's unlikely