On Fri, 5 Sep 2003, Mitch \(WebCob\) wrote:
Hi Marian.
I think there are a lot of us that would like to see this work!
For things like removing executable attachments from email, etc. Would love to see what you have as I'm sure others would and then find out how to make it work.
Actually, after hearing the various arguments for and against (I used to be 'for' in-place modification of messages), I am now a fan of 'reinjection'. Sam, how easy is it to 're-inject' a message that one has modified and expect it to get delivered* as it's currently being delivered?
* assuming no change to the message that would otherwise change it's delivery.
It's fairly easy, once you have all your ducks lined up in a row. You need to simply create another control file/data file pair. The tricky part is to make sure that the existing naming and submission convention is followed: that is, the files are created in the right order, and they follow the same naming convention.
This is not well documented, so you'll need to dig through the code. The rough outline is that first the control file is created using the same rough naming convention as when delivering new messages to the maildir. The new control file is stated, and its inode is used for the name of the data file. When both the control file and the data file are ready, the control file is renamed according to its inode. There are also a few other data items that need to be taken care of too. The last step is to send a trigger to courierd to pick up the new message; that may not be necessary since the original process is going to send the trigger message itself.
pgp00000.pgp
Description: PGP signature
