Author |
|
jmc Newbie
Joined: 25 September 2018 Location: United Kingdom
Online Status: Offline Posts: 1
|
Posted: 25 September 2018 at 1:36am | IP Logged
|
|
|
Hi
We are using MailBee.Net v10.0.2.506 to create Outlook message files from data held in Microsoft Dynamics 2016 and copy and save these into SharePoint 2010sp2. All of which works fine and has done for a number of years. If we open the file from SharePoint (or download and open) then it is recognised as a valid Outlook document and opens correctly looking like a genuine Outlook message. However, when SharePoint crawls the database it fails to Index the MSG file created by MailBee. If we save and copy from Outlook directly into SharePoint there is no issue with the crawl. Can anyone suggest a) what could be wrong in the file that is preventing it being crawled to fix going forward b) If anyone can suggest a reliable iFilter to crawl these (and genuine Outlook mails) as we already have millions of stored mails using this method.
We have tried a number of iFilters from the base SP2010, Office Filter Packs, Office 365 and Windows 10 and can get none to crawl these files on SharePoint 2010. It does however work on SharePoint Online. A case was raised with Microsoft who have in essence washed their hands of it, as although they can replicate they have pointed the finger at your product.
Any assistance will be appreciated.
John
|
Back to Top |
|
|
Alex AfterLogic Support
Joined: 19 November 2003
Online Status: Offline Posts: 2206
|
Posted: 25 September 2018 at 2:22am | IP Logged
|
|
|
Hi,
Perhaps, .MSGs generated by MailBee lack some properties which are not used/needed by Outlook but required by SharePoint. Outlook can inject hundreds of various properties on different levels of MSG structure while 3rd party generators (like ours) set only the minimum set which is actually required by Outlook.
Perhaps, it's possible to find out which property or set of properties is required by SharePoint if they provide this info in their error logs (or if MS can tell you what exactly is missing). This can be used as a starting point in order to understand if it's possible to add them into our generator.
Or you can manually compare two mostly identical messages, one produced with Outlook and another one - with MailBee, get the list of properties missing in MailBee's version. Then, remove these MAPI props one by one (such as with MFCMapi tool) and feed these gradually modified messages to SharePoint. At some moment the SharePoint will stop accepting the message - this designates the moment when you found that crucial property. You're lucky then. If, however, SharePoint needs more than one property, this approach will be more complicated but the idea remains - to find out the required properties.
Still, even if they are found, it doesn't guarantee they can be replicated easily. For instance, MSG files often contain the message body in RTF format. Although MailBee can convert EML to MSG and back, it cannot convert document formats (RTF to HTML and back), document format conversion is a separate and huge task for another kind of software. If it turns out that the missing properties require sophisticated conversion procedures, it might be quite a job to implement them (although it can still be possible).
Regards,
Alex
|
Back to Top |
|
|
Ghost Newbie
Joined: 20 November 2015
Online Status: Offline Posts: 4
|
Posted: 26 September 2018 at 8:56am | IP Logged
|
|
|
Hi - I work with John who posted the initial question and will be taking over the investigation of this issue.
We have example .msg files of ones that work and ones that don't for comparsion. Would it be possible to send them over for your review? To see if you can asertain any differences that may cause this problem.
Unfortunately Microsoft were not helpful in assisting with this issue.
Regards,
Dan.
|
Back to Top |
|
|
Alex AfterLogic Support
Joined: 19 November 2003
Online Status: Offline Posts: 2206
|
Posted: 26 September 2018 at 10:26am | IP Logged
|
|
|
Hi Dan,
Please contact us via Helpdesk to arrange the terms of this project.
https://s.afterlogic.com/helpdesk/
Thanks!
Regards,
Alex
|
Back to Top |
|
|