similar to: Does a script exist to fix broken maildir timestamps?

Hello, I am trying to migrate off a MS Exchange 5.0 server. I am using mailsync (http://www.linux-france.org/prj/imapsync/) to copy the files to a Dovecot server, version 0.99.10.7. For particular messages I get the following error: Couldn't append msg #114081 (Subject:[RE: balh blah]) to folder INBOX: Error trying to append: 826 NO Unexpected EOF I think this is Dovecot, complaining

Hi All, I have migrated a client from what I think was UW-IMAPD to Dovecot, using the tool imapsync (http://www.linux-france.org/prj/imapsync/). The client is using Outlook and Outlook Express as their mail client and now all of their emails have the date 20/01/2006 in the folder view. When the email is viewed directly, the date is the correct date for the email. I was wondering if any one has

Well, my Dovecot server (v2.0.8) is up and running, and now it's time to migrate mailboxes from the old mail server [Lotus Domino Release 5.0.8] running on Windows NT 4.0 [ancient -- been the mail server since Aug-2000]. I saw "dsync(1)" and thought my troubles were over. Only I can't figure out how to make it work with the NT/Domino server as a source for mailboxes. I guess

hi, we migrate from exchange to dovecot. we do it with imapsync. first we try to do it with --syncinternaldates, but this fails on many messages with invalid date, so we drop this option. unfortunately after this those users who use outlook see the received date as the date we do the migration in stead of the real received date. other clients eg webmail, thunderbird etc sees the right date. so my

I attempted an upgrade from 1.1.7 to 1.1.15 and encountered an apparent regression in handling gzipped maildir files. I have tried to narrow down the conditions under which it happens and reproduce it with as simple a case as possible. The actual mail application that exposed this problem is Squirrelmail. Starting off with the index files removed from the "Folder" maildir directory: *

> On 7. Jun 2020, at 18.20, John Stoffel <john at stoffel.org> wrote: > >>>>>> "Gingko" == Gingko <ldiff001 at gingko.ovh> writes: > > Gingko> I also have issues using Dovecot Backup. > > Gingko> I am trying to Backup (or possibly Sync - one way) a single > Gingko> user IMAP account from a remote server, unknown type, to my

I'm copying all my archives from one imap server on one machine to the imap-ssl dovecot server on another machine. After a bit, there's an error that's tossed up on my mozilla client that says the imap server couldn't complete the operation with the message append aborted. It keeps popping up after anything from 50 to 300 emails. Last night I was able to move ~12000 emails

Hello, I am trying to setup a migration scenario from an proprietary solution to dovecot IMAP/POP3. Whereas am only at the strating point, things appear quite complicated because of the following reasons: - The proprietary solution uses special/own/proprietary mailbox format (wich is more like maildir but is not maildir) - I don't have direct access to the filesystem where the mails are

I have some old mail on courier-imap that I'd like to bring over some of the readme says I need to make Dovecot's inbox as "INBOX" not "Inbox" for courier-imap compatibility.. that seems to be already default, no ? also, my INBOX is mainly like 'sent/year/month' and some other 'work/this' subfolders is there a tool I need to use, or should just copy

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

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, I'm using Imapsync to sync messages from an Exchange 2003 server to a Dovecot 1.1.11 server. The problem is that users' mailboxes are huge, several gigabytes with tens of thousands of messages. First Imapsync connects to Exchange and then to Dovecot, and then starts to get Inbox info from Exchange. By the time it gets this info, the connection to Dovecot has timed out. I realize the

Dear dovecot list, I'm using Maildir as mailbox format. Is there any recommendation for the namespace hierarchy separator? Currently I didn't set any. So it is the default of dot '.' I'm switiching from a rather unknown IMAP Server called DBMail (http://www.dbmail.org/) Planning to synchronize the mailboxes via imapsync (https://github.com/imapsync/imapsync) Is there

Could you help me trouble shoot this? I am a bit of a rookie and probably screwed something up. I am trying to "make" imapsync, but there is a complaint regarding some Perl problem that I cannot figure out. [root at testmail imapsync-1.182]# make Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/5.8.5/i386-linux-thread-multi/Scalar/Util.pm line 30. is

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,

The dot '.' will work, but I suggest to follow documentation here: https://wiki1.dovecot.org/Namespaces, And it says: A commonly used separator is '/'. It probably causes the least amount of trouble with different IMAP clients And I already had problems using '.' as a namespace separator. On 2020-04-24 15:56, Sami Ketola wrote: > >> On 24. Apr 2020, at

hello list, I am attempting to sync two imap servers using the imapsync perl script. It seems handy and easy. Here's what happens when I try to do this: # # Postfix master process configuration file. For details on the format # of the file, see the master(5) manual page (command: "man 5 master"). # -o smtpd_sasl_auth_enable=yes # -o

Am 04.09.2018 um 18:27 schrieb Sami Ketola: > > >> On 4 Sep 2018, at 18.38, Robert Schetterer <rs at sys4.de> wrote: >> >> Sorry i migrated terrabytes of mail with imapsync and never had a >> problem, it works as designed, also with maildir rsync did a good job, >> what never worked as it should was dsync ,cause of bugs ,that may >> changed now

Hi List, I am trying to migrate my dovecot 0.9 (mbox-Storage) to 1.0rc2 with maildir-storage using imapsync. I cannot manage to copy the emails from one server to the other, however the dry-run from imapsync works nicely. Is it possible to make dovecot more verbose to see what is happening (or not happening)? Thank you very much. Best Stephan