I agree with you that many people use Net::SMTP when the should be using other modules that are more well suited to quickly "building and sending" an email. However, there are many situations where using Net::SMTP as part of an overall mail solution where you need/want more control and more percise error handling over the SMTP exchange, or for the performance reasons mentioned above.
I frequently use Net:SMTP in conjunction with a module like MIME::Lite, using MIME::Lite to build the body of the message and Net::SMTP to inject it into an email system. Sure, I could use MIME::Lite to send the email via SMTP myself, but I'd loose control of the error handling of the SMTP exchange (for instance, failing over to a backup mailserver easily if my primary mailserver is down).
I don't see any problem with having to separate out each address individually when dealing with Net::SMTP. I normally have the addresses in an array before, so its very easy to do a
foreach(@recipient){
$smtp->to($_);
}
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.