Slash Boxes
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

How do you send mail?

Displaying poll results.
  36% 147 votes
  8% 32 votes
  5% 22 votes
  5% 22 votes
  15% 63 votes
  1% 5 votes
  24% 99 votes
  2% 8 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.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • 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
    • I think the most favoured method says it all. If it is at all possible one should use the injection capabilities of the local MTA in order to avail oneself of its MX lookup, queuing and other capabilities in my opinion - of course that is not to say one shouldn't use Mail::Send or the like that provide an interface to that ...
  • What? No IO::Socket?!?
    • Hey, that's taking the easy way out. IO::Socket is just a convenience wrapper around the raw socket routines.

      perldoc -f socket
      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
      • So whats wrong with opening /dev/tcp and using some judicious ioctl on it then ;-}

        • /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)

            I once wrote code to transmit 16 data streams in parallel using a parallel IO port which had each of the 16 bits connected to a different channel. The parallel port had to be written at the right times to generate the start and end of each bit. The bit stream for each port had to be modified to ensure that there were never more than 4 consecutive bits the same. Clock times for the processor were measured in Khz.

            This code was used to send updates to traffic light controllers. I don't know if they are s
          • Don't laugh. I worked at CERN on the safety systems for one on the large experiments. Local monitoring of the devices were done with small, VME and M68k based processor cards that they had stripped from some ancient, earlier experiment. These things should be in a museum.

            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
  • AOL 7.0!!!

    All my friends are on AOL!


  • Why isn't Mail::Mailer on here? That's what I've been using. Is it obsolete and I should move on to another module?
    • Mail::Mailer and Mail::Send are basically the same thing, and are both in MailTools. I suppose it could just say "MailTools" ...
      • 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
  • MIME::Lite!

    I love it:

    my $msg=MIME::Lite->new(
      From => $hr->{'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.",
      Type => "text/html",
      Data => $app,
      Disposition => 'attachment',
      Filename =>'ap
    • MIME::Lite uses sendmail (by default). You can also tell it to send mail by SMTP (uses Net::SMTP) or provide your own handler (a subroutine ref) using whatever method you choose.
  • Not all of us are lucky enough to have ISPs who run decent operating systems :-)
  • 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