StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2300136
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-02-19T22:43:05.290
FavoriteCount
0
LastActivityDate
2010-02-19T22:43:05.290
LastEditDate
LastEditorUserId
0
OwnerUserId
277341
ParentId
2274097
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I'm afraid it's not possible to migrate data to MS Exchange 2010 without changing the e-mail source. Exchange 2007 no longer stores the actual MIME data (which is the format you get from the IMAP server) and only re-constructs it on-demand. They only store what they call a "MIME Skeleton" - see this <a href="http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/21adbe96-e21b-458a-8242-2c3894b9d7cf" rel="nofollow noreferrer">MS forum</a>. What I have not found in that forum but observed myself is the that this reverse process doesn't usually produce a message identical to the original one - the content of MIME entities is unchanged, but its structure is often altered - different content-transfer-encodings are used, some headers or added or modified, and so on. At least that's how messages in user mailboxes are stored - but my guess is that it's the same for public folders. Also, it is possible (although unlikely) that Exchange 2010 behaves differently than Excahnge 2007. And while I'm not an expert on MAPI, I think that MIME format is not even used in it (Outlook can't even save a message in MIME format), which would make MAPI an unlikely solution for preserving the email source. So my advice is to do what you already tried - get the e-mail data from the IMAP server in MIME format and store it using Exchange Web Services. We are doing this to move e-mail messahgs from an IMAP server into Exchange 2007 user mailbox and never had any problems with broken e-mails (but then again we don't have 400GB of data).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POmigrating emails from imap to exchange 2010 using c#
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USLukas Pokorny
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POmigrating emails from imap to exchange 2010 using c#
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThanks for this, will have to give it ago.
 singulars
 PostPostId
 PO
 UserUserId
 USGrant Collins

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.