similar to: Director/Doveadm: Trying to iterate users, but userdbs don't support it

Sorry to bump up an old thread. 2.3.11.3 already contains this patch and the error still gets generated.? Anything else we could try ? Scott On Wednesday, 19/08/2020 at 11:37 Josef 'Jeff' Sipek wrote: On Wed, Aug 19, 2020 at 17:03:57 +0200, Alessio Cecchi wrote: > Hi, > > after the upgrade to Dovecot 2.3.11.3, from 2.3.10.1, I see frequently > these errors from

Hi, Thank you for your reply. I hope this bug to be fixed soon. :) Thank you. Tachibana ----- Original Message ----- > On Mon, Jul 20, 2020 at 09:43:12 -0400, Josef 'Jeff' Sipek wrote: > > On Mon, Jul 20, 2020 at 20:24:13 +0900, TACHIBANA Masashi wrote: > ... > > Thanks for the report. I reproduced it locally, but I'm not sure what is > > causing it yet.

Sorry about that. My FreeBSD system automatically applied your patches and I assumed they were already part of the master. Unfortunately it still means the bug isn't resolved with these changes. On Wednesday, 02/09/2020 at 15:34 Josef 'Jeff' Sipek wrote: On Wed, Sep 02, 2020 at 15:07:37 -0400, Scott Q. wrote: > Sorry to bump up an old thread. > > 2.3.11.3 already

Hi, still using 2.2.9, I've two directors, and these directors use both IPv4/IPv6 addresses. `host directors.<domain>` returns one A and AAA for each of the two directors: directors.<domain> has address 149.x.y.96 (director1) directors.<domain> has address 149.x.y.97 (director2) directors.<domain> has IPv6 address

Heiko Schlittermann <hs at schlittermann.de> (Mi 14 Okt 2015 00:10:50 CEST): > Timo Sirainen <tss at iki.fi> (Di 13 Okt 2015 23:49:20 CEST): > ? > > > > Proxying in general does check that hostname matches the SSL certificate, because both the hostname and IP address are sent to login process. So it should work in a way that host=<hostname> and

On 2017-05-02 09:35, Aki Tuomi wrote: > On 2017-05-02 10:20, Tom Sommer wrote: >> On 2017-05-01 19:26, Aki Tuomi wrote: >>>> On May 1, 2017 at 8:21 PM Tom Sommer <mail at tomsommer.dk> wrote: >>>> >>>> >>>> I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my >>>> dmesg >>>> and /var/log/messages

On 2017-05-01 19:26, Aki Tuomi wrote: >> On May 1, 2017 at 8:21 PM Tom Sommer <mail at tomsommer.dk> wrote: >> >> >> I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg >> and /var/log/messages are getting flooded by these errors: >> >> lmtp[45758]: segfault at 21 ip 00007fb412d3ad11 sp 00007ffe83ad2df0 >> error 4 in

On Wed, Sep 02, 2020 at 15:07:37 -0400, Scott Q. wrote: > Sorry to bump up an old thread. > > 2.3.11.3 already contains this patch and the error still gets > generated.? I'm not sure where you are finding it. The below patch isn't on the release-2.3.11 branch. It isn't in the 2.3.11.3 tarball. It isn't even on master. Those two files haven't been touched since

On Tue, Jul 21, 2020 at 08:18:21 +0900, TACHIBANA Masashi wrote: > Hi, > > Thank you for your reply. > > I hope this bug to be fixed soon. :) It is a tricky one because as far as I can tell, the From header is invalid. So, we have to figure out the best way to handle such input. The input is invalid because '@' is not allowed by the RFC to be in the name portion of an

On 14 Oct 2015, at 00:34, Heiko Schlittermann <hs at schlittermann.de> wrote: > > Hi Timo, > > Heiko Schlittermann <hs at schlittermann.de> (Di 13 Okt 2015 22:33:23 CEST): >>> Does the attached patch work? Compiles, but untested. >> I'm about to test it. > > It seems to update the struct mail_host, but it looks as if the data > in mail_host

Timo Sirainen <tss at iki.fi> (Di 13 Okt 2015 23:49:20 CEST): ? > > Proxying in general does check that hostname matches the SSL certificate, because both the hostname and IP address are sent to login process. So it should work in a way that host=<hostname> and hostip=<ip> is sent. I thought my patch did that.. Normally auth_debug=yes would be enough to debug this, but

Hello, I'm using dovecot 2.2.9 and a director/backend setup. On the director I've the LMTP in proxy mode, mapping the users to one of the backends. The backends to quota check and return the OverQuota message already at RCPT TO time. Here is what I typed, connected to the director Connection to director1 2525 port [tcp/*] succeeded! 220 director1.rz.hs-example.de Dovecot

hello ! I'm trying to get users from dovecot director server: doveadm director map doveadm(root): Error: User listing returned failure doveadm(root): Error: user listing failed user mail server ip expire time <unknown> 192.168.5.101 2012-06-10 21:54:06 in

Timo, Just this morning I upgraded from 2.0.6 to 2.0.7 (hg changeset 66a523135836). A few hours later we had some power problems that caused the networking to drop out at one site. The directors on the surviving site all had a few imap-login processes crash with the following error: Nov 23 09:15:30 cc-director1 dovecot: imap-login: Panic: file ioloop.c: line 35 (io_add): assertion failed: (fd

On 13 Oct 2015, at 22:31, Heiko Schlittermann <hs at schlittermann.de> wrote: > > Hi, > > still using 2.2.9, I've two directors, and these directors > use both IPv4/IPv6 addresses. > > `host directors.<domain>` returns one A and AAA for each > of the two directors: > > directors.<domain> has address 149.x.y.96 (director1)

I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg and /var/log/messages are getting flooded by these errors: lmtp[45758]: segfault at 21 ip 00007fb412d3ad11 sp 00007ffe83ad2df0 error 4 in libdovecot.so.0.0.0[7fb412c95000+11c000] lmtp[46304]: segfault at 91 ip 00007f771ba64d11 sp 00007ffe830635a0 error 4 in libdovecot.so.0.0.0[7f771b9bf000+11c000] lmtp[45775]: segfault at

Hi, I've almost finished my new director based setup, but in the first test I discovered that imap and lmtp connections were not always being proxied to the same server. After some research now I think that the main problem is that in imap connections users connect as 'username' while lmtp connections are as 'username at mailserver'. In my current setup I receive mail via

On 2019-03-20 16:40, Sami Ketola via dovecot wrote: >> On 20 Mar 2019, at 17.13, Tom Sommer via dovecot <dovecot at dovecot.org> >> wrote: >> >> I realize quota-service on Director is not supported, which is a >> shame. >> >> As a workaround I'm thinking of setting up quota-service on one of my >> backend nodes, and have all my

Using the host name of the volume, its related gluster commands can become very slow .For example,create,start,stop volume,nfs related commands. and some time And in some cases, the command will return Error : Request timed out but If using ip address to create the volume. The volume all gluster commands are normal. I have configured /etc/hosts correctly,Because,SSH can normally use the

On 2019-03-21 10:28, Sami Ketola via dovecot wrote: >> On 20 Mar 2019, at 18.17, Tom Sommer via dovecot <dovecot at dovecot.org> >> wrote: >> >> >> On 2019-03-20 16:40, Sami Ketola via dovecot wrote: >> >>>> On 20 Mar 2019, at 17.13, Tom Sommer via dovecot >>>> <dovecot at dovecot.org> wrote: >>>> I realize