ugh.
when you see those errors -- fatal errors -- that means your script will most likely not function as advertised in certain, potentially critical points.

For you to not care that your code is coughing up these errors is sloppy. Why bother loading Mime::Lite if its dependencies aren't met?
Take everybody's advice and either satisfy Mime::Lite's requirements. When you say

I believe many of the modules that Mime::Lite uses are optional and I don't use them so I guess that why it works...
you should be a little sad. Know how your script works and know what's required. If you're resorting to guessing why it works, you're going to be well and truly baffled when it breaks.

In reply to Re: Turning off carp(fatalsToBrowser) [briefly]? by boo_radley
in thread Turning off carp(fatalsToBrowser) [briefly]? by jfrm

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.