> On 05/20/2011 02:56 PM, Jared Johnson wrote:
>> We do the sort of signing that is a huge doozy, and Matt is right, it's
>> a
>> doozy :) There are a couple of ways we've accomplished re-writing the
>> body from a MIME::Entity. Honestly it seems a bit non-standard to me
> Why do you think this is non-standard? From a conceptual perspective or
> just from a tooling view?
> If conceptually, which other approach would you recommend?
just non-standard in that I don't use public API's, so e.g. if they
decided to store the body file in $txn->notes('body_file') instead of
$txn->{_body_file}, for instance, you'd be SOL. Other than that, though,
we haven't had any problems with our method :)
I'm not sure if it can be done with a public API, but if you want to look
for a method, i'd check out the POD for Qpsmtpd::Transaction, for the
various body* methods.
> I did some preliminary tests and it works.
> That also means there is no API or any other way to put an email into
> the queue, isn't it?
well, the standard way to put a message into the queue is to have the
message in a state you want it in before the queue hook gets ahold of it,
and then let the queueing plugin do its work... I think smtp-forward is an
example of a queueing plugin?
> Well, can I use this approach in a productive environment or could there
> be any side effects?
YMMV, but we've been using that method in production a while with no side
effects that I know of :)
-Jared
