Page 1 of 2

Email .msg file import corruption

PostPosted:Fri May 24, 2019 2:41 pm
by chrwei
I have several msg files exported from outlook that the message body is corrupted when added to 6.3.7. opening the msg file in outlook shows a plain text email with a few attachments. when I save the added file out of openkm it's an eml file, and that opens as an html email. the readable text from the msg file gets turned into non-printable characters in the openkm preview and the eml file.

additionally, if I use OKMRest 1.2.2 .net SDK's importMsg method the files added corrupt as with the interface, but I get an exception too: $exception {"MailImpl (importMsg)\n'\u0003', hexadecimal value 0x03, is an invalid character. Line 1, position 410.\n\ncom.openkm.sdk4csharp.exception.UnknowException: '\u0003', hexadecimal value 0x03, is an invalid character. Line 1, position 410.\r\n at com.openkm.sdk4csharp.impl.MailImpl.importMsg(String dstId, String title, FileStream fileStream)"} com.openkm.sdk4csharp.exception.OKMRestException

search results on this error lead to a possible XML conversion issue, like that 0x03 needs to be escaped but isn't

I was able to find the original raw SMTP message in my mail archives, headers mark it as:
Code: Select all
Content-Transfer-Encoding: 7bit
Content-Type: multipart/mixed;
        boundary="Apple-Mail-E819C806-3C10-4266-AB6B-491067E0E843"
text body part is
Code: Select all
--Apple-Mail-E819C806-3C10-4266-AB6B-491067E0E843
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Adjunto fotos como evidencia del rechazo

followed by a base64 image part, another plain text 7bit part that's just a couple newlines (what the hell apple), then another base64 image, and another plain text 7bit part that's a signature
Code: Select all
--Apple-Mail-E819C806-3C10-4266-AB6B-491067E0E843
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit



Enviado desde mi iPhone
all the msg files that I'm seeing issues with are spanish language, but so far I'm not seeing accented characters or anything in the original files that would explain a 0x03 character. any ideas how to go about making this work?

Re: Email .msg file import corruption

PostPosted:Sat May 25, 2019 8:24 am
by jllort
You are exporting msg from outlook and then you upload to OpenKM?
Before talking to export, the email from OpenKM is shown right?

Re: Email .msg file import corruption

PostPosted:Tue May 28, 2019 1:05 pm
by chrwei
yes, export from outlook via drag and drop email to a windows explorer folder. it shows right in outlook, and shows right in the .msg file, but once uploaded into openkm it no longer shows correctly.

Re: Email .msg file import corruption

PostPosted:Fri May 31, 2019 5:29 pm
by jllort
can you share with us the msg file to check what happens.

Re: Email .msg file import corruption

PostPosted:Fri May 31, 2019 9:26 pm
by chrwei
i'll have to dig one up that isn't confidential, or see if I can reproduce from scratch, might take a bit

Re: Email .msg file import corruption

PostPosted:Fri Jun 07, 2019 6:42 pm
by jllort
When you have someone please send us from here. If it is confidential contact us from https://www.openkm.com/en/contact.html indicating the URL of the forum and I will share direct contact with us.

Re: Email .msg file import corruption

PostPosted:Mon Jun 10, 2019 9:33 pm
by chrwei
contact form sent, but it doens't allow URLs, so I put "OpenKM English Users-> Usage-> Email .msg file import corruption"

Re: Email .msg file import corruption

PostPosted:Thu Jun 13, 2019 1:07 pm
by chrwei
Will you have a conversation with Mario Zules? he seems a little confused as to why i emailed.

Re: Email .msg file import corruption

PostPosted:Thu Jun 13, 2019 5:14 pm
by chrwei
it would seem they are aware of the cause of the issue and have it fixed in the Pro version already.

Re: Email .msg file import corruption

PostPosted:Sat Jun 15, 2019 6:47 pm
by jllort
Sorry, but at the end of the day I talk with a lot of persons and here I think we have had some miss understanding. I had not received the file, usually when somebody contact with something about the forum I ask him to share the URL of the forum post to do not lose the focus ( seems I forget to explain it ). I will send my private email address from a private message in the forum. Contact me directly and share the URL of this post. Apologies.

When I have all the data I will sure know if it is a problem with community, your mail, or some extra feature what we have in professional edition an is not currently present in the community. Mario Contacted me, but I do not being able to link the questions with this previous forum post, it is not his fault, apologies.

Re: Email .msg file import corruption

PostPosted:Mon Jun 17, 2019 1:01 pm
by chrwei
the contact form does not allow URLs. I got your email and will reply.

Re: Email .msg file import corruption

PostPosted:Fri Feb 14, 2020 6:45 am
by landi
Is a solultion available for this issue?

Re: Email .msg file import corruption

PostPosted:Sat Feb 15, 2020 7:23 pm
by jllort
If you have an issue related with email import I suggest open an issue here https://github.com/openkm/document-management-system, try to explain exactly the steps to reproduce the issue and if it is possible we need some sample to reproduce in our development environment. If this is a non-public email we will find a way you share us.

Re: Email .msg file import corruption

PostPosted:Mon Feb 17, 2020 2:03 pm
by chrwei
my specific issue didn't get resolved, and the project has been delayed so I haven't worked on it or tested a newer okm release, if any happened, in more than 6 months. my work around was to import it as not an email. my primary use was to be through the API so dealing with it in my client program was my plan.

Re: Email .msg file import corruption

PostPosted:Sun Feb 23, 2020 10:47 am
by jllort
If you do not share some sample email to reproduce the issue we can not solve it. Before sending us the sample email check in the latest version, because maybe there the issue is solved