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

use Perl Log In

Log In

[ Create a new account ]

rjbs (4671)

  (email not shown publicly)
AOL IM: RicardoJBSignes (Add Buddy, Send Message)
Yahoo! ID: RicardoSignes (Add User, Send Message)

I'm a Perl coder living in Bethlehem, PA and working Philadelphia. I'm a philosopher and theologan by training, but I was shocked to learn upon my graduation that these skills don't have many associated careers. Now I write code.

Journal of rjbs (4671)

Tuesday August 28, 2007
07:17 AM

new mime::lite

[ #34245 ]

MIME::Lite is, in my opinion, the worst of the popular email object modules. It's buggy, has a lousy interface, and just does awful things. I'd go so far as to say that the number one mistake I see in new email modules is a reliance on MIME::Lite instead of Mail::Message or Email::MIME.

That said, I've just released the first non-developer release of MIME::Lite in over four years! I get a nightly report of bugs in all (or much) of the CPAN's email code, and nearly a third of those have long been bugs in MIME::Lite. I've closed a number of them already, and will try to close some more. So far, I think that nothing much should break, but it's hard to say. The tests for MIME::Lite::HTML now fail, but only because it relies on receiving exactly identical output, and the location of the MIME-Version header has changed. (That's another lousy module, by the way, which was for a long time the only game in town. It's finally been superseded by Email::MIME::CreateHTML.)

Please report problems with this new release of MIME::Lite to its bug tracker at

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.
  • I never had a problem with MIME::Lite. Should I go with Mail::Sender instead?
    • You should be using, imho, a mail object class for constructing your message and another tool for sending it. I'd suggest that you use, for the first, either Email::Simple, Email::MIME, or Mail::Message. For the later, Email::Send, at least until it is replaced by Email::Sender, which has long been languishing in the wings.
    • Or if you want something that dumbs down the whole process of doing things the "right" way (rjbs tells me how to do things the right way, and I dumb them down) you could use something like Email::Stuff [].
  • MIME::Lite has always worked well for me, and I like the convenience of having build/send packaged together. (Hey, at least they are separate methods).

    Now that it has been improved, I'll have less reason to quit using it. :)

    Thanks for the update.