One rule of thumb for perl programming improvement is that if you are writing pretty much the same code over and over again in your program, you have the potental to do a lot of improvement in your program. Namely, in your case, you've got the switch block... if you take your header variables and move them into a hash, you can rewrite that as...
if (@$MsgContent[$count] =~ /^(To|From|CC|Date|Subject|Message-ID)\s*:\s*(.*)$/ ) { $MsgHash{ $1 } = $2; print "$1 : $2"; }
(The extra \s* before the : in the regex may be bad, but I can't recall if the specs allow a space there or not)


Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain

In reply to Re: Evaluation of Simple Pop3 Client by Masem
in thread Evaluation of Simple Pop3 Client by Jamnet

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.