I have an email inbox for which I have written a script to fetch and read on demand and pick out the particular message of interest.

I had thought that splitting the message was going to be the most straightforward part as I expected some division between messages such as a === or other such specific ending on which a split can be done. Alas there was no such animal! The only constant that there seems to be is the word From at the beginning of the message, but of course if I split on that there is too much chance that it also happens to be in the message and the whole thing would go down the chute...

Since this is being done all the time by email software there must be a standard way of doing it and if anyone could help me I would as always be very grateful.


In reply to Splitting email inbox text into separate messages by jonnyfolk

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.