similar to: dsync core dump

Hi all, Another question regarding migration. While migrating a mailbox with dsync is it safe to deliver mail via LMTP to the new (target) mailbox or is it wiser to deactivate LMTP delivery to this mailbox until it's fully migrated? And what methods could I use to stop delivery to a mailbox during migration? Our user data is stored on an LDAP server. Cheers, -- j.hofm?ller

Am 2015-04-02 um 18:24 schrieb Reindl Harald: > Am 02.04.2015 um 18:19 schrieb Jogi Hofm?ller: >> Am 2015-04-02 um 17:49 schrieb Reindl Harald: >>> Am 02.04.2015 um 14:30 schrieb Edwardo Garcia: >>>> On 4/1/15, Reindl Harald <h.reindl at thelounge.net> wrote: >>>>> Am 01.04.2015 um 14:33 schrieb Bernd Petrovitsch: >>>>>> On Mit,

Folks, Several questions packed into one email ;) Can dovecot use TLS/SSL on LTMP inet socket? Can I configure dovecot to only let an authenticated user deliver mail via LMTP? Can I tell dovecot to use a user/password for proxying LMTP connections? All this is related to my quest to move from cyrus to dovecot transparently to our users. And if any of the above questions can be answered

Hello, I am deploying a new dovecot server to replace and old one, both of the with dovecot 2.1.9. Now I want to synchronize imap mailbox from the old to the new one. So, in my new server I run (whith a $ sudo dsync -v -D -o imapc_host="<oldserver>" -o imapc_password="<master password>" -o imapc_features=rfc822.size backup -R -f -u myuser at um.es imapc:

Hi folks, Firstly, the first: dovecot --version 2.2.10 dovecot -n # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-514.16.1.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core) auth_debug = yes auth_krb5_keytab = /var/lib/dovecot/krb5.keytab auth_master_user_separator = * auth_mechanisms = plain login gssapi auth_verbose = yes debug_log_path = /dev/null default_process_limit = 400

Hi All! I'm also hitted by this problem. I'm trying to migrate emails from very old dbmail to dovecot (maildir). I read old threads with similar problem but I found only such solutions: - upgrade to 2.2.13 - workarround : use imapsync - no solution I'd like to not use imapsync, have you got an idea what should I do to do migration successfully? dsync throws: doveadm(root): Debug:

Am 2015-04-02 um 17:49 schrieb Reindl Harald: > Am 02.04.2015 um 14:30 schrieb Edwardo Garcia: >> On 4/1/15, Reindl Harald <h.reindl at thelounge.net> wrote: >>> Am 01.04.2015 um 14:33 schrieb Bernd Petrovitsch: >>>> On Mit, 2015-04-01 at 13:07 +0200, Reindl Harald wrote: >>>>> Am 01.04.2015 um 13:04 schrieb Bernd Petrovitsch: >>>>>

Hi all, I'm trying to migrate messages from icewarp (merak) mailserver to dovecot via dsync, IMAP migration is looking fine, but I'm unable to migrate pop3 uidls from originating server, probably is something wrong with configuration, but I don't know what. The only documentation i found is on the wiki: http://wiki2.dovecot.org/Migration/Dsync where is bad writen mail_plugins =

I've run into a problem with `doveadm backup` (2.2 rc2 and 20130226) I did not notice in 2.1.15 doveadm backup [-Dv] -R -u cyrtest1 at iai.uni-bonn.de -m INBOX imapc: => crashes (signal 6 with acl plugin configured, sig 11 without acl) If this is considered a bug (not just because of the crash but in the meaning of "my configuration should work") it would be great if it could be

Hi all i'm migrating a cyrus imapd server to dovecot with dsync everyting seems working but sieve rules are not copied to dovecot server I searched for documentation but without any luck I use the configuration below with doveadm -v -o mail_fsync=never backup -R -u emailaddr imapc: Is sieve supported with dsync? How I can specify sieve server address and port? # 2.2.13.21 (606efd4a4f35):

Hello, I'm aware of these two threads http://www.dovecot.org/pipermail/dovecot/2012-March/thread.html#134311 http://dovecot.org/pipermail/dovecot/2012-June/thread.html#136488 but unfortunately I wasn't successful with my dsync mailbox migration attempt despite the information I could find there. I'm using iRedMail setup for the dovecot server. I made sure that the dovecot mailbox

Hi dovecot people, We are in the process of preparing the migration from a cyrus 2.1 installation to dovecot. Dovecot will be installed on new hardware, so we have separated servers that can/will exist in parallel for a while. Our goal is to do the migration without interrupting the service for our users too much. Currently we tend to using dsync. So I am asking for best practice suggestions,

Hi all, We are facing quite large mailboxes (>10GB) in our migration from cyrus to dovecot. I did a test on one mailbox and repeated the sync a couple of times with the expected result that the second, third, etc. sync took only seconds compared to minutes for the first sync. We use this command to sync a mailbox: doveadm backup -R -u USER imapc: Are there any problems to be expected

Hi Dovecot list! I try to sync from a remote imap server to my local dovecot server via the dsync tool with imapc. Here is my command: # /usr/local/dovecot/bin/dsync -c /usr/local/dovecot/etc/dovecot/dovecot.conf -D -o imapc_user= test at example.com -o imapc_password=pwd backup -R -u test at example.com imapc: Here the error message: dsync(test at example.com): Panic: file quota-maildir.c:

Hi all, We face a problem migrating shared mailboxes from an old cyrus server to dovecot. Whereas migrating regular users works like a charm, the shared mailboxes cannot be migrated. dsync/doveadm states: "Error: Failed to access mailbox INBOX: Mailbox does not exist". This is somehow true since the shared mailboxes live not under user.mailbox but rather under shared.mailbox (cyrus

with dovecot --version 2.3.10.1 (a3d0e1171) exec of doveadm -v -o mail_fsync=never backup -R -f -u testuser at example.com imapc: currently fails, here, with Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted checking lists, this has been seen before @ https://dovecot.org/pipermail/dovecot/2016-January/102988.html On 24 Jan 2016, at 18:47, Timo Sirainen

Hi folks, Not sure how much extra information I'll be able to provide on this, but I'm experiencing a consistent, reproducible dsync backup error with a single, specific account I'm trying to migrate from UW-IMAP / Panda (mix mailbox) to a Dovecot 2.2.32 cluster. Didn't spot any core files laying around. Doveadm backup output, dovecot --version and dovecot -n below:

I'm working on migrating IMAP users from Mirapoint Message Servers to Dovecot servers. The Mirapoint IMAP server uses INBOX as a namespace for private mailboxes. I created the same namespace in Dovecot, but when I migrate mailboxes dsync seems to ignore/miss the namespace on Mirapoint and I end up with all mailboxes under a INBOX.INBOX hierarchy. Mirapoint Source Server

Hi! You need to add a ssl_client_ca_* setting even if you don't want the imapc to verify the remote cert. I'll have to look into why this has been made a requirement in the code, since it has to do what with how we do OpenSSL initialization. Aki On 21.07.2018 12:59, Andrzej Polaty?ski wrote: > Hi, > > I'm trying to migrate from an old courier IMAP server to Dovecot 2.3.1

> On 28 Sep 2019, at 11:48, Philip Iezzi via dovecot <dovecot at dovecot.org> wrote: > > >> On 28 Sep 2019, at 11:28, Sami Ketola via dovecot <dovecot at dovecot.org> wrote: >> >> >> >>> On 28 Sep 2019, at 12.21, Philip Iezzi via dovecot <dovecot at dovecot.org> wrote: >>> >>> Hi there >>> >>> We