similar to: Problem with converting mdbox to MailDir

Yeah, I think dovecot was a custom compiled build Version is 2.2.18 Config: # 2.2.18: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 # OS: Linux 2.6.32-754.14.2.el6.x86_64 x86_64 CentOS release 6.10 (Final) xfs auth_master_user_separator = * auth_mechanisms = plain login dict { acl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no lda_mailbox_autosubscribe =

And /bin/doveconf namespace namespace { disabled = no hidden = no ignore_on_failure = no inbox = no list = children location = mdbox:/var/mailboxes/%%2Mu/%%2.2Mu/%%u order = 0 prefix = shared/%%u/ separator = / subscriptions = yes type = shared } namespace inbox { disabled = no hidden = no ignore_on_failure = no inbox = yes list = yes location = mailbox Drafts

I?m trying to migrate mdbox to maildir based on https://wiki.dovecot.org/Migration/MailFormat * Modified dovecot.conf and set mail_location=maildir:/tmp/destination/mailboxes/ * Then I had run /mnt/testmail/bin/dsync -Dv -u user at domain.com<mailto:user at domain.com> mirror mdbox:/source/mailboxes/user at domain.com<mailto:/source/mailboxes/user at domain.com> but that

we have some replication issues. From time to time a doveadm-server process takes 100% cpu in the state recv_mailbox_tree_deletes on the replica. The process runs forever until it is manually killed. Strace on this process doesn't show anything. Sometimes we have several doveadm-server processes in this state, all for the same account, all with 100% CPU Load. The logfile on the master says:

I saw that before but there is only maildir -> mdbox but not mdbox -> maildir Did I have missed anything there? ?On 6/18/19, 9:59 PM, "dovecot on behalf of @lbutlr via dovecot" <dovecot-bounces at dovecot.org on behalf of dovecot at dovecot.org> wrote: > On 18 Jun 2019, at 15:18, Benny Pedersen via dovecot <dovecot at dovecot.org> wrote: >

Hi Tim, > Do you have any new insights on the problem with reappearing mail using dovecot replication + pop3? > > It's driving me mad. I'm running dovecot 2.2.34 (874deae) on OpenBSD and it looks like I have the same problem as you have. unfortunately there has been no response, I'm stuck with 2.2.33.2 for the time being. I can only suspect it has something to do with

I saw that before but there is only maildir -> mdbox but not mdbox -> maildir Did I have missed anything there? From: dovecot <dovecot-bounces at dovecot.org> on behalf of Sami Ketola via dovecot <dovecot at dovecot.org> Reply-To: Sami Ketola <sami.ketola at dovecot.fi> Date: Tuesday, June 18, 2019 at 9:58 PM To: Dovecot Mailing List <dovecot at dovecot.org> Cc:

Hi, I tried to migrate my dovecot 2.2 to a new server with a other storage configuration and dovecot 2.3. New (and old) Server uses mysql for user information I use the following storage settings mail_home = /storage1/vmail/%{userdb:path} mail_location =

Hi Aki, thanks for looking into this :) Am 14.08.18 um 15:15 schrieb Aki Tuomi: > can you turn on mail_debug=yes and run doveadm -Dv mailbox delete and > provide output and logs from both servers? root at ka-nfs-mail:~# doveadm -Dv mailbox delete? -u h 'INBOX/Fachbereiche ' Debug: Loading modules from directory: /usr/lib/dovecot Debug: Module loaded:

Hi All, I currently have a small Dovecot server (Server A) and I've installed a second dovecot mailbox server (server B) and am trying to sync mailboxes from Server A to Server B. Both servers sit behind two dovecot directors on separate hosts and have identical config files (doveconf -n output below). Mailboxes on Server A are on an NFS mount. Server A has been working fine with no

Hello, I use dovecot replication and the sieve scripts are not replicated. Mail replication is working fine. Log when sieve script (with Rainloop webmail) is created: Oct 12 12:57:57 srv1 dovecot: managesieve-login: Login: user=<hativ at example.com>, method=PLAIN, rip=91.67.174.186, lip=195.201.251.57, mpid=5360, TLS, session=<OXvK9QV4fOBbQ666> Oct 12 12:57:57 srv1 dovecot:

Hi, I am running two dovecot servers active/active. Everything runs pretty great, except for the replication of subscriptions in a shared namespace. When I unsubscribe from a folder the subscription instantly re-appears. The timestamp on the subscriptions file is updated, but the entry is still in there. If the other node is shut down, everything works as expected, which leads me to believe that

Hi Aki, Am 14.08.18 um 16:42 schrieb Aki Tuomi: > Hi, > > the thing I'm actually looking for is that whether the sync causes the folder to be restored, so it might be a better idea for you to try and spot this from the logs. I assume that as an SP that you are using mail_log plugin, so that might be useful to spot if this happens. You can also try looking at the UIDVALIDITY value of

On 19.6.2019 6.39, @lbutlr via dovecot wrote: > On 18 Jun 2019, at 20:46, Adam Raszkiewicz <araszkiewicz at medallies.com> wrote: >> maildir -> mdbox it is maildir to mdbox conversion when I'm looking something opposite: mdbox -> maildir > Please go back and read all the words in my previous reply. > doveadm supports convering mdbox to maildir as well, it works

Am 14.08.18 um 18:51 schrieb Aki Tuomi: > Try > > doveadm mailbox list -u user INBOX/* Hmm, posted that before, it lists all these undeletable mailboxes: root at ka-nfs-mail:~# doveadm mailbox list? -u <username> 'INBOX/*' | grep hbereich INBOX/[Fachbereiche INBOX/Fachbereiche INBOX/hbereiche INBOX/hbereiche/LAGen] INBOX/hbereiche/LAG INBOX/[Fachbereiche

Dovecot 2.2.31 with mailboxes in mdbox format. Since a couple of days some mailboxes have the problem, that sieve rules moving mails to folders stop working and .sieve.log in mailbox shows: sieve: info: started log at Sep 07 13:57:17. error: msgid=<20170907155704.EGroupware.S4yThVJRr12WSiJLpKbK0Bz at somedomain.egroupware.de>: failed to store into mailbox 'INBOX/Munser': Mailbox

I have noticed a difference in the behavior of ACLs. When used in a MUA the following global ACL works fine and has the desired effect - new mailboxes can be created by a user being part of the 'PublicMailboxAdmins' group: [ global-acl: ] INBOX owner lrwstiekxap Public/* group=PublicMailboxAdmins lrwsipk Public/* anyone lr Public/* authenticated lrws Creating the same mailbox via

Hi all, I'm receiving a reproducible dsync backup panic for some of my users. The error message is as follows: dsync-remote(user@<removed>): Panic: file dsync-brain-mailbox-tree-sync.c: line 111 (dsync_brain_mailbox_tree_sync_change): assertion failed: (brain->no_backup_overwrite) dsync-remote(user@<removed>): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x69b70)

> > Did you check your logs? > that?s just it. There?s nothing in syslog (which is logging at mail.debug). Not just nothing useful, absolutely _nothing_ logged when I run that. All I see is this (printed, I presume to STDERR): doveadm backup -D -A -R -f ssh -i id_rsa.dsync imap01.coyhile.com /opt/local/bin/doveadm dsync-server -A Error: User listing returned failure doveadm: Error:

* Timo Sirainen <tss at iki.fi> 2015.09.08 12:20: > How does the PublicMailboxAdmins group get set? Looks to me like the problem is that it's not getting set to doveadm. Here's an easy way to check if that's the problem or something else: http://hg.dovecot.org/dovecot-2.2/rev/500e8dd7a389 > > If that doesn't help: Show your full doveconf -n, set auth_debug=yes and