Unsolved
This post is more than 5 years old
5 Posts
0
1057
October 30th, 2014 09:00
emailxtender MAPI properties
Hello,
does anybody has list all MAPI property which EX can create. I would like to know what MAPI properties say that message was/is archived ?
Regards
Leffa
No Events found!
RKatwal
2 Intern
•
600 Posts
0
October 30th, 2014 15:00
Hello,
I don’t have EX handy to check but I remember there used to be ExMD5 property tagged to messages which will have EX messageID. There are few other properties tagged depending upon if message was only processed by archive job or a shortcut job as well.
You can use MFCMAPI to do the comparison before and after a message is processed.
Thanks,
Rajan
zleffa
5 Posts
0
October 31st, 2014 02:00
Hello,
if message was archived i can see only this property
ExMD5 with Value message ID
ExLastAccessedTime
ExLastCreationTime
I would like to know , if every property which EX using start with character Ex...
I have a issue with SourceOne, which skipped message during archive historical activity with information, "Archive job skiped message with this descriptionDescription 4X message will be skipped". This messages was previously shortcuted wit EX and restored back to user mailbox. After that EX was decommissioned and S1 was deployed. I would like to try delete every EX mapi property tagged with EX.
Regards
RKatwal
2 Intern
•
600 Posts
0
October 31st, 2014 20:00
Hi,
Have you spoken to EMC Support about it ? You are moving towards uncharted waters so be cautious. EMC consulting/partners might have done something like this or consulted on something like this in past and might be able to help in some way.
Usually for EX customers recommended path is to install SourceOne and then use In-Place Migration (IPM) to migrate from EX to SourceOne. This gets completed in short period of time once EX is all cleaned up. In your case I believe that might to be possible ? By any chance you have backup of EmailXtender .EMX files around, you might be asked for this if you consult others in this scenario.
Best regards,
Rajan