echelon wrote:I found exporting mail from Scalix 11 and Outlook 2003/2007 to be unreliable. The export would sometimes fail but but you would not know where it had failed. In this case I would have to create a local PST file and drag and drop mail items in batches. This would let me isolate bad messages- usually ones with bad attachments (mostly from the same internal sender.) When I reimported into Exchange, the internal e-mail messages would be screwed up (they would show up as X400 or something similar.) This could be an issue if someone receive a message from a coworker on monday, migrated to exchange on tueday, then tried replaying to the message on wed. If you are in IMAP mode (vs MAPI mode) when exporting the mail from outlook you don't have this problem. I don't think it is really that big of a problem if you give the users a heads-up (my company is relatively small with a mostly computer-savvy employees.) FYI- you would have the same issue if you exported your Exchange e-mail to have a backup at home on machine with Outlook not connecting to your exchange server.
Replying to old messages after a migration, more often than not will not work because the address is not just email@example.com, its an X400 with reference to the original server. Its the same for addresses in outlook cache (nk2). Even though they may appear correct, they still have characteristics related to the source server. You have to cleanup the nk2 file for internal addresses and let users know that replying to an old email may not work, so forwarding is the better option if necessary. I've seen that happen on many migrations, not just from Scalix to whatever.