One of the recent Mail.dll email component updates brings the ability to process BinHex encoded email attachments.
BinHex is short for “binary-to-hexadecimal”. It is a binary to 7bit ASCII text encoding, that was used on the Mac OS for sending binary files through email. It is similar to Uuencode and Base64 encodings (both supported by Mail.dll), but it combines both “forks” (data and resources) of the Mac file.
As with all other data-to-ASCII encodings, BinHex files usually take more space than the original files, however as BinHex includes very simple run-length compression, encoded files may be smaller under some circumstances.
Below you can see such file inside a MIME entity:
Content-type: application/mac-binhex40; name="binhex.test.sit"
Content-disposition: attachment; filename="binhex.test.sit"
(This file must be converted with BinHex 4.0)
Mail.dll is going to extract data fork from such entity and put it in the IMail.Attachments collection, just like it was attached using standard MIME-way.
byte eml = ...; IMail mail = new MailBuilder().CreateFromEml(eml); Assert.AreEqual(1, mail.Attachments.Count); MimeData att = (MimeData) mail.Attachments; byte data = att.Data; // data fork
You can control, if BinHex attachments should be processed using MailBuilder.ProcessBinHexAutomatically property:
byte eml = ...; MailBuilder builder = new MailBuilder(); builder.ProcessBinHexAutomatically = false; IMail mail = builder.CreateFromEml(eml); Assert.AreEqual(1, mail.Attachments.Count); MimeBinHex binHex = (MimeBinHex) mail.Attachments; byte data = binHex.BinHex.Data; byte resource = binHex.BinHex.Resource; string name = binHex.BinHex.Name;
As you can see, data fork is not extracted automatically and you can use MimeBinHex instance to access both data and resource forks and other information stored inside the BinHex encoded attachment.