similar to: Dovecot Replication - Architecture Endianness?

On 4/05/2015 11:06 PM, Teemu Huovila wrote: > On 05/03/2015 01:48 PM, Reuben Farrelly wrote: >> Hi all, >> >> I've had an interesting use case come up which - to cut the story short - one way to solve the problem I am looking at may be to >> replicate a small number of mailboxes to a third remote server. >> >> I've currently had replication running

On 4/05/2015 11:06 PM, Teemu Huovila wrote: >> Also is there a way to restrict replication users aside from a crude hack around system first and last UIDs? > You can set the userdb to return an empty mail_replica variable for users you want to exclude from replication. > http://hg.dovecot.org/dovecot-2.2/rev/c1c67bdc8752 > > br, > Teemu Huovila One last question. Is it

On 7/05/2015 7:49 AM, Timo Sirainen wrote: > On 06 May 2015, at 13:52, Reuben Farrelly <reuben-dovecot at reub.net> wrote: >> >> On 4/05/2015 11:06 PM, Teemu Huovila wrote: >>>> Also is there a way to restrict replication users aside from a crude hack around system first and last UIDs? >>> You can set the userdb to return an empty mail_replica variable for

On 8/05/2015 6:10 PM, Teemu Huovila wrote: > On 05/07/2015 02:32 PM, Reuben Farrelly wrote: >> On 7/05/2015 7:49 AM, Timo Sirainen wrote: >>> On 06 May 2015, at 13:52, Reuben Farrelly >>> <reuben-dovecot at reub.net> wrote: >>>> >>>> On 4/05/2015 11:06 PM, Teemu Huovila wrote: >>>>>> Also is there a way to restrict

On 05/03/2015 01:48 PM, Reuben Farrelly wrote: > Hi all, > > I've had an interesting use case come up which - to cut the story short - one way to solve the problem I am looking at may be to > replicate a small number of mailboxes to a third remote server. > > I've currently had replication running between my main dovecot machine and another remote VM for some time and

On 04 May 2015, at 17:11, Reuben Farrelly <reuben-dovecot at reub.net> wrote: > > On 4/05/2015 11:06 PM, Teemu Huovila wrote: >> On 05/03/2015 01:48 PM, Reuben Farrelly wrote: >>> Hi all, >>> >>> I've had an interesting use case come up which - to cut the story short - one way to solve the problem I am looking at may be to >>> replicate a

On 05/07/2015 02:32 PM, Reuben Farrelly wrote: > On 7/05/2015 7:49 AM, Timo Sirainen wrote: >> On 06 May 2015, at 13:52, Reuben Farrelly <reuben-dovecot at reub.net> wrote: >>> >>> On 4/05/2015 11:06 PM, Teemu Huovila wrote: >>>>> Also is there a way to restrict replication users aside from a crude hack around system first and last UIDs?

Seems there is some breakage with -hg latest - 2.2.16 (86f535375750+). I've just had 4 core files created in short succession on both servers in the replication set. Here's the first... tornado reuben # gdb /usr/libexec/dovecot/imap core GNU gdb (Gentoo 7.9 vanilla) 7.9 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

Hi, On 30/10/2017 7:22 PM, dovecot-request at dovecot.org wrote: > Message: 6 > Date: Mon, 30 Oct 2017 10:22:42 +0200 > From: Teemu Huovila <teemu.huovila at dovecot.fi> > To: dovecot at dovecot.org > Subject: Re: dovecot-2.3 (-git) Warning and Fatal Compile Error > Message-ID: <7d2c0b5b-019a-067c-c6be-f36571ed9a96 at dovecot.fi> > Content-Type: text/plain;

On 06 May 2015, at 13:52, Reuben Farrelly <reuben-dovecot at reub.net> wrote: > > On 4/05/2015 11:06 PM, Teemu Huovila wrote: >>> Also is there a way to restrict replication users aside from a crude hack around system first and last UIDs? >> You can set the userdb to return an empty mail_replica variable for users you want to exclude from replication. >>

http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz.sig Quite a lot of changes, so here's a release candidate first. If no problems are reported I'll make v2.2.17 release early next week. Please test especially non-Linux systems as there are some larger configure/Makefile changes done since v2.2.16. * Dovecot no

http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz.sig Quite a lot of changes, so here's a release candidate first. If no problems are reported I'll make v2.2.17 release early next week. Please test especially non-Linux systems as there are some larger configure/Makefile changes done since v2.2.16. * Dovecot no

Hi People, I recently setup a replication service within dovecot between two machines in different datacenters, which has the following configuration; (yes it is hashed out, because I needed to) #service replicator { # unix_listener replicator-doveadm { # mode = 0666 # } # process_min_avail = 1 #} # #service aggregator { # fifo_listener replication-notify-fifo { # mode = 0666 #

Teemu, If just need the http request, I will need something like the following configuration, right? So no meta data plugin, but with notify and push_notification? protocol lmtp { mail_plugins = $mail_plugins notify push_notification } plugin { push_notification_driver = ox:url=http://myurl/ <http://login:pass at node1.domain.tld:8009/preliminary/http-notify/v1/notify> }

On Monday 01 December 2014 03:41 PM, Teemu Huovila wrote: > On 11/30/2014 05:53 AM, AMM wrote: >> __strspn_sse42 (in /lib64/libc-2.14.90.so) > Is it possible that you are encountering this issue? https://bugs.kde.org/show_bug.cgi?id=270925 > Either way, the error seems to stem from your libc implementation (if it is not the valgrind bug). > > If possible, upgrade your

On 04/25/2015 11:55 AM, James wrote: > On 24/04/2015 22:17, Hanno B?ck wrote: > > Hello, > >> I tracked down a tricky bug in dovecot that can cause the imap-login >> and pop3-login processes to crash on handshake failures. >> This can be tested by disabling SSLv3 in the dovecot config >> (ssl_protocols = !SSLv2 !SSLv3) and trying to connect with openssl and

On 04/26/2015 04:07 PM, Florian Pritz wrote: > Since there are three people involved I kindly ask you to be more > specific as to who should provide which (exact) information. > > Given you ask for it right after quoting my link all I can tell you is > that I provide all the information you ask for (openssl version, crash > message) in the link you quoted. Sorry if I was not

Ah fantastic. Now I guess I can use notify plugin without push_notification metadata plugins, right? On 26-10-15 08:36, Teemu Huovila wrote: > > On 26.10.2015 08:59, Frederik Bosch | Genkgo wrote: >> Thanks again. Final question: how do I configure this plugin? > As the only existing driver at the moment is the OX one, the plugin is documented in OX wiki at >

On 18.05.2017 10:55, Tom Sommer wrote: > On 2017-05-18 09:36, Teemu Huovila wrote: >> Hello Tom >> >> On 02.05.2017 11:19, Timo Sirainen wrote: >>> On 2 May 2017, at 10.41, Tom Sommer <mail at tomsommer.dk> wrote: >>>> >>>> (gdb) bt full >>>> #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298 >>>>

I have postfix/dovecot setup on a virtual gentoo server. It's been in service for almost two years without any issues. Now I want to set up a spare server to replicate mails from the one running. I copied the vm files to the second host server, changed the ip, hostname and hosts file for the copy and followed the dovecot replication doc. The last point in the doc tells to rundovecot