New MIME::Lite

brian_d_foy on 2007-08-28T19:33:00

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 rt.cpan.org.


Rats

sigzero on 2007-08-28T22:20:03

I never had a problem with MIME::Lite. Should I go with Mail::Sender instead?

Re:Rats

rjbs on 2007-08-28T23:03:52

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.

Re:Rats

Alias on 2007-08-28T23:56:09

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.

Re:Rats

sigzero on 2007-08-29T01:14:46

Yes, I need the dumbed down version. Thanks!

Thanks

markjugg on 2007-08-31T18:41:40

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.