search for: director1

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 2001:x:y:f33::5:1 (director1) directors.<domain> has IPv6 address 2001:x:y:f33::5:2 (director2) But connecting the the neighbor director gives: Oct 13 21:23:2...

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

...t; > 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 2001:x:y:f33::5:1 (director1) > directors.<domain> has IPv6 address 2001:x:y:f33::5:2 (director2) > > But connecting the the neighbor director...

...on't think it's going to be of much use. login process's client_auth_parse_args() is what should see these two parameters correctly. > > I can check this further tomorrow. I've put an i_warning("*** %s: ...", __FUNCTION__, ...) into several places. Oct 14 00:02:33 director1 dovecot: director: Warning: *** login_host_callback: OK#0112#011user=foo#011proxy#011ssl=yes#011nopassword=y#011lip=2001:x.y:f33::5:1#011lport=993#011pass=x#011proxy_refresh=450#011host=2001:x.y:f33::5:fe Here it seems that the director doesn't send it's knowledge about the hostname. Here...

...to be of much use. login process's client_auth_parse_args() is what should see these two parameters correctly. > > > > I can check this further tomorrow. > > I've put an i_warning("*** %s: ...", __FUNCTION__, ...) into several places. > > Oct 14 00:02:33 director1 dovecot: director: Warning: *** login_host_callback: OK#0112#011user=foo#011proxy#011ssl=yes#011nopassword=y#011lip=2001:x.y:f33::5:1#011lport=993#011pass=x#011proxy_refresh=450#011host=2001:x.y:f33::5:fe > > Here it seems that the director doesn't send it's knowledge about the >...

...;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 (Ubuntu) ready. LHLO mailhub1.rz.hs-example.de 250-director1.rz.hs-example.de 250-8BITMIME 250-ENHANCEDSTATUSCODES 250 PIPELINING MAIL FROM:<hs at schlittermann.de> 250 2.1.0 OK RCPT TO:&lt...

...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 >= 0) Nov 23 09:15:31 cc-director1 dovecot: imap-login: Panic: file ioloop.c: line 35 (io_add): assertion failed: (fd >= 0) Nov 23 09:55:48 cc-director1 dovecot: imap-login: Panic: file ioloop.c: line 35 (io_ad...

Is there a specific order in which one has to add servers to director_mail_servers, Let's say I have 20 loadbalanced director servers (I dont, but for arguments sake). I want to add 5 servers to director_mail_servers. If I do this by restarting each director server 1 by 1 with an updated conf, it seems the 5 new servers dont get added. Or at least I dont get what makes it work eventually.

Hi I'm doing: doveadm force-resync -S director1:1234 -A "*" The director gives this error: Jul 06 16:17:29 auth: Error: Trying to iterate users, but userdbs don't support it Jul 06 16:17:29 doveadm: Error: User listing returned failure Jul 06 16:17:29 doveadm: Error: Failed to iterate through some users The director has "i...

Hi Timo, Upgraded to 2.0.14 last night for the director-related features and I noticed an oddity in the logs: Sep 28 09:53:21 director2 dovecot: master: Warning: service(ipc): client_limit reached, client connections are being dropped Sep 28 09:53:56 director1 dovecot: master: Warning: service(ipc): client_limit reached, client connections are being dropped Sep 28 09:54:23 director2 dovecot: master: Warning: service(ipc): client_limit reached, client connections are being dropped Sep 28 09:55:07 director1 dovecot: master: Warning: service(ipc): client_li...

Hi Timo, Periodic segfaults with doveadm proxy list: root at director1:~) doveadm proxy list doveadm(root): Error: LIST failed: Disconnected Segmentation fault (core dumped) Sometimes it's just the 'LIST failed' error, other times it's the error with the segfault. Usually the first attempt to call it works, subsequent attempts fail. I've attached...

...config -n # 2.1.8: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-220.17.1.el6.x86_64 x86_64 Red Hat Enterprise Linux Server release 6.2 (Santiago) auth_debug = yes auth_master_user_separator = * auth_verbose = yes director_mail_servers = buzones2.ehu.es buzones3.ehu.es director_servers = director1.ehu.es director2.ehu.es doveadm_proxy_port = 4444 lmtp_proxy = yes mail_debug = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables bo...

...looded by these errors: >> >> lmtp[45758]: segfault at 21 ip 00007fb412d3ad11 sp 00007ffe83ad2df0 >> error 4 in libdovecot.so.0.0.0[7fb412c95000+11c000] >> >> Any ideas? >> >> -- >> Tom > > Try get a core dump and run it thru gdb. [root at director1 dovecot]# gdb /usr/libexec/dovecot/lmtp core.19749 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribut...

...ll do more testing. Good work, thank you. BTW: I've put there an IPv6 address into the director_servers list (not an DNS name). director_servers = 2001:x:y:f33::5:1 ? inet_listener { address = :: port = 9090 } it doesn't recognize itself: Oct 14 01:06:13 director1 dovecot: director: Fatal: director_servers doesn't list ourself director_servers = 2001:x:y:f33::5:1:9090 ? inet_listener { address = :: port = 9090 } works, but is ambigous, isn't it? Shouldn't we use [2001:x:y:f33::5:1]:9090 in such a case? But: *Unkn...

Dear all, We would like to setup, if possible, for example: We have 4 example groups, we various users in those groups: Directors director1,director2 Support manager1,support1,support2,support3 Enquiries manager2,enquiry1,enquiry2,enquiry3 Accounts manager3, accounts1,account2 Shared Mailboxes: Support: Support, user1, user2, user3 Accounts: Directors, Support So basically, we want 2 public folder shares, with the names: Support...

...ain goal is high availability. CRAM-MD5 auth is working fine if I connect directly to the backends, but the director only supports AUTH=PLAIN because of the static passdb. director config: > passdb { > driver = static > args = nopassword=y proxy=y > } > > director_servers = director1 director2 > director_mail_servers = backend1 backend2 backend config: > passdb { > driver = vpopmail > args = > } > > userdb { > driver = vpopmail > } It seems that the director is only working, if I use the static passdb?! How can I use the director with other...

...00007fb412d3ad11 sp 00007ffe83ad2df0 >>>> error 4 in libdovecot.so.0.0.0[7fb412c95000+11c000] >>>> >>>> Any ideas? >>>> >>>> -- Tom >>> >>> Try get a core dump and run it thru gdb. >> >> >> [root at director1 dovecot]# gdb /usr/libexec/dovecot/lmtp core.19749 >> GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6) >> Copyright (C) 2010 Free Software Foundation, Inc. >> License GPLv3+: GNU GPL version 3 or later >> <http://gnu.org/licenses/gpl.html> >> This is free sof...

...lmtp[45758]: segfault at 21 ip 00007fb412d3ad11 sp 00007ffe83ad2df0 >>> error 4 in libdovecot.so.0.0.0[7fb412c95000+11c000] >>> >>> Any ideas? >>> >>> -- >>> Tom >> >> Try get a core dump and run it thru gdb. > > > [root at director1 dovecot]# gdb /usr/libexec/dovecot/lmtp core.19749 > GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6) > Copyright (C) 2010 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > <http://gnu.org/licenses/gpl.html> > This is free software: you are free...

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 Maby stupid question :) It possible to have 3 directors (frontend) but without rings ? All directors connect to this same dovecot (backend) - all backad have this same login_trusted_networks -- Maciej Mi?aszewski IQ PL Sp. z o.o. Starszy Administrator Systemowy