Re: dovecot-pigeonhole Missing sieve_imapsieve Plugin?

2018-06-07 Thread Will Foster 
On Thu, Jun 07, 2018 at 07:02:40PM +0200, Christian Kivalo wrote:
> 
> 
> On June 7, 2018 6:47:54 PM GMT+02:00, Will Foster  wrote:
> >Hi Folks,
> >
> >I am having a problem configuring imapsieve via dovecot-pidgeonhole on
> >CentOS7.
> >
> >After following the docs here:
> >
> >https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve
> >
> >I get:
> >
> >dovecot[22026]: managesieve: Fatal: Plugin 'sieve_imapsieve' not found
> >from directory /usr/lib64/dovecot/sieve
> >dovecot[22026]: doveconf: Error: managesieve-login: dump-capability
> >process returned 89
> >
> >There doesn't seem to be that plugin present or provided by
> >dovecot-pigeonhole
> >
> ># ls -lah /usr/lib64/dovecot/sieve/
> >total 56K
> >drwxr-xr-x. 2 root root   46 Jun  5 12:16 .
> >drwxr-xr-x. 7 root root 4.0K Jun  5 12:16 ..
> >-rwxr-xr-x. 1 root root  52K Aug  3  2017
> >lib90_sieve_extprograms_plugin.so
> >
> >Am I doing something wrong?  This is provided via the CentOS EPEL
> >package
> >
> >Here's my system details:
> >
> >* dovecot-pigeonhole-2.2.10-8.el7.x86_64
> >* CentOS 7.5 on XFS
> >* Rainloop Webmail / Mutt / IMAP access
> 
> As written on the imapsieve wiki page you linked above, the imapsieve plugin 
> is available with pigeonhole 0.4.14 which requires dovecot 2.2.24. 
> 

Thanks, I seemed to have missed that.  I've found a bugzilla that seems related
and commented on it, hoping to get it fixed in upstream RHEL/CentOS instead of
building it myself.

https://bugzilla.redhat.com/show_bug.cgi?id=1489943

-will

> >Here's my dovecot -n
> >
> >
> >
> ># 2.2.10: /etc/dovecot/dovecot.conf
> >managesieve(root): Fatal: Plugin 'sieve_imapsieve' not found from
> >directory /usr/lib64/dovecot/sieve
> >doveconf: Error: managesieve-login: dump-capability process returned 89
> ># OS: Linux 3.10.0-862.2.3.el7.x86_64 x86_64 CentOS Linux release
> >7.5.1804 (Core)
> >first_valid_uid = 1000
> >info_log_path = /var/log/dovecot-info.log
> >log_path = /var/log/dovecot.log
> >mail_location = mbox:~/Mail:INBOX=/home/%u/Mail/INBOX_MAIL
> >mail_privileged_group = mail
> >mbox_write_locks = fcntl
> >namespace inbox {
> >  inbox = yes
> >  location =
> >  mailbox Drafts {
> >special_use = \Drafts
> >  } 
> >  mailbox Junk {
> >special_use = \Junk
> >  } 
> >  mailbox Sent {
> >special_use = \Sent
> >  } 
> >  mailbox "Sent Messages" {
> >special_use = \Sent
> >  } 
> >  mailbox Trash {
> >special_use = \Trash
> >  } 
> >  prefix =
> >} 
> >passdb {
> >  args = %s
> >  driver = pam
> >} 
> >passdb {
> >  driver = pam
> >} 
> >plugin {
> >  imapsieve_url = sieve://localhost:4190
> >  sieve = file:~/sieve;active=~/.dovecot.sieve
> >  sieve_after = /etc/dovecot/sieve-after
> >  sieve_dir = ~/sieve
> >  sieve_plugins = sieve_imapsieve sieve_extprograms
> >  sieve_user_log = ~/.dovecot.sieve.log
> >}
> >protocols = imap sieve sieve
> >service imap-login {
> >  inet_listener imap {
> >port = 143
> >  }
> >  inet_listener imaps {
> >port = 993
> >ssl = yes
> >  }
> >}
> >service managesieve-login {
> >  inet_listener sieve {
> >port = 4190   
> >  }
> >  process_min_avail = 0
> >  service_count = 1
> >  vsz_limit = 64 M
> >}
> >ssl = required
> >ssl_cert =  >ssl_key =  >userdb {
> >  driver = passwd 
> >}
> >userdb {
> >  driver = passwd 
> >}
> >protocol lmtp {   
> >  mail_plugins = " sieve"
> >}
> >protocol lda {
> >  mail_plugins = " sieve"
> >}
> >protocol imap {   
> >  mail_plugins = " imap_sieve"
> >}
> >
> >-
> >
> >Thanks for any guidance here.
> >
> >
> >--
> >@sadsfae // gpg: A31F27E0 // irc: sadsfae
> >come have a squat at https://hobo.house
> 
> -- 
> Christian Kivalo


signature.asc
Description: PGP signature

Re: dovecot-pigeonhole Missing sieve_imapsieve Plugin?

2018-06-07 Thread Christian Kivalo 



On June 7, 2018 6:47:54 PM GMT+02:00, Will Foster  wrote:
>Hi Folks,
>
>I am having a problem configuring imapsieve via dovecot-pidgeonhole on
>CentOS7.
>
>After following the docs here:
>
>https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve
>
>I get:
>
>dovecot[22026]: managesieve: Fatal: Plugin 'sieve_imapsieve' not found
>from directory /usr/lib64/dovecot/sieve
>dovecot[22026]: doveconf: Error: managesieve-login: dump-capability
>process returned 89
>
>There doesn't seem to be that plugin present or provided by
>dovecot-pigeonhole
>
># ls -lah /usr/lib64/dovecot/sieve/
>total 56K
>drwxr-xr-x. 2 root root   46 Jun  5 12:16 .
>drwxr-xr-x. 7 root root 4.0K Jun  5 12:16 ..
>-rwxr-xr-x. 1 root root  52K Aug  3  2017
>lib90_sieve_extprograms_plugin.so
>
>Am I doing something wrong?  This is provided via the CentOS EPEL
>package
>
>Here's my system details:
>
>* dovecot-pigeonhole-2.2.10-8.el7.x86_64
>* CentOS 7.5 on XFS
>* Rainloop Webmail / Mutt / IMAP access

As written on the imapsieve wiki page you linked above, the imapsieve plugin is 
available with pigeonhole 0.4.14 which requires dovecot 2.2.24. 

>Here's my dovecot -n
>
>
>
># 2.2.10: /etc/dovecot/dovecot.conf
>managesieve(root): Fatal: Plugin 'sieve_imapsieve' not found from
>directory /usr/lib64/dovecot/sieve
>doveconf: Error: managesieve-login: dump-capability process returned 89
># OS: Linux 3.10.0-862.2.3.el7.x86_64 x86_64 CentOS Linux release
>7.5.1804 (Core)
>first_valid_uid = 1000
>info_log_path = /var/log/dovecot-info.log
>log_path = /var/log/dovecot.log
>mail_location = mbox:~/Mail:INBOX=/home/%u/Mail/INBOX_MAIL
>mail_privileged_group = mail
>mbox_write_locks = fcntl
>namespace inbox {
>  inbox = yes
>  location =
>  mailbox Drafts {
>special_use = \Drafts
>  } 
>  mailbox Junk {
>special_use = \Junk
>  } 
>  mailbox Sent {
>special_use = \Sent
>  } 
>  mailbox "Sent Messages" {
>special_use = \Sent
>  } 
>  mailbox Trash {
>special_use = \Trash
>  } 
>  prefix =
>} 
>passdb {
>  args = %s
>  driver = pam
>} 
>passdb {
>  driver = pam
>} 
>plugin {
>  imapsieve_url = sieve://localhost:4190
>  sieve = file:~/sieve;active=~/.dovecot.sieve
>  sieve_after = /etc/dovecot/sieve-after
>  sieve_dir = ~/sieve
>  sieve_plugins = sieve_imapsieve sieve_extprograms
>  sieve_user_log = ~/.dovecot.sieve.log
>}
>protocols = imap sieve sieve
>service imap-login {
>  inet_listener imap {
>port = 143
>  }
>  inet_listener imaps {
>port = 993
>ssl = yes
>  }
>}
>service managesieve-login {
>  inet_listener sieve {
>port = 4190   
>  }
>  process_min_avail = 0
>  service_count = 1
>  vsz_limit = 64 M
>}
>ssl = required
>ssl_cert = ssl_key = userdb {
>  driver = passwd 
>}
>userdb {
>  driver = passwd 
>}
>protocol lmtp {   
>  mail_plugins = " sieve"
>}
>protocol lda {
>  mail_plugins = " sieve"
>}
>protocol imap {   
>  mail_plugins = " imap_sieve"
>}
>
>-
>
>Thanks for any guidance here.
>
>
>--
>@sadsfae // gpg: A31F27E0 // irc: sadsfae
>come have a squat at https://hobo.house

-- 
Christian Kivalo

dovecot-pigeonhole Missing sieve_imapsieve Plugin?

2018-06-07 Thread Will Foster 
Hi Folks,

I am having a problem configuring imapsieve via dovecot-pidgeonhole on CentOS7.

After following the docs here:

https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve

I get:

dovecot[22026]: managesieve: Fatal: Plugin 'sieve_imapsieve' not found from 
directory /usr/lib64/dovecot/sieve
dovecot[22026]: doveconf: Error: managesieve-login: dump-capability process 
returned 89

There doesn't seem to be that plugin present or provided by dovecot-pigeonhole

# ls -lah /usr/lib64/dovecot/sieve/
total 56K
drwxr-xr-x. 2 root root   46 Jun  5 12:16 .
drwxr-xr-x. 7 root root 4.0K Jun  5 12:16 ..
-rwxr-xr-x. 1 root root  52K Aug  3  2017 lib90_sieve_extprograms_plugin.so

Am I doing something wrong?  This is provided via the CentOS EPEL package

Here's my system details:

* dovecot-pigeonhole-2.2.10-8.el7.x86_64
* CentOS 7.5 on XFS
* Rainloop Webmail / Mutt / IMAP access

Here's my dovecot -n



# 2.2.10: /etc/dovecot/dovecot.conf
managesieve(root): Fatal: Plugin 'sieve_imapsieve' not found from directory 
/usr/lib64/dovecot/sieve
doveconf: Error: managesieve-login: dump-capability process returned 89
# OS: Linux 3.10.0-862.2.3.el7.x86_64 x86_64 CentOS Linux release 7.5.1804 
(Core)
first_valid_uid = 1000
info_log_path = /var/log/dovecot-info.log
log_path = /var/log/dovecot.log
mail_location = mbox:~/Mail:INBOX=/home/%u/Mail/INBOX_MAIL
mail_privileged_group = mail
mbox_write_locks = fcntl
namespace inbox {
  inbox = yes
  location =
  mailbox Drafts {
special_use = \Drafts
  } 
  mailbox Junk {
special_use = \Junk
  } 
  mailbox Sent {
special_use = \Sent
  } 
  mailbox "Sent Messages" {
special_use = \Sent
  } 
  mailbox Trash {
special_use = \Trash
  } 
  prefix =
} 
passdb {
  args = %s
  driver = pam
} 
passdb {
  driver = pam
} 
plugin {
  imapsieve_url = sieve://localhost:4190
  sieve = file:~/sieve;active=~/.dovecot.sieve
  sieve_after = /etc/dovecot/sieve-after
  sieve_dir = ~/sieve
  sieve_plugins = sieve_imapsieve sieve_extprograms
  sieve_user_log = ~/.dovecot.sieve.log
}
protocols = imap sieve sieve
service imap-login {
  inet_listener imap {
port = 143
  }
  inet_listener imaps {
port = 993
ssl = yes
  }
}
service managesieve-login {
  inet_listener sieve {
port = 4190   
  }
  process_min_avail = 0
  service_count = 1
  vsz_limit = 64 M
}
ssl = required
ssl_cert = https://hobo.house

FTS Solr errors using doveadm

2018-06-07 Thread Ricardo Branco 

Solr 7 returns JSON by default but fts_solr requires XML.

Would be good to have wt=xml added to the query to force it to xml all the time, this would prevent errors if solr has 
not had xml set as default for index.



Dovecot 2.2.36
Centos 6

*Doveadm Request:*

doveadm search -u carol...@covermg.com TEXT smith

doveadm(carol...@covermg.com): Error: fts_solr: Invalid XML input at 1:0: not 
well-formed (invalid token) (near: {
  "responseHeader":{
    "status":0,
    "QTime":0,
    "params":{
  "q":"{!lucene q.op=AND}(hdr:smith OR body:smith)",
  )
doveadm(carol...@covermg.com): Error: fts_solr: Invalid XML input at 1:0: not 
well-formed (invalid token) (near: {
  "responseHeader":{
    "status":0,
    "QTime":0,
    "params":{
  "q":"box:1065b22d6b02185bd40fd09efc50 AND user:ca)


*TCP Dump*

Content-Type: application/json;charset=utf-8
Content-Length: 329

{
  "responseHeader":{
    "status":0,
    "QTime":1,
    "params":{
  "q":"{!lucene q.op=AND}from:smith",
  "fl":"uid,score",
  "sort":"uid asc",
  "fq":"+box:b571472154d7035b4e25d09efc50 +user:carol...@covermg.com",
  "rows":"69235"}},
  "response":{"numFound":0,"start":0,"maxScore":0.0,"docs":[]
  }}

Re: 2.3.1 Replication is throwing scary errors

2018-06-07 Thread Reuben Farrelly 
Regarding my comment below - it looks like a false alarm on my part. 
The commit referenced below hasn't gone into master-2.3 yet which meant 
it wasn't included when I rebuilt earlier today.  That was was an 
incorrect assumption I made.


I have since manually patched it into master-2.3 and it looks to be OK 
so far - touch wood - with 4 hours testing so far.


Reuben


On 7/06/2018 3:21 pm, Reuben Farrelly wrote:

Still not quite right for me.

Jun  7 15:11:33 thunderstorm.reub.net dovecot: doveadm: Error: 
dsync(lightning.reub.net): I/O has stalled, no activity for 600 seconds 
(last sent=mail, last recv=mail (EOL))
Jun  7 15:11:33 thunderstorm.reub.net dovecot: doveadm: Error: Timeout 
during state=sync_mails (send=mails recv=recv_last_common)


I'm not sure if there is an underlying replication error or if the 
message is just cosmetic, though.


Reuben


On 7/06/2018 4:55 AM, Remko Lodder wrote:

Hi Timo,

Yes this seems to work fine so far. I’ll ask the people to add it to 
the current FreeBSD version..


Cheers
Remko

On 6 Jun 2018, at 19:34, Timo Sirainen > wrote:


Should be fixed by 
https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49336

Re: 2.3.1 Replication is throwing scary errors

2018-06-07 Thread Timo Sirainen 
On 7 Jun 2018, at 11.43, Michael Grimm  wrote:
> 
> Timo Sirainen:
> 
>> Should be fixed by
>> https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49336
> 
> please ignore my ignorance but shouldn't one add this commit regarding 
> src/doveadm/client-connection-tcp.c ...
> 
> https://github.com/dovecot/core/commit/2a3b7083ce4e62a8bd836f9983b223e98e9bc157
> 
> ... to a vanilla 2.3.1 source tree as well?

That's a code simplification / cleanup commit. It doesn't fix anything.

Re: 2.3.1 Replication is throwing scary errors

2018-06-07 Thread Larry Rosenman 

On 6/7/18, 3:43 AM, "dovecot on behalf of Michael Grimm" 
 wrote:

Timo Sirainen:

> Should be fixed by
> 
https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49336

please ignore my ignorance but shouldn't one add this commit regarding 
src/doveadm/client-connection-tcp.c ...


https://github.com/dovecot/core/commit/2a3b7083ce4e62a8bd836f9983b223e98e9bc157

... to a vanilla 2.3.1 source tree as well?

I do have to admit that I am absolutely clueless in understanding 
dovecot's source code, but I came accross this commit because it has 
been committed the very same day as the one solving those hanging 
processes.

I could test it by myself, but I am not sure if that commit would break 
my productive dovecot instances.

Regards,
Michael


I'm happy to add 
https://github.com/dovecot/core/commit/2a3b7083ce4e62a8bd836f9983b223e98e9bc157 
to 
The FreeBSD port if folks think it should help.

-- 
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: larry...@gmail.com
US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106

Re: 2.3.1 Replication is throwing scary errors

2018-06-07 Thread Michael Grimm 

Timo Sirainen:


Should be fixed by
https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49336


please ignore my ignorance but shouldn't one add this commit regarding 
src/doveadm/client-connection-tcp.c ...


https://github.com/dovecot/core/commit/2a3b7083ce4e62a8bd836f9983b223e98e9bc157

... to a vanilla 2.3.1 source tree as well?

I do have to admit that I am absolutely clueless in understanding 
dovecot's source code, but I came accross this commit because it has 
been committed the very same day as the one solving those hanging 
processes.


I could test it by myself, but I am not sure if that commit would break 
my productive dovecot instances.


Regards,
Michael

Re: 2.3.1 Replication is throwing scary errors

2018-06-07 Thread Michael Grimm 

Am 2018-06-07 08:48, schrieb Remko Lodder:

On Thu, Jun 07, 2018 at 08:04:49AM +0200, Michael Grimm wrote:


Conclusion: After 12 hours of running a patched FBSD port I do get 
those
error messages but replictaion seems to work now. But, I still have 
the

feeling that there might something else going wrong.


I agree with that. Are you using the new pkg that ler@ prepared ? That 
includes

the patch and is a 'native' package..


Yes, I am running this new port from ler@.
And: Thanks for his very fast modification!

Regards,
Michael

Re: Shared mailboxes, index files and 'per-user-seen' flags

2018-06-07 Thread Marco Giunta 
Hi Thomas,
it is a known problem:

  https://www.dovecot.org/pipermail/dovecot/2018-February/111057.html

Try the solution suggested in above mail; it works for me.

Thanks,
  Marco

On 2018-06-06 13:53, Thomas Robers wrote:
> Hello,
> 
> i have a dovecot server version 2.3.1 under CentOS 6.9 and we're
> using shared mailboxes with index files shared. With this configuration
> I can see a lot of error messages like:
> 
>    Jun  6 13:20:31 mail dovecot: Error: imap(us...@tutech.de)<4513>
>    : /export/home/imap/us...@tutech.de/shared
>    /us...@tutech.de/folder/dovecot.index.pvt view is inconsistent
> 
> In 10-mail.conf the location setting is:
> 
>    location = maildir:%%h/Maildir:INDEXPVT=%h/shared/%%u
> 
> I thought setting the index files to "not shared" might help to
> get rid of the errors, so I changed the setting to:
> 
>    location = maildir:%%h/Maildir:INDEX=%h/shared/%%u:INDEXPVT=%h
>    /shared/%%u
> 
> like it's mentioned in the Dovecot wiki. But that doesn't work as
> I expected, because the 'per-user-seen' flags do not work correctly
> anymore, i think. If UserA, who has UserB as shared mailbox,
> changes the seen flags of UserBs INBOX, UserBs seen flags are also
> changed. The other way, if UserB changes seen flags in his INBOX
> they are not changed in the shared view of UserA. Is this the
> supposed way to work  or do i have an error in the configuration?
> 
> Any help is appreciated.
> 
> Thanks, Thomas.
> 
> Here's my currently used configuration:
> 
> # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf
> # Pigeonhole version 0.5.devel (61b47828)
> # OS: Linux 2.6.32-696.23.1.el6.x86_64 x86_64 CentOS release 6.9 (Final)
> ext4
> # Hostname: mail.tutech.de
> auth_master_user_separator = *
> auth_mechanisms = plain login
> auth_verbose = yes
> disable_plaintext_auth = no
> doveadm_password =  # hidden, use -P to show it
> doveadm_port = 12345
> imap_max_line_length = 2 M
> mail_debug = yes
> mail_location = maildir:/export/home/imap/%Lu/Maildir
> mail_plugins = acl zlib mail_log notify
> mail_prefetch_count = 1
> mailbox_idle_check_interval = 10 secs
> managesieve_notify_capability = mailto
> managesieve_sieve_capability = fileinto reject envelope
> encoded-character vacation subaddress comparator-i;ascii-numeric
> relational regex imap4flags copy include variables body enotify
> environment mailbox date index ihave duplicate mime foreverypart
> extracttext
> namespace {
>   hidden = no
>   ignore_on_failure = no
>   inbox = no
>   list = children
>   location = maildir:%%h/Maildir:INDEXPVT=%h/shared/%%u
>   prefix = shared/%%u/
>   separator = /
>   subscriptions = yes
>   type = shared
> }
> namespace inbox {
>   hidden = no
>   inbox = yes
>   list = yes
>   location =
>   mailbox Drafts {
>     special_use = \Drafts
>   }
>   mailbox Junk {
>     special_use = \Junk
>   }
>   mailbox Sent {
>     special_use = \Sent
>   }
>   mailbox "Sent Messages" {
>     special_use = \Sent
>   }
>   mailbox Trash {
>     special_use = \Trash
>   }
>   prefix = INBOX/
>   separator = /
>   type = private
> }
> 
> passdb {
>   args = /etc/dovecot/master-users
>   driver = passwd-file
>   master = yes
> }
> passdb {
>   args = /etc/dovecot/dovecot-ldap.conf.ext
>   driver = ldap
> }
> plugin {
>   acl = vfile:/etc/dovecot/global-acls:cache_secs=300
>   acl_shared_dict = file:/export/home/shared-db/shared-mailboxes
>   mail_log_events = append delete undelete expunge copy mailbox_delete
> mailbox_rename flag_change
>   mail_log_fields = uid box msgid size from flags
>   mail_replica = tcp:mail2.tutech.de
>   sieve = ~/.dovecot.sieve
>   sieve_dir = ~/sieve
>   sieve_global = /var/lib/dovecot/sieve/global/
>   sieve_user_log = ~/.dovecot.sieve.log
>   zlib_save = gz
>   zlib_save_level = 6
> }
> protocols = imap pop3 lmtp sieve sieve
> service aggregator {
>   fifo_listener replication-notify-fifo {
>     mode = 0666
>     user = vmail
>   }
>   unix_listener replication-notify {
>     mode = 0666
>     user = vmail
>   }
> }
> service auth {
>   unix_listener /var/spool/postfix/private/auth {
>     mode = 0666
>   }
>   unix_listener auth-userdb {
>     group = vmail
>     mode = 0660
>     user = vmail
>   }
> }
> service config {
>   unix_listener config {
>     user = vmail
>   }
> }
> service doveadm {
>   inet_listener {
>     port = 12345
>   }
>   user = vmail
> }
> service imap-login {
>   inet_listener imaps {
>     port = 993
>     ssl = yes
>   }
>   process_limit = 500
>   process_min_avail = 20
> }
> service imap {
>   executable = imap
> }
> service lmtp {
>   inet_listener lmtp {
>     address = 127.0.0.1
>     port = 24
>   }
> }
> service managesieve-login {
>   inet_listener sieve {
>     port = 4190
>   }
>   inet_listener sieve_deprecated {
>     port = 2000
>   }
> }
> service pop3-login {
>   inet_listener pop3s {
>     port = 995
>     ssl = yes
>   }
> }
> service pop3 {
>   executable = pop3
> }
> service replicator {
>   unix_listener replicator-doveadm {
>     mode = 0666
>  

Re: 2.3.1 Replication is throwing scary errors

2018-06-07 Thread Michael Grimm 

Am 2018-06-07 07:34, schrieb Remko Lodder:
On 7 Jun 2018, at 07:21, Reuben Farrelly  
wrote:



Still not quite right for me.

Jun  7 15:11:33 thunderstorm.reub.net dovecot: doveadm: Error: 
dsync(lightning.reub.net): I/O has stalled, no activity for 600 
seconds (last sent=mail, last recv=mail (EOL))
Jun  7 15:11:33 thunderstorm.reub.net dovecot: doveadm: Error: Timeout 
during state=sync_mails (send=mails recv=recv_last_common)


I'm not sure if there is an underlying replication error or if the 
message is just cosmetic, though.


Admittedly I have had a few occurences of this behaviour as well last 
night. It happens more sporadic now and seems to be a conflict with my 
user settings. (My users
get added twice to the system, user-domain.tld and u...@domain.tld, 
both are being replicated, the noreplicate flag is not yet honored in 
the version I am using so I cannot

bypass that yet).

I do see messages that came on the other machine on the machine that I 
am using to read these emails. So replication seems to work in that 
regard (where it obviously

did not do that well before).


First of all: Major improvement by this patch applied to 2.3.1, there 
are no more hanging processes.


But: I do find quite a number of error messages like:

	Jun  7 06:34:20 mail dovecot: doveadm: Error: Failed to lock mailbox 
NAME for dsyncing: \
		file_create_locked(/.../USER/mailboxes/NAME/dbox-Mails/.dovecot-box-sync.lock) 
\
		failed: 
fcntl(/.../USER/mailboxes/NAME/dbox-Mails/.dovecot-box-sync.lock, 
write-lock, F_SETLKW) \
		locking failed: Timed out after 30 seconds (WRITE lock held by pid 
79452)


These messages are only found at that server which is normally receiving 
synced messages (because almost all mail is received via the other 
master due to MX priorities).


Conclusion: After 12 hours of running a patched FBSD port I do get those 
error messages but replictaion seems to work now. But, I still have the 
feeling that there might something else going wrong.


@Timo: Wouldn't it be worth to add replicator/aggreator error messages 
to head like Aki sent to Remko? That might add some light into 
replication issues today and in the future.


Regards,
Michael