Another alternative is using chromatic's Test::MockObject to simulate the mail server. Mocking allows you to unit test your mail generating component independently from the mail server, and you will be able to trap the output of your code to verify the contents of your mail.

This will not be enough, though, as you will need to test the component in combination with the mail server too. The unit tests will verify the interfaces between the two. I don't think mocking is the complete solution to your problem, but it will get you closer to your goal.

Good luck!

pernod
--
Mischief. Mayhem. Soap.

Update: Fixed som typos

In reply to Re: Testing email send and Test::MockObject by pernod
in thread Testing email send by Euclid

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.