The problem is, we want to do a more global system, as we have tons of utilities sending out mail and all the bounced mail is landing in root, they have tons of old mail backed up. I'd like to build both a retroactive and a proactive solution but having problems doing so as nobodys mail server seems to be returning consistently formatted errors. I'm looking into the idea of seeing if sendmail can remote connect and validate but not having much luck. Someone suggested: 
/usr/lib/sendmail -oeq -bv the@email.com;  echo $status

[download]
but not returning much of anything useful :(

In reply to Re: Re: Email Parsing of mail files for e-mail errors by notbob
in thread Email Parsing of mail files for e-mail errors by notbob

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.