similar to: preserving flags for shared mailbox when migrating from cyrus to dovecot

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,

Hello, Using cyrus2dovecot (https://github.com/a-schild/cyrus2dovecot) I have migrated some test mailboxes from Cyrus (2.4.17) to Dovecot (2.2.9). The problem I'm having is that the seen status is in cyrus.index files, which cyrus2dovecot doesn't understand. Does anyone use cyrus2dovecot for migrations? If so, how do you deal with seen status when it is stored in the .index files?

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, 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

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

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,

Dear all, We're slowly progressing towards migration, and now run into dscyn dumping core when trying to sync mailboxes from the old imap server. Needless to say that not one byte get's transferred. On the old.server all I see is a correct login. This is what we get for one example user: server:~# doveadm -v -D backup -R -u USER imapc: doveadm(root): Debug: Loading modules from

2015-01-23 4:20 GMT-03:00 Marc St?rmer <mail at marc-stuermer.de>: > > Zitat von Norberto Bensa <nbensa+dovecot at gmail.com>: > > Does anyone use cyrus2dovecot for migrations? If so, how do you deal with >> seen status when it is stored in the .index files? >> > > Why don't you use the migration tool that comes with Dovecot bundled > instead,

Dear all, We are getting closer to the migration of our mailsystem. Now I have a special question. We are successfully using passdb { driver = pam } and that is good. Now, how would I tell dovecot to proxy certain users (the ones not yet migrated) to the old server? My attempts to configure an additional userdb failed since this seems to override the passdb setting. Grateful for any

you wouldnt know, your not a developer, shit processor maybe, but not a developer On 4/3/15, Reindl Harald <h.reindl at thelounge.net> wrote: > > > 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

I have been attempting to use the cyrus2dovecot script, to no avail. I have many years of content that I want to convert from Cyrus to Dovecot; with the above not working, what are other options out there? Another idea I had is simply set up another IMAP server (using Dovecot) and drag-and-drop and just wait, which I may end up doing. In the above, I copied over my entire /var/imap and

Hi all, I start this on in a new thread. I setup the deny-user setting to temporarily prevent users from logging in and (that would be great) also stop mail delivery for said user. All this is because of our upcoming migration. Now it seems that lmtp is ignoring this setting. This is from the logfile: Aug 21 13:01:00 klee dovecot: lmtp(pid): Connect from IP Aug 21 13:01:00 klee dovecot:

Thank you for the reply. I did find imapsync whilst perusing Google. I will give it a shot, it sounds more realistic/reliable. I have a hoard of emails going back to 1999, so I want as few errors as possible :) On 11/7/15 3:31 PM, Philon wrote: > Hi there, > > I was in the same position, but for mutliple accounts. Still you might want to look at imapsync

Hi all, We use prefix=INBOX. in order to keep things as they were on the old server. Now I started playing with quota and have trouble getting the additional quota for Trash and/or Junk working. My expectation was that once a user is over quota and moves email to trash sh/e should be able to receive new email again. That's what I cannot get to work with our setup. Attached you find the

Hello, Because it did not work ? In a similar situation, we where forced to use isync/mbsync in imap to imap mode because dsync did not work. It was reported here more than a year ago (May 2014). Time to time, I see the same report from other trying to use dsync to do a migration to dovecot. Dsync is a very appealing and elegant solution to this usage, but it does not always work in real

Hi, No, I tried fetching over imapc too exactly as you suggested. In my case it was not from cyrus, but from CriticalPath. isync was finally able to do the job, preserving flags and doing UIDs mapping. The most boring part was generating proper config file for thousands of accounts. A working imapc/dsync would have been better. Emmanuel. Le 26/11/2015 15:24, Sami Ketola a ?crit : > Hi,

Hello, unfortunatly, TLS doesn't seem to work on LMTP, anyway, not by simply put ssl=yet to the lmtp inet_listener. I've tried and when I *openssl s_client -connect* to the lmtp listener I've got the following response : CONNECTED(00000003) 34379118248:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 30 Jul 2014, Jogi Hofm?ller wrote: >> Or better - disable LMTP service in Dovecot. Incoming mail will stay on >> your MTA and when you're done, you just tell it to deliver everything >> that piled up in the queue in the meantime > > Better but still not perfect ;) We have users that work late and I am > sure

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

Hi, we are migrating from Cyrus 2.3.7 to Dovecot 2.2.13. We have ~7000 maildirs with ~500GB. Our goal is to do the migration without users have notice and with the shortest service downtime. The users use IMAP (with shared folders and ACL), POP3 and sieve filters. As a first choice, we tried the Dovecot's dsync tool. First tests were great, but we are not able to change the Cyrus auth