Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>writing a string parser of the mail message IS in fact writing a simple MIME parser. You can write a quick-and-dirty MIME parser in a few hours. If you will use it for parsing similar mails (e.g. sent from one location by same client software) it should all you need. </p> <p>For details about MIME see</p> <ul> <li><a href="http://www.ietf.org/rfc/rfc2045.txt" rel="nofollow noreferrer">RFC 2045</a></li> <li><a href="http://www.ietf.org/rfc/rfc2046.txt" rel="nofollow noreferrer">RFC 2046</a></li> <li><a href="http://www.ietf.org/rfc/rfc2047.txt" rel="nofollow noreferrer">RFC 2047</a></li> <li><a href="http://www.ietf.org/rfc/rfc2048.txt" rel="nofollow noreferrer">RFC 2048</a></li> <li><a href="http://www.ietf.org/rfc/rfc2049.txt" rel="nofollow noreferrer">RFC 2049</a></li> <li>RFC 847, 3217, 3370, 3852, 3851, 3850 are also relevant but you can skip them for start</li> </ul> <p>Few days of work should be realistic. I was involved in development of a simple in-house MIME parser (took few days to hack and parsed 95% of received emails), which envolved into a commercial product (few months of work, tons of unittest and hudreds of really vierd test emails from the wild) and then was modified so it can be used in Compact Framework (changes because of memory-constrained devices, changes because only small portion of .NET framework is ported to .NET CF). And add rewriting of quite big part of CryptoAPI functionality in order to make signed and encrypted S/MIME emails work on .NET CF.</p> <p>The MIME parser is part of the Rebex Secure Mail for .NET/.NET CF component and can be downloaded from <a href="http://www.rebex.net/secure-mail.net/" rel="nofollow noreferrer">http://www.rebex.net/secure-mail.net/</a> </p> <p>All version of .NET and .NET CF are supported. Even the .NET CF1 dinosaurus ;-). However, it's not free.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload