On Mon, 20 Jan 2003, Peter C. McCluskey wrote:
> >Content-Type: multipart/alternative;
> > boundary="----=_NextPart_000_0001_01C2B231.93642270"
> >X-Mailer: Microsoft Outlook, Build 10.0.2627
> >Importance: Normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
> >X-Spam-Status: No, hits=0.0 required=100.0 tests= version=2.20
> >X-Spam-Level:
> >
> >Content-Type: text/html;
> > charset="iso-8859-1"
> >Content-Transfer-Encoding: quoted-printable
> >
> ><html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
>
> I'm looking for advice from anyone who understands hypermail's
> mime-handling code about what should be done with this kind of message.
I once wrote it, but I can't say I remember every bit of it.
In the above case, there's an obvious error in the mail. It says multipart and specifies the boundary string, but then there's no boundary string appearing...
> Hypermail sets variable isinheader to 1 after detecting the end of the
> regular headers. It expects to find a mime boundary next, and because there
> isn't any boundary until the end of the message, it decides the message has
> no body.
I guess we need to figure out a way where we stop searching for the boundary string. It will be a somewhat artificial thing to do, since a mail *can* in fact contain ANYTHING so checking for something particular to bail out can be tricky.
> Discarding the entire body doesn't seem right, but I don't see an easy way
> to handle it cleanly.
Me neither.
Getting nice output with junk input is not easy.
--
Daniel Stenberg - http://daniel.haxx.se - +46-705-44 31 77
ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol
Received on Tue 21 Jan 2003 03:55:44 PM GMT
This archive was generated by hypermail 2.2.0 : Thu 22 Feb 2007 07:33:54 PM GMT GMT