Hi all,
I'm chugging along writing our very-specific-to-our-application code,
and I'm currently working on the spamassassin code. We have multiple
user-configurable message handling possibilities: queue, reject with 550
error, delete with 250, send to alternate "quarantine" address / local
storage, alter subject, alter body. I'm currently swimming around in
this world of possibilities modifying the spamassassin plugin heavily to
get it to deal with all these possibilities for multiple recipients with
different settings etc. I'm wondering, is there some supported, "right"
way to basically clone a transaction so that I can modify aspects of it
like the message body and/or subject for one list of recipients while
leaving it intact in the original transaction object for the recipients
for which the message is passing through unmodified? I may be able to
write something specifically to deal with this but it seems like it
would be difficult to do so without being sloppy, e.g. losing the
opportunity to run through the rest of QP's hook / plugin structure from
where we left off. The few in #qpsmtpd believed this was an area where
no specific support exists right now, but I thought I'd open the
question up to this possibly wider audience :) Perhaps the best method
would be to write a patch implimenting Qpsmtpd::Transaction->clone()?
Is this something that would be desirable for QP upstream?
We're pushing to alpha our QP-based product by the end of this month and
beta by the end of the next... so this is not the last question I'll be
posing to this list :)
-Jared Johnson
Software Developer and Support Engineer
Network Management Group, Inc.
620-664-6000 x118
--
Inbound and outbound email scanned for spam and viruses by the
DoubleCheck Email Manager: http://www.doublecheckemail.com/
