On October 11, 2002 at 12:22, "Chris Russell" wrote: > But, on the off chance something can be done, this is the body > of a message containing an image, as created by Outlook Express: > > <DIV><FONT face=3D"verdana, arial, helvetica, sans-serif" size=3D2><IMG = > height=3D45=20 > src=3D"http://www.moonfish.com/moonfish.gif" width=3D35=20 ---------^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > border=3D0></FONT></DIV></BODY></HTML> > > ------=_NextPart_001_0083_01C2711E.B7D76760-- > > ------=_NextPart_000_0082_01C2711E.B7D76760 > Content-Type: image/gif; > name="moonfish.gif" > Content-Transfer-Encoding: base64 > Content-Location: http://www.moonfish.com/moonfish.gif --------------------^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is a valid MHTML message. Instead of using cid: URLs, it makes the association by the Content-Location field. The security filtering code of the HTML filter will only preserve cid: URLs, so the 'http://www.moonfish.com/moonfish.gif' gets zapped in the HTML before entity part relations are resolved. This method is too restrictive since it is valid to reference another entity via a regular URL. I've recently checked in some changes to the CVS tree to where the above case will be handled by MHonArc, along with better support for MHTML messages. --ewh --------------------------------------------------------------------- To sign-off this list, send email to [EMAIL PROTECTED] with the message text UNSUBSCRIBE MHONARC-USERS
