That looks like it should work, unless the email in question was generated by Outlook in which case it will have a non-conformant header. (What? You don't know all of the headers that could possibly be contained in an email message and don't know to break out at the first thing that doesn't fit? Then you are probably a Netscape client and we want to make you crash. So not sorry if you are merely a trusting Perl script...)

So I don't know what the issue is, but I would suggest that the first thing you should do is take XML::Twig out of it. Just try to print the contents of the file after the header and see if that looks reasonable. Print it to a file and see if XML::Twig is happy with that. Then proceed from there.

In reply to Re (tilly) 1: Preprocessing STDIN by tilly
in thread Preprocessing STDIN by uuoc

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.