> I think we should probably consider putting support for parsed messages
> into core, with the parsing done lazily if requested by the API.
It's a good idea, it's only that I haven't yet had the time and
justification to write and to test a move from the plugin model (see the
attached plugin in my newer post) to an internal API model. The plugin I
attached represents a trivially-edited version of a plugin we've been
testing in production for quite some time. It probably wouldn't be *that*
difficult or risky, though, to take the very same code and put it into the
lazy API of your choice. And I think it'd be great, even though we
wouldn't actually benefit from the laziness ourselves ;)
If you don't hate storing the resulting parsed mime in
$txn->notes('mime_body'), though, that would rock, since then it wouldn't
break our existing plugin-based forked code ;)
-Jared
