Hmmm ... not sure but why don't you check for errors 

 
$sender->Open( ... ) or die "Error: $Mail::Sender::Error\n";

[download]

I always wrap stuff like this (Mail::Mailer) in one sub (or local package) that dies on error and then I just eval the call. 

sub mymail {
   my( $to, $text ) = @_;
   eval {
      Local::Mail::send( $to, $text );
   };
   warn "Errors: $@\n" if $@;
}

[download]

and then in the Local::Mail::send method would just be a wrapper for Mail::Sender that dies on any error.

-derby

updateI just perused the source of Mail::Sender and noticed that an exit value of 40 is SERVNOTAVAIL (and it closes the socket which explains the rest of your error messages). Moral: check for errors and act appropriately.

In reply to Re: Mail::Sender error by derby
in thread Mail::Sender error by neilwatson

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.