Re: A message on which hypermail cannot do anything with

---------

From: Peter C. McCluskey (pcm@rahul.net)
Date: Tue Jan 21 2003 - 00:09:56 CST

  • Next message: Daniel Stenberg: "Re: A message on which hypermail cannot do anything with"

     rvt@dds.nl (rvt@dds.nl) writes:
    >I just found a message on which hypermail says 'No mail to output!'

    >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.
     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.
     Discarding the entire body doesn't seem right, but I don't see an easy
    way to handle it cleanly. Maybe I can find a set isinheader to something
    other than 0 or 1 when looking for a mime boundary, and then keep any
    nonboundary lines found while looking for the boundary to be used if no
    valid mime section is found. But it looks like with this approach it would
    be hard to use any of the code that handles Content-Type. Does anyone else
    have a better idea?

    -- 
    ------------------------------------------------------------------------------
    Peter McCluskey          | 
    http://www.rahul.net/pcm | 
    

  • Next message: Daniel Stenberg: "Re: A message on which hypermail cannot do anything with"

    ---------

    This archive was generated by hypermail 2.1.5.