To 1: Yes thats exactly what happened and i understand the result. My point is that maybe you could allow user to chose in what format to save the mail on disk. I would prefer to save the email in unchanged format so that the RTF to HTML conversion is performed on runtime. This way each time you make your RTF parser better all i need to do is update the libraries and run it against all saved emails. Right now i have to download the emails again from mail server where they can be already deleted. This is just an idea.
To 2: Yes the bug is fixed thanks! If you would like to make your parser even better here is another sample email in RTF format. Just to be clear, I'm not personaly using RTF but potential clients can so I'm trying to prepare for it. Email was created in Outlook 2013 and i added two images as attachments and two as embedded images. Below are two screenshots of how the email looks like in Outlook and when parsed to HTML using Rebex library. One difference is the missing footer image and the other thing is that images added as attachments are recognized are accessable after parsing in Resources collection (maybe it should be in Attachments ?) This is no deal breaker for me but if you strive for perfection I'm willing to provide sample data :)
And here how it looks like when parsed to HTML using Rebex library
