Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
Thanks DWS.. I dont know why but this script doesnt want to parse emails, after piping an email to it, this is what I get:
Name "main::ent" used only once: possible typo at / line 63. Name "main::bodyh" used only once: possible typo at / line 63 +. Name "main::subject" used only once: possible typo at / line +54. Trouble parsing mail:debug: process_header warning: skipping bogus mailbox 'From ' line debug: type = multipart, subtype = alternative debug: process_multipart... debug: parsing part 1... debug: process_header debug: type = text, subtype = plain debug: process_singlepart... debug: using temp file debug: t bound: 0 wallclock secs ( 0.00 usr + 0.00 sys = 0.00 + CPU) debug: extract uuencode? 0 debug: encoding? quoted-printable debug: effective type? text/plain debug: no filename recommended: synthesizing our own debug: planning to use 'msg-12389-1.txt' debug: outputting body to disk file: ./msg-12389-1.txt

In reply to Re: Re: MIME Errors by Anonymous Monk
in thread MIME Errors by Anonymous Monk

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

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.