Use MimeKit for parsing messages about msgreader HOT 14 CLOSED

MimeKit looks good, only don't know if the license can be used with the license I use...
I use the CPOL license --> http://www.codeproject.com/info/cpol10.aspx

Otherwise it would be a good replacement for the OpenPop.Net library... since I only used the Mime parsing part.

from msgreader.

MimeKit uses the MIT license which is compatible with everything.

from msgreader.

I will certainly then have a look into it. Only want to prevent to implement the complete code because the MSGReader was original build to only read Outlook MSG files and I only added the OpenPop.NET mime parsing part to support singed MSG files... but after implementing it (since it was also a mime reader) I decided to also support mime message with the MSGReader.... oops.. I think I mixed things up with your mailkit

from msgreader.

I had a look into MimeKit... you did a very nice job... I have seen terrible code and this certainly was not that 👍

from msgreader.

Thanks! This library is based on a C library I worked on for 14 years, so it's been through a ton of design iterations to get to this point.

If you decide to use MimeKit, let me know if you run into any problems or have any questions and I'll try to help.

from msgreader.

I will do that, I'm also going to use your MailKit implementation in something I did program at work. I was looking today for a MAPI implementation (to replace OpenPop.NET POP3 because it lacks the use of folders) on nuget and found AE.NET.Mail but your MailKit looks like a much better solution. Already started to implement the XLIST command in AE.NET.Mail but why do that if you already did the job :-)

from msgreader.

How did you find my MSGReader project? Did you search on GitHub?

from msgreader.

Yea, I was just searching for email-related C# apps on GitHub that looked like they were still active.

from msgreader.

Yea, this project is alive... just released the MSGReader as a NuGet package because some people requested it. This version still has the OpenPop.NET mime parser in it but I'm probably going to replace it with some of your code.... but I first have to figure out what parts I need and what I don't need. After that there probably isn't much coding to do anymore on this project. Anything I needed is in the library.

from msgreader.

Hey... question for you. I'm looking over your code and it looks like you have your own TNEF reader (the MAPI stuff). I'd be curious to know how much of that code you'd be able to replace with MimeKit's TNEF implementation.

MimeKit doesn't (yet) have support for converting RTF into HTML, but that is something I've been planning on implementing. Ultimately, what I'd love to have in MimeKit, is a clone of Microsoft's TextConverter API (not necessarily an exact clone, but something similar at least): http://msdn.microsoft.com/en-us/library/microsoft.exchange.data.textconverters(v=exchg.80).aspx

from msgreader.

What part of the code do you mean with the MAPI stuff? I never did anything with TNEF so I don't know how that works. And I need to look into your code to see if some parts could be replaced. There are even more parts that could be replaced by other native .NET code. Like most of the Native Methods (with this https://github.com/Sicos1977/CompoundFileStorage) but like everything that takes a lot of time and testing and that is something I don't have the next few weeks.

For the RTF to HTML conversion I found something on the internet that some Microsoft person had made. I refactored about half of the code to fit my own needs. It is not perfect but it does do the job. It has some disadvantages but it works good. And it is also a lot of work to write your own RTF to HTML converter. You first need to parse all the RTF tokens and convert them likewise to HTML.

Greetings,
Kees van Spelde

from msgreader.

I meant this code: https://github.com/Sicos1977/MSGReader/tree/master/MsgReader/Outlook

You have a lot of MAPI property stuff in there to decode MAPI streams and such. I'm pretty sure that is also known as TNEF, which MimeKit has support for parsing/decoding (see the MimeKit.Tnef namespace).

I think you could replace a lot of it with MimeKit's TnefReader, TnefPropertyId, etc.

I also wrote an RtfCompressedToRtf class which incrementally decompresses an RTF Compressed stream as data passes through it.

(MimeKit is designed around streams, so one of the cool features it has is the FilteredStream which you can attach data filters to that it will push data through when you read/write to/from the stream).

from msgreader.

TNEF does not seem to be the same as MSG... see this uri

http://social.technet.microsoft.com/Forums/office/en-US/f5058201-8e26-4e50-9b4b-8a9a9611b47c/differences-between-tnef-msg?forum=exchangesvrdevelopment

and see this uri for a more detailed explanation of the MSG internal format.

http://msdn.microsoft.com/en-us/library/ee217698%28v=exchg.80%29.aspx

from msgreader.

Thanks. That's a bummer, it looks like decoding both is very very similar. Oh well.

from msgreader.