Re: Rewritten URIBL plugin

> I think we should probably consider putting support for parsed messages
> into core, with the parsing done lazily if requested by the API.

I forgot, we did kinda think of a couple of reasons not to want an API. 
depending on where you put it, you may find QP in general depending on
MIME::Parser even if it never uses it.  The benefit of the plugin is that
/etc/qpsmtpd/plugins controls whether you wind up having to install, and
take up your memory with, MIME::Parser

You could conditionally 'require', although that does do different things
to memory management that I don't understand

Another thought, there are different reasons people might want mime to be
parsed that benefit from different implementations.  If you only want the
text data, maybe you want to optimize for that somehow and throw away the
binary attachment data, or vice versa (unfortunately there doesn't seem to
be a way to do this with MIME::Parser that i've found though...).  If you
only want the text data *and* you don't mind having it not perfectly
reconstructed (like the URIBL) plugin, then perhaps you could come up with
a way to parse without MIME::Parser that is more efficient and more lazy
(not in the sense you were suggesting earlier :P)

-Jared