> If the filter reports success to Postfix before giving the FILTERED > message to the Postfix queue, then Postfix will remove the UNFILTERED > message from the queue too early, and you will lose mail when (not > if) the filter has a problem. >
The filter re-injects the message back into the queue prior to what I am doing. Basically, I'm saving a copy of the message and the envelope, re-injecting it back to postfix, then exiting with 0 (similar to a callout to spamassassin). Prior to that exit call, I need to call a script that will process this message. Let's call it the post_content_file script. I don't care if the post_content_filter script succeeds or fails (as I have a backup process to handle some of it), I just need to trigger it. The idea is at the end of the content_filter, prior to exiting with 0, to call a script that will internally fork, then immediately return back to the original content_filter, so it can exit. My question is will this fork process cause any problems with postfix itself? I just don't know what the impact of a fork in the content_filter will be. Gary-
