Re: SQL-AUTH driver replace for VPOPMAIL-AUTH
It seems like it would be possible to use a view table (with a union query) to
"make" the many domain style table out of the tables by domain. You wouldn't
want to do that if you were adding domains often... but it should make the
dovecot auth for many domains work on top of the old tables instantly.Sent from
my T-Mobile 4G LTE device-- Original message--From: Eric BrochDate:
Wed, Feb 10, 2021 2:58 PMTo: dovecot@dovecot.org;Cc: Subject:Re: SQL-AUTH
driver replace for VPOPMAIL-AUTHPablo,
Can you share your dovecot-sql.conf.ext file for 'one table for each
domain'.
Eric
On 2/10/2021 9:24 AM, Pablo Murillo wrote:
> Hi Aki
>
>
> Don't work, but you give me a new idea
> I set default_pass_scheme = PLAIN on dovecot-sql.conf.ext anda I send
> the pass encrypted and now is working !
>
> On 2/10/2021 3:34 AM, Aki Tuomi wrote:
>> Return the password with {CRAM-MD5} or {MD5-CRYPT} prefix, then
>> dovecot will know the password scheme.
>>
>> Aki
>>
>>> On 10/02/2021 05:04 Pablo
Murillo wrote:
>>>
>>> Hi
>>>
>>> I'm made a lot of test trying to get SLQ auth driver work with
>>> vpopmail/mysql configured with many domains (one table for each domain)
>>> Finally I made it work, but ... only with PLAIN password
>>> Is there a way to make SQL auth work with vpopmail/mysql tables with
>>> encrypted password (CRAM-MD5 / MD5-CRYPT) ?
>>>
>>> Thanks
>>> Pablo Murillo
>>>
>>>
>>>
>>> --
>>> This email has been checked for viruses by AVG.
>>> https://www.avg.com
Re: dovecot 2.3.13 : make check FAILURE : Assert failed: buffer_append_full_file
I was experiencing multiple failures with make check on a fresh installation of CentOS 8.3.The solution for me was to use mock instead of rpmbuild. (I was not building as root with rpmbuild.) With mock all tests were successful. Sent from my T-Mobile 4G LTE device-- Original message--From: J LumbyDate: Sat, Jan 16, 2021 11:31 AMTo: dovecot@dovecot.org;Cc: Subject:dovecot 2.3.13 : make check FAILURE : Assert failed: buffer_append_full_fileAfter successfully building dovecot 2.3.13 (linux kernel 5.10.1 , glibc-2.32 , gcc-9.3) make check had one failure as follows : test-buffer-istream.c:54: Assert failed: buffer_append_full_file(result, TEST_FILENAME, SIZE_MAX, ) == BUFFER_APPEND_READ_ERROR test-buffer-istream.c:56: Assert failed: error != NULL && *error != '\0' buffer_append_full_file .. : FAILED After a brief look at the referenced code in test-buffer-istream.c , I can't find out what this FAIL really means or whether it is serious. The assert is finding that the result of the call to buffer_append_full_file is not BUFFER_APPEND_READ_ERROR, but it does not report what the result code actually was. Maybe errno was actually 0 and call succeeded? I don't know. Nor can I see how to add some code to find out. Can anyone offer any advice on what this means and/or how to investigate? Cheers, John Lumby
Re: status of test code
Update:I was finally able to build 2.3.13 on centos 8 (8.3). I managed this by going back to the qmailtoaster spec file, removing a few things no longer relevant (vpopmail) and disabling all the tests. Most tests were still running but there were also many that did not. The good news is the resulting executable in the RPM no longer complains about not being able to find libdovecot.so. i've done some basic testing on imap and everything appears to be working.Someone who maintains the tests and rpm build should really have a look. Doing a build on a fresh centos 8 machine, as I was able to with the qmailtoaster source rpm, should really be much simpler. My impression is the current spec file may have edits that were eroneously committed? SteveSent from my T-Mobile 4G LTE device-- Original message--From: steve@keptprivate.comDate: Sat, Jan 9, 2021 3:42 PMTo: dovecot@dovecot.org;Cc: Subject:status of test codeHi, I'm continuing to try to build 2.3.13 with a source RPM. At this point I've taken the source zip file and I'm working with the previously working qmailtoaster SPEC file and RPM build process. The toaster SPEC file runs the built-in dovecot tests after build... 2.3.11 would make it through all the tests with a few minor exceptions. 2.3.13 seems no longer able to run the test is lib-ssl-iostream or lib-lua (and perhaps others, but that's as far as I've gotten). I can selectively disable the tests to make progress, but it raises the question of what the plans are for the built-in tests. Also, I continue to not be able to find where all the testing is turned on/off at once? I'm sure it will be obvious when someone tells me but please tell me, because I'm pulling my hair out. Steve
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
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
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
