Re: Dovecot 2.3.13 source rpm build fails on Centos 8
> On 08/01/2021 04:34 st...@keptprivate.com wrote:
>
>
>
> I tried to post this in a more nuanced way, but the fact is the latest source
> RPM does not build on the latest Centos 8.
>
> > + sed -i 's|/etc/ssl|/etc/pki/dovecot|' doc/mkcert.sh (http://mkcert.sh)
> > doc/example-config/conf.d/10-ssl.co (http://10-ssl.co)nf
> > + '[' -e buildinfo.com (http://buildinfo.com)mit ']'
> > ++ head -1 buildinfo.com (http://buildinfo.com)mit
> > + COMMIT=89f716dc2ec7362864a368d32533184b55fb7831
> > ++ /bin/sh /home/build/rpmbuild/SOURCES/lsb_release -is
> >
> /bin/sh: /home/build/rpmbuild/SOURCES/lsb_release: No such file or directory
> > + ID=
> > error: Bad exit status from /var/tmp/rpm-tmp.WF (http://rpm-tmp.WF)aLYQ
> > (%build)
> >
> >
> > RPM build errors:
> > Macro expanded in comment on line 455:
> %{_libdir}/dovecot/settings
> >
> > Bad exit status from /var/tmp/rpm-tmp.WF (http://rpm-tmp.WF)aLYQ
> > (%build)
> >
> > I can get past this with an edit to the dovecot.spec file (removing
> > sourcedir):
> >
> > if [ -e "buildinfo.com (http://buildinfo.com)mit" ]; then
> >COMMIT=`head -1 buildinfo.com (http://buildinfo.com)mit`
> >ID=`/bin/sh %̶{̶_̶s̶o̶u̶r̶c̶e̶d̶i̶r̶}̶/̶lsb_release -is`
> >RELEASE=`/bin/sh %̶{̶_̶s̶o̶u̶r̶c̶e̶d̶i̶r̶}̶/̶lsb_release -rs`
> >CODENAME=`/bin/sh %̶{̶_̶s̶o̶u̶r̶c̶e̶d̶i̶r̶}̶/̶lsb_release -cs`
> >ARCH=`arch`
> > fi
> Can someone who knows the source rpm build config. please respond?
> The committed spec file contains errors.
>
> Thanks
>
> Sent from my T-Mobile 4G LTE device
There are now source RPMs for centos8 in repo.dovecot.org. Maybe they work
better?
Aki
Dovecot 2.3.13 source rpm build fails on Centos 8
I tried to post this in a more nuanced way, but the fact is the latest source
RPM does not build on the latest Centos 8.> + sed -i
's|/etc/ssl|/etc/pki/dovecot|' doc/mkcert.sh
doc/example-config/conf.d/10-ssl.conf
> + '[' -e buildinfo.commit ']'
> ++ head -1 buildinfo.commit
> + COMMIT=89f716dc2ec7362864a368d32533184b55fb7831
> ++ /bin/sh /home/build/rpmbuild/SOURCES/lsb_release -is
>
/bin/sh: /home/build/rpmbuild/SOURCES/lsb_release: No such file or directory
> + ID=
> error: Bad exit status from /var/tmp/rpm-tmp.WFaLYQ (%build)
>
>
> RPM build errors:
> Macro expanded in comment on line 455: %{_libdir}/dovecot/settings
>
> Bad exit status from /var/tmp/rpm-tmp.WFaLYQ (%build)
>
> I can get past this with an edit to the dovecot.spec file (removing
> sourcedir):
>
> if [ -e "buildinfo.commit" ]; then
>COMMIT=`head -1 buildinfo.commit`
>ID=`/bin/sh %̶{̶_̶s̶o̶u̶r̶c̶e̶d̶i̶r̶}̶/̶lsb_release -is`
>RELEASE=`/bin/sh %̶{̶_̶s̶o̶u̶r̶c̶e̶d̶i̶r̶}̶/̶lsb_release -rs`
>
CODENAME=`/bin/sh %̶{̶_̶s̶o̶u̶r̶c̶e̶d̶i̶r̶}̶/̶lsb_release -cs`
>ARCH=`arch`
> fiCan someone who knows the source rpm build config. please respond?The
> committed spec file contains errors.ThanksSent from my T-Mobile 4G LTE device
Update: 2.3.13: newly introduced TLS bug : tls_construct_server_key_exchange
Am 07.01.21 um 17:31 schrieb Marius Schwarz: Versions: dovecot-2.3.13-1.fc32.x86_64 openssl-1.1.1i-1.fc32.x86_64 Fedora released dovecot-2.3.13-2.fc32.x86_64, which seems to fix the issue. best regards, Marius Schwarz
Re: problem building on centos 8 (8.3 kernel)
Another thought... Could I use a different build mechanism that would result in
the same installation rpm? There's no reason I have to use source rpms, I'm
just used to it because of qmailtoaster.SteveSent from my T-Mobile 4G LTE
device-- Original message--From: steve@keptprivate.comDate: Thu, Jan 7,
2021 3:48 PMTo: Aki Tuomi;dovecot@dovecot.org;Cc: Subject:Re: problem building
on centos 8 (8.3 kernel)
Any ideas about the lsb_release error in the spec file and where that came
from? I have a very vanilla centos 8 install I'm trying to bulid on. Any
thoughts appreciated because I'm stuck and at something of a loss on what to
try next. My first thought is to look at spec file revisions.SteveSent from my
T-Mobile 4G LTE device-- Original message--From: Aki TuomiDate: Thu,
Jan 7, 2021 3:10 AMTo: st...@keptprivate.com;dovecot@dovecot.org;Cc:
Subject:Re: problem building on centos 8 (8.3 kernel)> On 07/01/2021 03:57
st...@keptprivate.com wrote:
>
>
> Hi,
>
> I'm
converting from qmailtoaster/vpopmail build.
> When I try to build dovecot-2.3.13-2.src.rpm for centos 8.3 the first thing I
> run into is this:
>
> + sed -i 's|/etc/ssl|/etc/pki/dovecot|' doc/mkcert.sh
> doc/example-config/conf.d/10-ssl.conf
> + '[' -e buildinfo.commit ']'
> ++ head -1 buildinfo.commit
> + COMMIT=89f716dc2ec7362864a368d32533184b55fb7831
> ++ /bin/sh /home/build/rpmbuild/SOURCES/lsb_release -is
>
/bin/sh: /home/build/rpmbuild/SOURCES/lsb_release: No such file or directory
> + ID=
> error: Bad exit status from /var/tmp/rpm-tmp.WFaLYQ (%build)
>
>
> RPM build errors:
> Macro expanded in comment on line 455: %{_libdir}/dovecot/settings
>
> Bad exit status from /var/tmp/rpm-tmp.WFaLYQ (%build)
>
> I can get past this with an edit to the dovecot.spec file (removing
> sourcedir):
>
> if [ -e "buildinfo.commit" ]; then
>COMMIT=`head -1 buildinfo.commit`
>ID=`/bin/sh %̶{̶_̶s̶o̶u̶r̶c̶e̶d̶i̶r̶}̶/̶lsb_release -is`
>RELEASE=`/bin/sh
%̶{̶_̶s̶o̶u̶r̶c̶e̶d̶i̶r̶}̶/̶lsb_release -rs`
>CODENAME=`/bin/sh %̶{̶_̶s̶o̶u̶r̶c̶e̶d̶i̶r̶}̶/̶lsb_release -cs`
>ARCH=`arch`
> fi
>
> The RPM builds but it fails to run with this message in the logs:
>
> Jan 6 20:52:11 beta1
systemd[1]: Starting Dovecot IMAP/POP3 email server...
> Jan 6 20:52:11 beta1 systemd[1]: Started Dovecot IMAP/POP3 email server.
> Jan 6 20:52:11 beta1 dovecot[356909]: /usr/sbin/dovecot: error while loading
> shared libraries: libdovecot.so.0: cannot open shared object
> file: No such file or directory
> Jan 6 20:52:11 beta1 systemd[1]: dovecot.service: Main process exited,
> code=exited, status=127/n/a
> Jan 6 20:52:11 beta1 systemd[1]: dovecot.service: Failed with result
> 'exit-code'.
>
> Any ideas what I have going wrong?
>
> Also, a side question, when I build the rpm it's not running the extensive
> tests that the old qmailtoaster source rpm used to run. I've
> looked through the spec file and I don't really see where to turn that back
> on.
>
>
Sorry if any of this is stupid, but I'm new to building directly from the
dovecot repo.
>
>
Steve
I think the file is installed under /usr/lib64/, so check
ldd /usr/lib64/libdovecot.so.0
Is there some reason you are building the rpms yourself?
Aki
Re: problem building on centos 8 (8.3 kernel)
Any ideas about the lsb_release error in the spec file and where that came
from? I have a very vanilla centos 8 install I'm trying to bulid on. Any
thoughts appreciated because I'm stuck and at something of a loss on what to
try next. My first thought is to look at spec file revisions.SteveSent from my
T-Mobile 4G LTE device-- Original message--From: Aki TuomiDate: Thu,
Jan 7, 2021 3:10 AMTo: st...@keptprivate.com;dovecot@dovecot.org;Cc:
Subject:Re: problem building on centos 8 (8.3 kernel)> On 07/01/2021 03:57
st...@keptprivate.com wrote:
>
>
> Hi,
>
> I'm converting from qmailtoaster/vpopmail build.
> When I try to build dovecot-2.3.13-2.src.rpm for centos 8.3 the first thing I
> run into is this:
>
> + sed -i 's|/etc/ssl|/etc/pki/dovecot|' doc/mkcert.sh
> doc/example-config/conf.d/10-ssl.conf
> + '[' -e buildinfo.commit ']'
> ++ head -1 buildinfo.commit
> + COMMIT=89f716dc2ec7362864a368d32533184b55fb7831
> ++ /bin/sh /home/build/rpmbuild/SOURCES/lsb_release -is
> /bin/sh:
/home/build/rpmbuild/SOURCES/lsb_release: No such file or directory
> + ID=
> error: Bad exit status from /var/tmp/rpm-tmp.WFaLYQ (%build)
>
>
> RPM build errors:
> Macro expanded in comment on line 455: %{_libdir}/dovecot/settings
>
> Bad exit status from /var/tmp/rpm-tmp.WFaLYQ (%build)
>
> I can get past this with an edit to the dovecot.spec file (removing
> sourcedir):
>
> if [ -e "buildinfo.commit" ]; then
>COMMIT=`head -1 buildinfo.commit`
>ID=`/bin/sh %̶{̶_̶s̶o̶u̶r̶c̶e̶d̶i̶r̶}̶/̶lsb_release -is`
>RELEASE=`/bin/sh %̶{̶_̶s̶o̶u̶r̶c̶e̶d̶i̶r̶}̶/̶lsb_release -rs`
>CODENAME=`/bin/sh %̶{̶_̶s̶o̶u̶r̶c̶e̶d̶i̶r̶}̶/̶lsb_release -cs`
>ARCH=`arch`
> fi
>
> The RPM builds but it fails to run with this message in the logs:
>
> Jan 6 20:52:11 beta1 systemd[1]: Starting Dovecot IMAP/POP3 email server...
> Jan 6 20:52:11 beta1 systemd[1]: Started Dovecot IMAP/POP3 email server.
> Jan 6 20:52:11 beta1 dovecot[356909]: /usr/sbin/dovecot: error while loading
shared libraries: libdovecot.so.0: cannot open shared object
> file: No such file or directory
> Jan 6 20:52:11 beta1 systemd[1]: dovecot.service: Main process exited,
> code=exited, status=127/n/a
> Jan 6 20:52:11 beta1 systemd[1]: dovecot.service: Failed with result
> 'exit-code'.
>
> Any ideas what I have going wrong?
>
> Also, a side question, when I build the rpm it's not running the extensive
> tests that the old qmailtoaster source rpm used to run. I've
> looked through the spec file and I don't really see where to turn that back
> on.
>
> Sorry if any of this is stupid, but I'm new to building directly from the
> dovecot repo.
>
> Steve
I think the file is installed under /usr/lib64/, so check
ldd /usr/lib64/libdovecot.so.0
Is there some reason you are building the rpms yourself?
Aki
2.3.13: newly introduced TLS bug : tls_construct_server_key_exchange
Hi, since the update from 2.3.11 to 2.3.13 some clients generate this bug : TLS handshaking: SSL_accept() failed: error:141EC044:SSL routines:tls_construct_server_key_exchange:internal error As it looks for now, they use the old SSL approach on Ports 993 and 995. SSL Config says: ssl = yes ssl_cert =
Re: problem building on centos 8 (8.3 kernel)
Hi,Yes, a whole subdir "dovecot" in /usr/lib64 with files. The actual so.0 file
is a link to an so.0.0.0 file.I was able to successfully build test run the
source rpm from qmailtoaster 2.3.11.I'm building from source because I have a
patch I want to apply. My suspicion is the problem is config. related given the
odd lsb_release issue that happens right at the start of the build.I've tried
to review the spec files for differences, qmailtoaster 2.3.11 vs 2.3.13 but the
differences are significant.SteveSent from my T-Mobile 4G LTE device--
Original message--From: Aki TuomiDate: Thu, Jan 7, 2021 3:10 AMTo:
st...@keptprivate.com;dovecot@dovecot.org;Cc: Subject:Re: problem building on
centos 8 (8.3 kernel)> On 07/01/2021 03:57 st...@keptprivate.com wrote:
>
>
> Hi,
>
> I'm converting from qmailtoaster/vpopmail build.
> When I try to build dovecot-2.3.13-2.src.rpm for centos 8.3 the first thing I
> run into is this:
>
> + sed -i 's|/etc/ssl|/etc/pki/dovecot|' doc/mkcert.sh
doc/example-config/conf.d/10-ssl.conf
> + '[' -e buildinfo.commit ']'
> ++ head -1 buildinfo.commit
> + COMMIT=89f716dc2ec7362864a368d32533184b55fb7831
> ++ /bin/sh /home/build/rpmbuild/SOURCES/lsb_release -is
> /bin/sh: /home/build/rpmbuild/SOURCES/lsb_release: No such file or directory
> + ID=
> error: Bad exit status from /var/tmp/rpm-tmp.WFaLYQ (%build)
>
>
> RPM build errors:
> Macro expanded in comment on line 455: %{_libdir}/dovecot/settings
>
> Bad exit status from /var/tmp/rpm-tmp.WFaLYQ (%build)
>
> I can get past this with an edit to the dovecot.spec file (removing
> sourcedir):
>
> if [ -e "buildinfo.commit" ]; then
>COMMIT=`head -1 buildinfo.commit`
>ID=`/bin/sh %̶{̶_̶s̶o̶u̶r̶c̶e̶d̶i̶r̶}̶/̶lsb_release -is`
>RELEASE=`/bin/sh %̶{̶_̶s̶o̶u̶r̶c̶e̶d̶i̶r̶}̶/̶lsb_release -rs`
>CODENAME=`/bin/sh %̶{̶_̶s̶o̶u̶r̶c̶e̶d̶i̶r̶}̶/̶lsb_release -cs`
>ARCH=`arch`
> fi
>
> The RPM builds but it fails to run with this message in the logs:
>
> Jan 6 20:52:11
beta1 systemd[1]: Starting Dovecot IMAP/POP3 email server...
> Jan 6 20:52:11 beta1 systemd[1]: Started Dovecot IMAP/POP3 email server.
> Jan 6 20:52:11 beta1 dovecot[356909]: /usr/sbin/dovecot: error while loading
> shared libraries: libdovecot.so.0: cannot open shared object
> file: No such file or directory
> Jan 6 20:52:11 beta1 systemd[1]: dovecot.service: Main process exited,
> code=exited, status=127/n/a
> Jan 6 20:52:11 beta1 systemd[1]: dovecot.service: Failed with result
> 'exit-code'.
>
> Any ideas what I have going wrong?
>
> Also, a side question, when I build the rpm it's not running the extensive
> tests that the old qmailtoaster source rpm used to run. I've
> looked through the spec file and I don't really see where to turn that back
> on.
>
> Sorry if any of this is stupid, but I'm new to building directly from the
> dovecot repo.
>
> Steve
I think the file is installed under /usr/lib64/, so check
ldd /usr/lib64/libdovecot.so.0
Is there some reason you are
building the rpms yourself?
Aki
Re: migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator
dsync is intended to be used to change mailbox format, so it should work just fine. that's exactly what we thought and why we use dsync to migrate like described here https://wiki2.dovecot.org/Migration/Dsync Our replication is configured according to https://wiki.dovecot.org/Replication Both processes run separately in time. Still on some accounts mails of Inbox or another folder get duplicated. We're currently trying to debug this. what are we missing? thanks Thomas On 07.01.2021 10:21, Aki Tuomi wrote: dsync is intended to be used to change mailbox format, so it should work just fine. Aki On 07/01/2021 11:17 Andrea Gabellini wrote: Hello, I had a similar problem some time ago, and the problem was the mailbox format change. Please try to migrate with the same format. Andrea Il 05/01/21 15:02, Thomas Winterstein ha scritto: No one? If there are limitations in regards to how dsync in migration and replication can operate together these should be stated clearly in the documentation. On 23.12.2020 20:33, Thomas Winterstein wrote: Hello everyone, we are working on migrating from dovecot 2.0.9 (maildir) to 2.2.36 (mdbox). The new cluster has two backend mail servers which replicate through doveadm replicator. To move the data initially we use doveadm backup (imapc). arb Our migration command doveadm -o mail_fsync=never backup -R -u $user imapc: To test the replication of new and purge of old mails with live data changes we ran imapc on a daily basis but encountered the problem that some mailboxes multiplied in size. We then made sure that imapc and replication don't run at the same time but after the first incremental imapc process, we still had the same problems. The doveadm-backup man-page states that it's possible to run it multiple times during migration. But is it also possible to have the replicator running in between? From our understanding the doveadm backup should just work as an imap connection between the servers, synchronizing all changes made on the source to the destination. Or does the conversion from maildir to mdbox format in our case produce the problems? If you're not supposed to run the replicator before having fully migrated, how can we shorten the downtime? rsync? And how can we be sure that similar problems don't occur after the migration if we can't test all mechanisms together with live data? thanks -- __ Daddy, why doesn't this magnet pick up this floppy ? __ TIM San Marino S.p.A. Andrea Gabellini Engineering R&D TIM San Marino S.p.A. - https://www.telecomitalia.sm Via Ventotto Luglio, 212 - Piano -2 47893 - Borgo Maggiore - Republic of San Marino Tel: (+378) 0549 886237 Fax: (+378) 0549 886188 -- Informativa Privacy Questa email ha per destinatari dei contatti presenti negli archivi di TIM San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione dei vostri dati presenti nei nostri archivi potete inviare una email a priv...@telecomitalia.sm. Avviso di Riservatezza Il contenuto di questa e-mail e degli eventuali allegati e' strettamente confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo immediatamente e di cancellarla dal vostro computer. E' fatto divieto di copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo delle informazioni qui contenute da parte di persone terze o comunque non indicate nella presente e-mail potra' essere perseguito ai sensi di legge. -- Thomas Winterstein http://www.rz.uni-augsburg.de/ Universität Augsburg, Rechenzentrum . Tel. (0821) 598-2068 86135 Augsburg .. Fax. (0821) 598-2028
Re: test-file-cache.c needs #ifdef HAVE_RLIMIT_AS
It compiles. --- ./src/lib/test-file-cache.c.origWed Jan 6 19:11:47 2021 +++ ./src/lib/test-file-cache.c Thu Jan 7 11:38:03 2021 @@ -254,6 +254,11 @@ test_assert(size == 0); test_assert(map == NULL); + /* OpenBSD does not support RLIMIT_AS */ + #ifndef HAVE_RLIMIT_AS + #define RLIMIT_AS RLIMIT_DATA + #endif + /* temporarily set a small memory limit to make mmap attempt fail */ struct rlimit rl_cur; test_assert(getrlimit(RLIMIT_AS, &rl_cur) == 0); ‐‐‐ Original Message ‐‐‐ On Thursday, January 7, 2021 6:45 AM, Aki Tuomi wrote: > Can you try adding this to the file? > > #define RLIMIT_AS RLIMIT_DATA > > Aki > > > On 06/01/2021 22:47 Rupert Gallagher r...@protonmail.com wrote: > > OpenBSD > > Original Message > > On Jan 6, 2021, 21:37, Aki Tuomi < aki.tu...@open-xchange.com> wrote: > > Which distro/OS is this? > > Aki
Server searches not working for 1 user only
Hi there I'm using dovecot version 2.3.4.1 precompiled in Debian stretch-backports (with Maildir, and Lucene FTS). Everything seems to be running fine but server searches by one user (precisely me) using roundcube 1.4.8. For all other checked users server searches work fine. My account is not particularly differnt from others, aprox same amount of mail. The only difference with others is that I use/check my mail constantly and from different devices at the same time (roundcube, a couple of instances of Thunderbird and Aquamail for Android always open). I only use IMAP. Googling around I read about deleting cache/index files with Dovecot recreating them automagically, but since I haven't found anything official on the Wiki, before I do something potentially stupid I wanted to confirm with you all for guidance on this Thanks so much in advance Ignacio
Re: migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator
dsync is intended to be used to change mailbox format, so it should work just fine. Aki > On 07/01/2021 11:17 Andrea Gabellini > wrote: > > > Hello, > > I had a similar problem some time ago, and the problem was the mailbox > format change. > > Please try to migrate with the same format. > > Andrea > > Il 05/01/21 15:02, Thomas Winterstein ha scritto: > > No one? > > > > If there are limitations in regards to how dsync in migration and > > replication can operate together these should be stated clearly in the > > documentation. > > > > On 23.12.2020 20:33, Thomas Winterstein wrote: > >> Hello everyone, > >> > >> > >> we are working on migrating from dovecot 2.0.9 (maildir) to 2.2.36 > >> (mdbox). The new cluster has two backend mail servers which replicate > >> through doveadm replicator. To move the data initially we use doveadm > >> backup (imapc). > >> > >> arb > >> Our migration command > >> doveadm -o mail_fsync=never backup -R -u $user imapc: > >> > >> > >> To test the replication of new and purge of old mails with live data > >> changes we ran imapc on a daily basis but encountered the problem > >> that some mailboxes multiplied in size. We then made sure that imapc > >> and replication don't run at the same time but after the first > >> incremental imapc process, we still had the same problems. > >> > >> > >> The doveadm-backup man-page states that it's possible to run it > >> multiple times during migration. But is it also possible to have the > >> replicator running in between? From our understanding the doveadm > >> backup should just work as an imap connection between the servers, > >> synchronizing all changes made on the source to the destination. Or > >> does the conversion from maildir to mdbox format in our case produce > >> the problems? > >> > >> > >> If you're not supposed to run the replicator before having fully > >> migrated, how can we shorten the downtime? rsync? And how can we be > >> sure that similar problems don't occur after the migration if we > >> can't test all mechanisms together with live data? > >> > >> > >> thanks > > > > > > -- > __ > Daddy, why doesn't this magnet pick up this floppy ? > __ > > TIM San Marino S.p.A. > Andrea Gabellini > Engineering R&D > TIM San Marino S.p.A. - https://www.telecomitalia.sm > Via Ventotto Luglio, 212 - Piano -2 > 47893 - Borgo Maggiore - Republic of San Marino > Tel: (+378) 0549 886237 > Fax: (+378) 0549 886188 > > > -- > Informativa Privacy > > Questa email ha per destinatari dei contatti presenti negli archivi di TIM > San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel > rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU > 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione > dei vostri dati presenti nei nostri archivi potete inviare una email a > priv...@telecomitalia.sm. > > Avviso di Riservatezza > > Il contenuto di questa e-mail e degli eventuali allegati e' strettamente > confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete > ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo > immediatamente e di cancellarla dal vostro computer. E' fatto divieto di > copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo > delle informazioni qui contenute da parte di persone terze o comunque non > indicate nella presente e-mail potra' essere perseguito ai sensi di legge.
Re: migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator
Hello, I had a similar problem some time ago, and the problem was the mailbox format change. Please try to migrate with the same format. Andrea Il 05/01/21 15:02, Thomas Winterstein ha scritto: > No one? > > If there are limitations in regards to how dsync in migration and > replication can operate together these should be stated clearly in the > documentation. > > On 23.12.2020 20:33, Thomas Winterstein wrote: >> Hello everyone, >> >> >> we are working on migrating from dovecot 2.0.9 (maildir) to 2.2.36 >> (mdbox). The new cluster has two backend mail servers which replicate >> through doveadm replicator. To move the data initially we use doveadm >> backup (imapc). >> >> arb >> Our migration command >> doveadm -o mail_fsync=never backup -R -u $user imapc: >> >> >> To test the replication of new and purge of old mails with live data >> changes we ran imapc on a daily basis but encountered the problem >> that some mailboxes multiplied in size. We then made sure that imapc >> and replication don't run at the same time but after the first >> incremental imapc process, we still had the same problems. >> >> >> The doveadm-backup man-page states that it's possible to run it >> multiple times during migration. But is it also possible to have the >> replicator running in between? From our understanding the doveadm >> backup should just work as an imap connection between the servers, >> synchronizing all changes made on the source to the destination. Or >> does the conversion from maildir to mdbox format in our case produce >> the problems? >> >> >> If you're not supposed to run the replicator before having fully >> migrated, how can we shorten the downtime? rsync? And how can we be >> sure that similar problems don't occur after the migration if we >> can't test all mechanisms together with live data? >> >> >> thanks > > -- __ Daddy, why doesn't this magnet pick up this floppy ? __ TIM San Marino S.p.A. Andrea Gabellini Engineering R&D TIM San Marino S.p.A. - https://www.telecomitalia.sm Via Ventotto Luglio, 212 - Piano -2 47893 - Borgo Maggiore - Republic of San Marino Tel: (+378) 0549 886237 Fax: (+378) 0549 886188 -- Informativa Privacy Questa email ha per destinatari dei contatti presenti negli archivi di TIM San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione dei vostri dati presenti nei nostri archivi potete inviare una email a priv...@telecomitalia.sm. Avviso di Riservatezza Il contenuto di questa e-mail e degli eventuali allegati e' strettamente confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo immediatamente e di cancellarla dal vostro computer. E' fatto divieto di copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo delle informazioni qui contenute da parte di persone terze o comunque non indicate nella presente e-mail potra' essere perseguito ai sensi di legge.
Re: CVE-2020-24386: IMAP hibernation allows accessing other peoples mail
On 04.01.2021 14:02, Dan Malm wrote: > On 2021-01-04 13:03, Aki Tuomi wrote: >> Vulnerable version: 2.2.26-2.3.11.3 >> Fixed version: 2.3.13 > No fix for 2.2.36? > Hi Probably not fixed - my heart's been broken to - but this solutions "imap_hibernate_timeout = 0" probably save you... -- Maciej Miłaszewski Starszy Administrator Systemowy IQ PL Sp. z o.o. Biuro Obsługi Klienta: e-mail: b...@iq.pl tel.: +48 58 326 09 90 - 94 fax: +48 58 326 09 99 Dział pomocy: https://www.iq.pl/pomoc Informacja dotycząca przetwarzania danych osobowych: https://www.iq.pl/kontakt IQ PL Sp. z o.o. z siedzibą w Gdańsku (80-298), ul. Geodetów 16, KRS 007725, Sąd rejestrowy: Sąd Rejonowy w Gdańsku VII Wydział KRS, kapitał zakładowy: 140.000 PLN, NIP 5832736211, REGON 192478853
Re: Authentication segfault with Dovecot 2.3.13
Hi,
1. legacy customer requirement...
2. we will try to remove nodelay
thanks
Am 07.01.2021 um 00:05 schrieb Josef 'Jeff' Sipek:
On Wed, Jan 06, 2021 at 14:07:06 -0500, Josef 'Jeff' Sipek wrote:
Ok, just a quick update. I managed to reproduce it. I'll try to figure out
where things went wrong.
Two more questions:
(1) Why are you using a UNION in your SQL statement?
(2) Does the crash still happen if you remove the nodelay parts of the SQL
statements?
Thanks,
Jeff.
Thanks,
Jeff.
On Wed, Jan 06, 2021 at 18:22:03 +0100, Harald Leithner wrote:
Hi
Am 06.01.2021 um 18:08 schrieb Josef 'Jeff' Sipek:
On Wed, Jan 06, 2021 at 17:13:05 +0100, Harald Leithner wrote:
Hi,
and the user part with "user@redacted".
I assume you did this for additional privacy, and not because you think that
auth_debug_passwords=no should hide usernames as well.
yes
The user uses APOP for authentication, but other users login
successfully with APOP.
Do you only use APOP? Or are other authentication schemes affected as well?
No
Can you share your config? (`doveconf -n` will be a good start, any .ext
files may be useful as well)
yes here is the dovecot -n
[root@mail:~]$ doveconf -n
# 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf
# OS: Linux 5.9.16-100.fc32.x86_64 x86_64 Generic release 32 (Generic)
# Hostname:
auth_cache_negative_ttl = 10 secs
auth_cache_size = 64 k
auth_cache_ttl = 30 secs
auth_mechanisms = CRAM-MD5 DIGEST-MD5 APOP LOGIN PLAIN
auth_username_chars =
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@%
auth_username_translation =
%@AaBbCcDdEeFfGgHhIiJjKkLlMmNnOoPpQqRrSsTtUuVvWwXxYyZz
auth_worker_max_count = 150
disable_plaintext_auth = no
imap_capability = IMAP4 IMAP4rev1 ACL RIGHTS=texk NAMESPACE CHILDREN
SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT IDLE
login_greeting =
login_log_format_elements = user=<%u> %r %m %c %k
mail_max_userip_connections = 100
passdb {
args = /etc/dovecot/sql.conf
driver = sql
}
protocols = imap pop3
service anvil {
unix_listener anvil-auth-penalty {
mode = 00
}
}
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
}
}
service imap-login {
client_limit = 300
inet_listener imap {
address = xx.xx.xx.xx
port = 143
}
inet_listener imaps {
address = xx.xx.xx.xx
port = 993
}
process_limit = 15
process_min_avail = 1
service_count = 0
vsz_limit = 512 M
}
service pop3-login {
client_limit = 300
inet_listener pop3 {
address = xx.xx.xx.xx
port = 110
}
inet_listener pop3s {
address = xx.xx.xx.xx
port = 995
}
process_limit = 15
process_min_avail = 1
service_count = 0
vsz_limit = 512 M
}
service stats {
client_limit = 1
}
shutdown_clients = no
ssl_alt_cert =
Thanks,
Jeff.
thx
Harald
Here is a stacktrace and a log dump:
Jan 6 16:29:44 mail kernel: auth[2208397]: segfault at ec ip
7f67fc147174 sp 7ffeed993150 error 4 in
libdovecot.so.0.0.0[7f67fc06e000+fc000]
Jan 6 16:29:44 mail kernel: Code: 1f 80 00 00 00 00 41 54 e8 79 fd ff
ff 31 f6 49 89 c4 48 89 c7 31 c0 e8 ca f8 ff ff 4c 89 e0 41 5c c3 0f 1f
40 00 53 48 89 fb 87 ec 00 00 00 04 75 43 48 83 3d 7b aa 0a 00 00
0f 85 50 15 f4
Jan 6 16:29:44 mail systemd[1]: Started Process Core Dump (PID
2208677/UID 0).
Jan 6 16:29:44 mail systemd-coredump[2208678]: Process 2208397 (auth)
of user 489 dumped core.#012#012Stack trace of thread 2208397:#012#0
0x7f67fc147174 event_create_passthrough (libdovecot.so.0 +
0x116174)#012#1 0x555678812d6e auth_request_finished_event (auth +
0x1bd6e)#012#2 0x5556788159ae auth_request_log_finished (auth +
0x1e9ae)#012#3 0x555678816ee0 n/a (auth + 0x1fee0)#012#4
0x555678826dc1 passdb_handle_credentials (auth + 0x2fdc1)#012#5
0x555678816c7e n/a (auth + 0x1fc7e)#012#6 0x555678824f27 n/a
(auth + 0x2df27)#012#7 0x55567881b02d
auth_request_handler_auth_begin (auth + 0x2402d)#012#8
0x55567880dfaf n/a (auth + 0x16faf)#012#9 0x7f67fc143a79
io_loop_call_io (libdovecot.so.0 + 0x112a79)#012#10 0x7f67fc144ae2
io_loop_handler_run_internal (libdovecot.so.0 + 0x113ae2)#012#11
0x7f67fc143b21 io_loop_handler_run (libdovecot.so.0 +
0x112b21)#012#12 0x7f67fc143ce0 io_loop_run (libdovecot.so.0 +
0x112ce0)#012#13 0x7f67fc0b96f3 master_service_run (libdovecot.so.0
+ 0x886f3)#012#14 0x55567880c2db main (auth + 0x152db)#012#15
0x7f67fbc9d042 __libc_start_main (libc.so.6 + 0x27042)#012#16
0x55567880c48e _start (auth + 0x1548e)
Jan 6 16:29:44 mail dovecot[2208071]: auth: Debug: client in:
AUTH#011134#011PLAIN#011service=imap#011session=tgog/jy4erm5j7ZO#011lip=lan-ip#011rip=client-ip#011lport=143#011rport=47482
Jan 6 16:29:44 mail dovecot[2208071]: auth: Debug: client passdb out:
CONT#011134
Jan 6 16:29:44 mail dovecot[2208071]: auth: Debug: client in: CONT
Jan 6 16:29:44 m
