Thanks for the advice from all of you. For now, Mail::Sender works fine for me. I haven't had problem with losing mails yet.
Later on, I might need to validate someone's email address
(like someone enter an email address in my web site, I want to make
sure they don't make mistake in typing, etc.), I assume I could do that
by checking with our email server.(it is all inside our company). But
Mail::Sender might not allow me to do this. I don't have memory that it could.
Then I will look for another module to do the job then.
ted
On Mar 15, 2005, at 2:40 AM, Matt Doughty wrote:
On Mon, Mar 14, 2005 at 10:12:38AM -0500, Wiggins d'Anconia wrote:Matt Doughty wrote:modules that provide #1 will provide #2 too. And because talking toOn Wed, Mar 09, 2005 at 09:42:00AM -0800, Ted Zeng wrote:
sendmail at the command line can get very hairy very quickly you are
still better off letting a module do it. The interface has been designed
for ease of use, the module has (hopefully) been tested, possibly on many
platforms, and most provide an option to set which local mail
client/server you wish to talk to. So most can handle #2 using postfix,
sendmail, etc. Net::SMTP is probably one of the ones that can't, but then
you wouldn't want to build a message with it anyways.
I spent 2 years working on an application that 90% of the time was dealing with mail inbound or out, you need to be an absolute expert in mail handling (which I am not by a long stretch!) to do so directly.
Which wasn't my point. My point was that you should choose something that
uses a local mail client. As difficult as handling message construction
might be, it generally isn't nearly as nasty as implementing queueing
yourself. Certainly, you can use something like Email::Send::Sendmail, and
then you get the best of both worlds. I was objecting to those who were
blindly recommending Net::SMTP.
--Matt
