Hi! I'm trying to log the email sending result using Email::Sender, both OK and failure. In the doc, it says that when the message was sent, the result will be an Email::Sender::Success object that it is only a "true" value, but I found that it has a "message" property and I use it to write in the log.

The problems start when there is an error. The doc says that it will throw an object of the class Email::Sender::Failure with a "message" attribute describing the error, but it also dies!!! To avoid the unexpected finish, the module includes a method called "try_to_send", but on error it only returns "false" and no messages. Alternatively I could use Try::Tiny by myself, but I couldn't retrieve a "message" attribute in this case. Also, I couldn't find an example on how to catch the failure object correctly...

Any hint? Thanks in advance!

In reply to How to capture the failure reason of Email::Sender? by vitoco

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.