search for: dovecot23

Distro: OpenSuSE Tumbleweed for x86_64 Failing version: dovecot23-2.3.11.3-1.1.x86_64 Install Date: 2020-08-18 Reverting to previous version works: dovecot23-2.3.10.1-2.3.x86_64 (Packages downgraded coordinately: dovecot23 dovecot23-backend-sqlite) How to make it fail: As the user, execute doveadm expunge mailbox Spam37 savedbefore 3day #User's actual...

...etc/apparmor.d/local/usr.lib.dovecot.imap-login?but still cannot login with either the mail client or with explicit openssl: it complains error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:794: I check yast2 sw_single for the dovecot installation. Indeed the module dovecot23-xxx where xxx?is anything that looks like "clnt"?( client?) does not exist. Is there a missing module in my installation? It lists only dovecot dovecot23 dovecot23-backend-mysql dovecot23-backend-pgsql dovecot23-backend-sqlite dovecot23-fts dovecot23-fts-squat...

...t;> On 29/12/17 10:00, Fabian A. Santiago wrote: >> >>> i've now completely uninstalled all traces of dovecot and reinstalled >>> from your repo and still the same issue persists with the same >>> errors. >> >> I'd be interested to know if the dovecot23* packages in GhettoForge >> Testing have the same issue: >> >> http://mirror.ghettoforge.org/distributions/gf/el/7/testing/x86_64 >> >> Peter > > ok, the gf dovecot23 packages work and i have my sieve back now. BUT, initially it didn't but the dovecot-sieve....

...en 3: structure length disagrees with data size test rpa ..................................... : ok Info: invalid NTLM response: buffer length out of bounds test ntlm ............................: ok 1 / 86 tests failed [1] https://build.opensuse.org/package/show/home:stroeder:branches:server:mail/dovecot23 Ciao, Michael. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: <https://dovecot.org/pipermail/dovecot/attachments/20200813/d2019448/attachment.sig>

Citeren jimc <jimc at jfcarter.net>: > Distro: OpenSuSE Tumbleweed for x86_64 > Failing version: dovecot23-2.3.11.3-1.1.x86_64 Install Date: 2020-08-18 > Reverting to previous version works: dovecot23-2.3.10.1-2.3.x86_64 > (Packages downgraded coordinately: dovecot23 dovecot23-backend-sqlite) > > How to make it fail: As the user, execute > doveadm expunge mailbox Spam37 savedbefore 3...

.../tcpwrap > > > > which leads me to conclusion that the new version is just not compiled with tcpwrap > > support. > > At a guess it was removed from the spec for el8 (which does not support > tcpwrap) and somehow got removed from el7 by accident. The ghettoforge > dovecot23 packages have tcpwrap support for el7: > > # rpm -qf /usr/libexec/dovecot/tcpwrap > dovecot23-2.3.11.3-1.gf.el7.x86_64 > > > Peter Hi! We are looking into this, it was indeed removed from el7 by accident. RPM macros can be quite tricky sometimes. Aki

Using the Repo http://repo.dovecot.org/ce-2.3-latest after upgrading from 2.3.10.1-3 to 2.3.11.3-3 we get numerous error messages like: dovecot: imap-login: Error: connect(tcpwrap) failed: No such file or directory We use tcpwrap support in dovecot, which worked flawlessly in the older version. I can see that the socket /var/run/dovecot/login/tcpwrap is not created anymore. And comparing with

December 28, 2017 2:52 PM, "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote: > December 28, 2017 1:21 PM, "Aki Tuomi" <aki.tuomi at dovecot.fi> wrote: > >>> On December 28, 2017 at 7:43 PM "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote: >>> >>> December 28, 2017 12:14 PM, "Aki

Aki hello, thank you. Hopefully excerpts and top posting are acceptable in the mailing list?? On that assumption: Thanks for the input. I've checked out your suggestions (details below) but unfortunately no joy. I also restored my backup 10-ssl.conf. It indeed has the "<" sign with a space before the explicit paths to the files: ? ? ssl_cert =

...ian.dhs.org> wrote: > On 29/12/17 10:00, Fabian A. Santiago wrote: > >> i've now completely uninstalled all traces of dovecot and reinstalled >> from your repo and still the same issue persists with the same >> errors. > > I'd be interested to know if the dovecot23* packages in GhettoForge > Testing have the same issue: > > http://mirror.ghettoforge.org/distributions/gf/el/7/testing/x86_64 > > Peter ok, the gf dovecot23 packages work and i have my sieve back now. BUT, initially it didn't but the dovecot-sieve.log produced a different err...

...rpa ..................................... : ok >> Info: invalid NTLM response: buffer length out of bounds >> test ntlm ............................: ok >> 1 / 86 tests failed >> >> [1] >> https://build.opensuse.org/package/show/home:stroeder:branches:server:mail/dovecot23 > > Can you provide full output for the test suite so we can tell what actually failed? You can download full log of e.g. i586 build from OBS here: https://build.opensuse.org/build/home:stroeder:branches:server:mail/openSUSE_Tumbleweed/i586/dovecot23/_log Excerpt of failed test: [ 576s]...

...le: > > /usr/libexec/dovecot/tcpwrap > > which leads me to conclusion that the new version is just not compiled with tcpwrap > support. At a guess it was removed from the spec for el8 (which does not support tcpwrap) and somehow got removed from el7 by accident. The ghettoforge dovecot23 packages have tcpwrap support for el7: # rpm -qf /usr/libexec/dovecot/tcpwrap dovecot23-2.3.11.3-1.gf.el7.x86_64 Peter

On Fri, Aug 21, 2020 at 06:02:49PM +1200, Peter wrote: > On 21/08/20 5:55 pm, Aki Tuomi wrote: > > > At a guess it was removed from the spec for el8 (which does not support > > > tcpwrap) and somehow got removed from el7 by accident. The ghettoforge > > > dovecot23 packages have tcpwrap support for el7: So is el8 truly incompatible with tcpwrap? Or is it just too much effort to continue suport for every feature that was ever in the system? If the former, might it be reasonable for a user to change the 8's in the code below to 9's? -- hendrik &g...

On 29/12/17 10:00, Fabian A. Santiago wrote: > i've now completely uninstalled all traces of dovecot and reinstalled > from your repo and still the same issue persists with the same > errors. I'd be interested to know if the dovecot23* packages in GhettoForge Testing have the same issue: http://mirror.ghettoforge.org/distributions/gf/el/7/testing/x86_64/ Peter

...ng redhat 6.10 version, if it is successful, i will > be trying the Live one's on redhat 7.7 version. > > Please help me if it is possible to install dovecot 2.3 on redhat 6.10? > This is a temporary test setup only. https://mirror.ghettoforge.org/distributions/gf/el/6/plus/x86_64/dovecot23-2.3.10.1-1.gf.el6.x86_64.rpm http://ghettoforge.org/index.php/Usage > Thanks, > Kishore Potnuru Alexander

...th data size > test rpa ..................................... : ok > Info: invalid NTLM response: buffer length out of bounds > test ntlm ............................: ok > 1 / 86 tests failed > > [1] > https://build.opensuse.org/package/show/home:stroeder:branches:server:mail/dovecot23 > > Ciao, Michael. Can you provide full output for the test suite so we can tell what actually failed? Aki

On 21/08/20 5:55 pm, Aki Tuomi wrote: >> At a guess it was removed from the spec for el8 (which does not support >> tcpwrap) and somehow got removed from el7 by accident. The ghettoforge >> dovecot23 packages have tcpwrap support for el7: > > We are looking into this, it was indeed removed from el7 by accident. RPM macros can be quite tricky sometimes. I have: %if 0%{?rhel} < 8 BuildRequires: tcp_wrappers-devel %endif ... then later ... %if 0%{?rhel} < 8 --with-libwrap \...

>>>> At a guess it was removed from the spec for el8 (which does not support >>>> tcpwrap) and somehow got removed from el7 by accident. The ghettoforge >>>> dovecot23 packages have tcpwrap support for el7: > > So is el8 truly incompatible with tcpwrap? Or is it just too much > effort to continue suport for every feature that was ever in the system? https://access.redhat.com/solutions/3906701 "The TCP Wrappers package has been deprecated in RHE...

I am a little confused here. I have been running 2.2.34 which I installed in /opt/dovecot2.2 I installed 2.3.0.1 to /opt/dovecot23 I then used config files from /opt/dovecot2.2/etc/dovecot to /opt/dovecot2.3/etc/dovecot and all I did was sed -i.BAK 's/dovecot2.2/dovecot2.3/g'. Dovecot started and was running file. Next, I manually crafted config files for 2.3.0.1 based on the example config files provided which diff-...

...1...(no debugging symbols found)...done. > Loaded symbols for /lib64/libgcc_s.so.1 > Core was generated by `dovecot/imap'. > Program terminated with signal 6, Aborted. > #0 0x00007f9b50c9f495 in raise () from /lib64/libc.so.6 > Missing separate debuginfos, use: debuginfo-install dovecot23-2.3.0-3.gf.el6.x86_64 My Dovecot configuration is: ---snip--- # 2.3.0 (c8b89eb): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.0.1 (d33dca20) # OS: Linux 2.6.32-696.3.1.el6.x86_64 x86_64 CentOS release 6.9 (Final) ext4 auth_debug = yes auth_debug_passwords = yes auth_master_user_separator =...