NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Displaying poll results.
sendmail/qmail/postfix/exim/etc.
| |
36% |
147 votes |
Mail::Sendmail
| |
15% |
63 votes |
Mail::Bulkmail
| |
1% |
5 votes |
398 total votes.
[
Voting Booth |
Other Polls |
Back Home
]
- Don't complain about lack of options. You've got to pick a few when you do multiple choice. Those are the breaks.
- Feel free to suggest poll ideas if you're feeling creative. I'd strongly suggest reading the past polls first.
- This whole thing is wildly inaccurate. Rounding errors, ballot stuffers, dynamic IPs, firewalls. If you're using these numbers to do anything important, you're insane.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Best practice? (Score:1)
Neat question. So, I know There's More Than One Way To Do It and all, but which is The Right Way?
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Re:Best practice? (Score:3, Insightful)
Way to easy (Score:1)
Re:Way to easy (Score:1)
Hey, that's taking the easy way out. IO::Socket is just a convenience wrapper around the raw socket routines.
perldoc -f socketJ. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Re:Way to easy (Score:2)
/J\
Re:Way to easy (Score:2, Funny)
/dev/tcp! The luxury! Why, in my day, we had to compose Ethernet frames by hand and fiddle with network card I/O ports to get anything sent. And there weren't none of this full duplex nonsense back then, either. You young whippersnappers....
--
Esli epei eto cumprenan, shris soa Sfaha.
Aettot ibrec epesecoth, spakhea scrifeteis.
Re:Way to easy (Score:2, Interesting)
This code was used to send updates to traffic light controllers. I don't know if they are s
Re:Way to easy (Score:2, Funny)
The good news was that they had a built-in Ethernet chip. The bad news was that they did not have enough RAM to load the TCP/IP drivers. Rather then install more RAM, the obvious (!) solution was for the safety system to just drive th
You left out... (Score:0)
All my friends are on AOL!
;-)
Mail::Mailer (Score:1)
Re:Mail::Mailer (Score:1)
Re:Mail::Mailer (Score:2, Insightful)
Pudge, this has been very enlightening. Please consider having more polls like this in the future. It may be that TMTOWTDI, but I like knowing I've picked a solution that lots of smart people picked, too.
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Net::Mail (Score:1)
Re:Net::Mail^H^H^H^HSMTP (Score:1)
Re:Net::Mail (Score:1)
I didn't mean I had picked what lots of smart people had chosen. I meant I wanted to pick what lots of smart people have chosen and then feel good about it.
I'd like to hear more on this issue, too.
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
But what about (Score:1)
I love it:
my $msg=MIME::Lite->new(
From => $hr->{'email'},
To => ADMINISTRATOR_EMAIL,
Subject => "New Applicant",
Type => 'TEXT',
Data => "The application for $hr->{'name'} is attached to this email message in HTML format.\nOpen it in your web browser to view or print.",
);
$msg->attach(
Type => "text/html",
Data => $app,
Disposition => 'attachment',
Filename =>'ap
Re:But what about (Score:2, Informative)
Also missing.. Blat (Score:1)
Don't trust Javamail.... (Score:1)
Besides the fact that I use Mime::Lite for the majority of my tasks where I need to send email from an application, I also don't trust Javamail to get the job done.
More than one occasion I have run into issues where Javamail never emitted any sort of error but the email did not get sent.
My solution: have Java hand email requests off to Perl through a database.
create table email_request (email_request_id serial not null primary key,
subject text not null,
message tex
Peter L. Berghold -- Unix Professional