Closed nitrotm closed 3 years ago
I found the following MS documentation mentioning potential mappings:
It seems in particular that IPM.Note.Mobile.SMS
or IPM.Note.Mobile.MMS
will not be typical email format. Do you think it could be possible to implement a fallback logic on IPM.Note.*
not specifically handled otherwise?
I would rather just add it as an enum and change the reader class to support it.
Added support for the 3 tags
@Sicos1977 I see, that's great, thanks. Where did you find the documentation about what each custom type does?
We asked around about all the possible types that we might encounter and I just received this list of possible 'statuses' (checked ones are implemented by your update):
I just Googled around and assumed most of the MSG files are like e-mails because the types start with IPM.Note.
Watch out a little bit with version 4.0 (do some good testing) I refactored the RTF parser (got rid of everything that was obsolete or unused) that extract the HTML from the RTF and I think I got everything right but since its a major overhaul you never know.
I just Googled around and assumed most of the MSG files are like e-mails because the types start with IPM.Note.
Yes, we got confirmation that they can be opened in Outlook without any extra plugins. So basically just type aliases.
We'll give v4 a try and let you know if we detect any issue with RTF parser. Thank you for the notice.
Describe the bug We came across some msg containing a message type equal to
IPM.Note.WorkSite.Ems.Filed
,IPM.Note.WorkSite.Ems.Queued
orIPM.Note.WorkSite.Ems.Filed.Re
which is an alias for email format used by iManage.Expected behavior It should be parsed as an email.
Additional context Would it make sense to create aliases such as 'IPM.Note.*' is considered an email convertible to HTML + attachments ? It seems that 3rd party providers are extending the message type to indicate some processing state (such as 'filed' in this case).