similar to: Upgrading dovecot 2.2 to 2.3 without downtime when using proxy/director?

On 9/9/19 6:18 PM, @lbutlr via dovecot wrote: > On 9 Sep 2019, at 09:27, Niels Kobsch?tzki <niels at kobschaetzki.net> wrote: >> The moment I remove those folders, the size gets calculated correctly. Unfortunately those folders are generated by some clients automatically afaik (like .INBOX.Trash) >> That sounds like a misconfiguration of the IMAP client. Someone has gone in

> On 6 May 2018, at 8.46, Niels Kobsch?tzki <niels at kobschaetzki.net> wrote: > > Hi, > > I have a setup with several dovecot-servers (2.2.35) and I use dovecot > proxy. I upgraded one server to 2.3.1 and got the configs fixed so far > that it started again. But when I tried to add it into the proxying > again with "doveadm director add" I see the

On 15 May 2018, at 12.06, Timo Sirainen <tss at iki.fi> wrote: > > If you look at .176's error log, do you see an error about "director_consistent_hashing settings differ between directors"? Have you set director_consistent_hashing=yes in the old directors? That is needed now, because the old non-consistent-hashing method is obsoleted. Unfortunately there's no easy

Hi, we just upgraded on FreeBSD (11.2-p14) from Dovecot 2.2 to Dovecot 2.3.7.2 and now we have kind of a big problem: the quota-plugin does not work correctly anymore. If a user has a subfolder of the INBOX (like .INBOX.foobar) the quota-calculation does not work anymore. It seems to be arbitrary but users get counted like double and more than they actually have in mails (the number of mails is

Hi, I have a setup with 3 Dovecot Director v2.2.36 and director_consistent_hashing = yes ;-) Now I would like to upgrade to 2.3.7, first only Director and after also Backend. Can works fine a ring of director with mixed 2.2 and 2.3 version? Mi idea is to setup a new Director server with 2.3, stop one server with 2.2 and insert the new 2.3 in the current ring to check if works fine. If all

On Mon, Sep 9, 2019 at 8:57 PM Niels Kobsch?tzki via dovecot < dovecot at dovecot.org> wrote: > On 9/9/19 6:18 PM, @lbutlr via dovecot wrote: > > On 9 Sep 2019, at 09:27, Niels Kobsch?tzki <niels at kobschaetzki.net> > wrote: > >> The moment I remove those folders, the size gets calculated correctly. > Unfortunately those folders are generated by some clients

Do both replication nodes need to be updated at the same time? Or can a 2.2(.36.4) node replicate with a 2.3(.10.1)? Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Gesch?ftsf?hrer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0 -------------- next part -------------- A non-text attachment was

On 9 Sep 2019, at 09:27, Niels Kobsch?tzki <niels at kobschaetzki.net> wrote: > The moment I remove those folders, the size gets calculated correctly. Unfortunately those folders are generated by some clients automatically afaik (like .INBOX.Trash) That sounds like a misconfiguration of the IMAP client. Someone has gone in and improperly set INBOX as the IMAP path Prefix in their MUA. I

Hi, I am trying to use dovecot replication for a two-way sync. And whatever I do, sieve-scripts won?t replicate. Mails replicate near instantaneous. When I disable the sieve-script in roundcube, the other server will create in the home of the user on the other side a folder sieve/tmp but enabling won?t create the roundcube.sieve and the symlink .dovecot.sieve -> sieve/roundcube.sieve The

On Thu, Feb 23, 2017 at 3:15 PM, Timo Sirainen <tss at iki.fi> wrote: > On 24 Feb 2017, at 0.08, Mark Moseley <moseleymark at gmail.com> wrote: > > > > As someone who is about to begin the process of moving from maildir to > > mdbox on NFS (and therefore just about to start the 'director-ization' of > > everything) for ~6.5m mailboxes, I'm

Il 18/07/19 21:42, Timo Sirainen ha scritto: > On 18 Jul 2019, at 11.44, Alessio Cecchi via dovecot > <dovecot at dovecot.org <mailto:dovecot at dovecot.org>> wrote: >> >> Hi, >> >> I have a setup with 3 Dovecot Director v2.2.36 and >> director_consistent_hashing = yes ;-) >> >> Now I would like to upgrade to 2.3.7, first only Director

On 18 Jul 2019, at 11.44, Alessio Cecchi via dovecot <dovecot at dovecot.org> wrote: > > Hi, > > I have a setup with 3 Dovecot Director v2.2.36 and director_consistent_hashing = yes ;-) > > Now I would like to upgrade to 2.3.7, first only Director and after also Backend. > > Can works fine a ring of director with mixed 2.2 and 2.3 version? > > Mi idea is to

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

Hi, I'm setting up an IMAP/POP cluster using dovecot director for some NFS reasons and I'm getting some troubles with director_servers directive. Configuration is shared on both nodes : director_servers = 10.0.50.50 10.0.50.51 director_mail_servers = 192.168.0.150 192.168.0.151 director_user_expire = 15 min service director { unix_listener login/director { mode = 0666 }

Hi Timo Heiko Schlittermann <hs at schlittermann.de> (Mi 14 Okt 2015 01:10:20 CEST): ? > Ah, the information comes from the other director running. The other one > is using an unpatched version of dovecot. Your patch for backend-certificate verification works. Thank you for the good and fast work. Is there any chance that this will make it into Dovecot's next release? BTW: The

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

Hello dovecot community, first of all: dovecot ist great! ;) ...nevertheless I?ve got some problems to get my director scenario running as needed/expected :( My scenario: I?d like to configure two dovecot backends, without the need for multiple dovecot instances. Both backend servers are active/active and act on top of a glusterfs storage, which implies the need for dovecot director. As

Hi, I've been running dovecot for many years, but now i've hit a strange problem. when retrieving imap there is sometimes in 1 of 4 imap requests a 4sec latency. * notes: - connected directly to the backends this latency disappears - removing a director from the loadbalancer(lvs) so i'm the only connected to the director this latency disappears too I would appreciate some feedback

Hi All, I can't get directory proxying of pop3 and imap working.? The director stuff appears to be OK - see below.?? The ldap authentication is working on the backend mail server.? I just get connection refused when I telnet to the proxy on the pop3 and imap ports.? Nothing appears to be running on the pop3 and imap ports despite the lines in the config below.? I am not sure what to do from

Hi Timo & everyone, I'm trying out a 2-node director setup, but I keep getting the following error: Oct 3 16:11:29 imapdir1 dovecot: master: Dovecot v2.0.15 starting up (core dumps disabled) Oct 3 16:11:34 imapdir1 dovecot: director: Error: connect(132.198.100.150:9090) failed: Invalid argument Oct 3 16:11:41 imapdir1 last message repeated 3 times Both nodes report this error. The