Scalix Forums

Hello everyone,

I have attempted to transfer one e-mail account from the old imap server to the new imap server. While transfering imapsync, and iamp copy report errors.

Imaysync reports the following errors:



The above is a small sample. imap sync ends up not transfering about 50% of the messages.

Imapcopy reported the following errors also:



I have attempted to use outllook to copy the messages, and that process locked up outlook.

On my last test I started monitoring the maillog log file, and nothing showed up there.

All the messages can be seen by the mail client, weather it be outlook or thunderbird or netscape 7.2 It seems I can't transfer them. Why?

Has anybody ran across this problem before?

Thank you all for your help

Sincerely,

Sideband Samurai

we migrated an exchange 5.5 server for about 20 users over to scalix. This had about 10 years of mail :-) so we had a lot of issues getting it to work reliably. imapsync seemed to be about the best of the imap mapping tools I tried although far from perfect.

i found the thing that seemed to work best was doing a justfolders first so that all the structure was created so I made a little script to do this, then I did the messages.

imapsync --host1 192.168.20.1 --user1 MyDomain/blah --password1 SECrEt --host2 192.168.20.4 --user2 blah --password2 StillASecrtet --noauthmd5 --justfolders --nofoldersize

imapsync --host1 192.168.20.1 --user1 MyDomain/blah --password1 SECrEt --host2 192.168.20.4 --user2 jhamill --password2 StillASecrtet --noauthmd5

I still found some folders that won't migrate correctly, so for those ones I exported to a pst file and imported back into outlook with the scalix connector.

Hello everyone,

I have attempted the suggestion. and this was a improvement. One of the other problems I was having is imapsync would create the folders and then not transfer the message, creating the folders first, solves that problem

Thanks for the suggestion.

but...

I am still getting transfer errors from the old imap server.

here is a copy of the --debugimap option



As you can see above, 342 messages are not being transferd, as all of the errors are exactly the same. I have tried the --nofastio option with no success

Does anybody know what the error "BAD syntax error" means It seems to transfer the other messages just fine. This issue also appears to be unrelated to attachments.

The old server is a University of Washington IMAP4 server which is installed by default on Redhat 8.

Here is the justconnect information:



Thanks everyone for all your suggestions,

Sincerely,

Sideband Samurai

I gave up finally for those "recalcitrant messages" as I was having the same issues for some users, so I exported the affected folders to a PST file using outlooks export with the exchange profile. Changed profile to scalix then imported the messges.

SidebandSamurai wrote:Hello everyone,

I have attempted the suggestion. and this was a improvement. One of the other problems I was having is imapsync would create the folders and then not transfer the message, creating the folders first, solves that problem


[/code]

Thanks everyone for all your suggestions,

Sincerely,

Sideband Samurai

My fear in that process was Outlook can be so unpredicitable when working with large batches of messages that it would just hang in the middle.

The good news was I Migrated the whole account (my test acount) with out issue. I did not have to use the Outlook connecter either. I just used Outlooks abiity to connect to the imap server directly.

Moving the messages to the PST first acutally prevents outlook from locking up because its doing to much at once.

Thanks for the suggestion.

Sincerely

Sideband Samurai

Hello eveyone,

I have come to the end of my migration and wanted to report back what i have discovered so that if someone has issues similar to mine this article will be helpful.

I have discoverd that the errors stated in previous posts were not a result of a faulty migration program. Imapsync works excellent.

My problem was with the imap files them selves. eveidently they had gotten corrupted but not enough to cause the e-mail client to report any errors.

In some instances, I used a utiltiy called mbxcvt from the RPM package called
imap-utils-2002d-6mdk.i586.rpm After installing this package, I re-converted the imap mailboxes to mbx format. The problem then disappeared.

Now I want to caution anybody who reads this. My imap server (university of Washington imap) was configured to handle mbx formated files. these files were placed in each users home directory under the directory /home/<userid>/Mail you have to configure a special .imaprc file in order to use these unsupported features. The unsupported features I was using was the ability to place the users e-mail files in a directory called "Mail". UWIMAP will read by default mbx formatted files as well as its standard files.

Some times this process would not work. I had at first attemted to use outlook to migrate the mail (using the imap accounts). The problem with this method was outlook appends winmail.dat files as attachments to all messages. This winmail.dat file contains message formatting information only understood by outlook. So now if the end user saw a winmail.dat file he could not see his attachments.

To solve this isssue, I used thunderbird and migrated to a local e-mail file. Once that completed I migrated to the new scalix server. Over 10GB if mail data was moved using this method successfuly.

I did use imapsync, when I could, to duplicate the folder directory structure, which helped emensely when migrating with thunderbird.

The file server has had only one glitch which I adressed today. My ethernet driver managed to get itself hosed up, and stopped communicating on the network. I had to reboot the sever to get it to communicate again.

Other than that Everything has been working just fine.

Sincerley,

Sideband Samurai

Thanks for that Sideband Samurai!

Best wishes,
Don