migrating from exchange 5.5 to kolab 2.2.1 -- imapsync issue (resolved)

[Lucas Hendricks]

The below attempt was done with the latest Mail::IMAPClient module for perl.
The error persisted even when attempting to use imapsync from one Kolab
mailbox to another using imapsync 1.99 and Mail::IMAPClient 3.16.

I reverted to the version of Mail::IMAPClient required by the imapsync and
it began to sync emails great using imapsync 1.99 and Mail::IMAPClient
2.2.9.

I'll try to update the wiki once my email verification comes =).

Lucas

-----Original Message-----
From: Lucas Hendricks 
Sent: Tuesday, May 05, 2009 4:07 PM
To: Kolab Users List
Subject: migrating from exchange 5.5 to kolab 2.2.1 -- imapsync issue

I am now starting the transition from Exchange 5.5 to Kolab 2.2.1, and I
know imapsync is a 3rd party script, but hopefully someone has seen this or
can tell me if it just isn't going to work.

Per the kolab wiki I attempted to use imapsync with the suggested command
(substituting my user login and password information for each server):

imapsync --host1 exchange --noauthmd5 --user1 "$u1" --password1 "$p1" \
         --host2 kolab    --user2 "$u2" --password2 "$p2" \
         --regextrans2 's/INBOX.INBOX/INBOX/'

First it gives permission denied errors for all the folders not inside the
inbox which I understand.

Then it seems to be connecting to each server and finds emails to sync, but
when it begins to try and copy messages, the below errors occur:

>From Folder [INBOX]
To   Folder [INBOX]
+ NO msg #13626 [fEB0wcz6JEyY7+tHduu0ag:143468] in INBOX
+ Copying msg #13626:143468 to folder INBOX
flags from : [\Seen][]
Couldn't append msg #13626 (Subject:[RE: oops]) to folder INBOX: Error
sending command '23 APPEND INBOX (\Seen) "" {143468}':
+ NO msg #13636 [iQ0F+l7aXbj3Gv3I60msug:1279] in INBOX
+ Copying msg #13636:1279 to folder INBOX
flags from : [\Seen][]
Couldn't append msg #13636 (Subject:[RE: oops]) to folder INBOX: Error
sending command '24 APPEND INBOX (\Seen) "" {1279}':


Thanks,
Lucas Hendricks
AENTC IT Support

P.S. if this is fixable the next thing I'll be searching for is a way to do
this without knowing all the individual user passwords.  Something like an
ldif I've read about, but if someone wants to toss me to a link with
info/walkthroughs that they have sitting around that would be super helpful,
thanks!