Hallo,

I've tryed to open one simple HMT-File, but got this exception.

Can you please, help me?!

P.S. File and screenshoot of exception inside attached file.

Thanks in advice!

Hello Alexander!

Thank you for reporting this.

I have reproduced the exception. This is a known issue #7473 with Aspose.Words. It has been fixed in the current codebase. The correction will be available with the next public build (3-4 weeks). Technical reason is that "multipart/alternative" hasn’t been supported. We’ll notify when the new release comes.

Hallo Klepus!

Thanks for your response!

Klepus:

Hello Alexander!

 

Thank you for reporting this.

 

I have reproduced the exception. This is a known issue #7473 with Aspose.Words. It has been fixed in the current codebase. The correction will be available with the next public build (3-4 weeks). Technical reason is that "multipart/alternative" hasn’t been supported. We’ll notify when the new release comes.

 

Regards,

I would like to know how to get and apply a path for this issue, because I must immediately create and evaluate a test-bevore-buy application.

Thanks in advice!

Hello!

Thank you for interest in Aspose.Words.

We are going to release a new version very soon. Hopefully on the next Monday. It’s difficult to provide a patch right now because it requires a lot of activities to build and test. Making a release is quite a complex procedure even despite it’s highly automated. So let us fix some more issues and improve the product a bit more. Thank you for understanding.

Hello!

Klepus:

Hello!

 

Thank you for interest in Aspose.Words.

 

We are going to release a new version very soon. Hopefully on the next Monday. It’s difficult to provide a patch right now because it requires a lot of activities to build and test. Making a release is quite a complex procedure even despite it’s highly automated. So let us fix some more issues and improve the product a bit more. Thank you for understanding.

 

Regards,

Is new version already available?

Thank you!

Hello Alexander!

Thank you for your patience. No, it isn’t. We’re working on this. Will release today or tomorrow. You’ll be notified via the forum.

The issues you have found earlier (filed as 7473) have been fixed in this update.

Thanks for update!

aspose.notifier:

The issues you have found earlier (filed as 7473) have been fixed in this update.

---

This message was posted using Notification2Forum from Downloads module by aspose.notifier.

Unfortunatelly, similar another mhtml problem a still peresent in the newest update - I got Exception "Cannot read from closed file" or "Cannot read from closed strem".

File is attached.

With our C# MIME-Parser I can parse this file without any problems and also Outlook  can open and show this file correct.

Do you like to share our code? For such case I need your mail-account.

Have you fix for this problem?

Thanks in advice.

I've done conversion so that convertet file does not have multipart/related and have only multipart/mixed and multipart/laternative (which must be supported in the 6.6.0 release), but this file is not loaded properly also.

File attached.

Thanks!

Hi

Thank you for reporting this problems to us. I managed to reproduce both of issues. You will be notified as soon as them are resolved.

Best regards.

Hello Alexander!

Thank you for experimenting with our new release.

I can explain what happens with these documents. Probably you would be able to find workarounds.

a5.eml has a very long primary header. When Aspose.Words reads a document it first briefly detects file format, then instantiates appropriate huge importer objects. It’s a very lightweight algorithm analyzing first 512 bytes of any file. During file format detection signatures, mime types etc. might be checked. HTML and MHTML don’t have any signatures. So we have to accept anything that looks like a mime header searching for some mandatory records. For instance, MHTML detection requires that "Content-Type" occurs within first 512 bytes. This doesn’t happen in your document and format detection fails. How long the detection buffer should be s a philosophical question. RFC 2557 and RFC 822 don’t restrict header length. But we don’t want to read any candidate file potentially up to the end. I’ll try to improve detection to cover your cases but right now you can enforce importing MHTML by specifying format explicitly:

Document doc = new Document("a5.eml", LoadFormat.Mhtml, string.Empty);

When I did this I found another issue. The main HTML document is not read. Here is also format detection. It’s needed in general case to ensure that the source has proper encoding. Since encoding is already specified in a subsidiary header we can soften the conditions. As a workaround you can enclose the whole document in <html> … </html> tags.

a6.eml is not read because multipart/mixed content type is not supported. Other multipart messages (alternative and related) are imported okay.

I have linked your requests to appropriate issues. You’ll be notified when they are fixed.

You can share any materials with us by sending them via Aspose website:

http://www.aspose.com/corporate/purchase/faqs/send-license-to-aspose-staff.aspx

  Hello!

Thanks for quick response!

I've tried some of this methods but it does not help.

Document doc = new Document("a5.eml", LoadFormat.Mhtml, string.Empty);

does not load the document.

Encoluring inside <html>...</html> and load with LoadFormat.Html have result, the whole file is totally unreadable plain ascii text.

I think, it's not to easy on customer site to do any fixes.

Thanks.

Hello,

Klepus:

...

 

You can share any materials with us by sending them via Aspose website:

http://www.aspose.com/corporate/purchase/faqs/send-license-to-aspose-staff.aspx

 

 

Regards,

Core MIMER classes send you per mail.

Thanks.

Thank you for your materials. I’ll take a look. I mean as a workaround you should add <html> … </html> and force MHTML format (not HTML) when reading the document. There are some minor issues but at least the document will be read without any fixes to the library.

Hello Alexander!

I’d like to ask for your advice regarding multipart/mixed MIME content type. Recently we got a file with this content type from you (a6.eml). Multipart/mixed is intended to pack several independent documents in one archive. In general there could be several items of any type: documents, images, attachments etc. When viewed in compatible browsers and mailers multipart/mixed parts are shown one after another. But it’s difficult to guess how they could be read into Aspose.Words document model. Import is designed to load one document file and produce one document model. Shall we choose from multipart/mixed parts or just concatenate anything found in one document? What can we do if multipart/mixed occurs on nested levels? Maybe it’s good to have several documents in output. This depends on the application tasks. Of course parsing MIME archive with multipart/mixed is not a problem since multipart structure is the same as for multipart/related and multipart/alternative.

This MIME content type is not frequently used. And I don’t see realistic scenarios how it can be processed by Aspose.Words. Maybe you tried multipart/mixed only as an experiment. Please let me know how you see this. There are two more multipart subtypes: multipart/parallel and multipart/digest. They are also not supported under the same reason.

Thank you in advance.