In general when you want to stop a module or function from dying, you wrap the call in an eval{ } block. Then you can test $@ to see if an error occurred. For example: 
eval {
    $msg->send();
};

if($@) {
    # We had an error, log it to a file...
    $log->add_message($email_address, $@);
}

[download]
This prevents the script from dying if send(); fails. Of course, you want to make sure sending is working properly to begin with (maybe your script is failing for some reason other than a bad email address - you can print the value of $@ to see why it is failing).

Update: Uh, let me clarify. That will catch the $msg->send() function ONLY IF it calls die() (raises an exception). So if the send() function returns true or false based on success or failure, you should check other solutions in this thread.

In reply to Re: Email error checking by saberworks
in thread Email error checking by Anonymous Monk

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.