2015-03-10 12:31 GMT+00:00 Wietse Venema <wie...@porcupine.org>: > Roger Walters: > > Hello, > > > > I have a few chained content filters based on pipe, so when the first > > script ends its task, it sends the processed headers to the second script > > and so on. > > > > It is clear how to get the content back to Postfix as an input, using the > > sendmail command. My question is how can the last content filter tell to > > Postfix that the message has been put on hold, has been temporarily or > > permanently rejected? > > If you concatenate filters, then each filter must propagate any > successor's reject status to its predecessor. > > As documented in: > http://www.postfix.org/pipe.8.html > http://www.postfix.org/FILTER-README.html > > The "hold" response is not documented, therefore it is not supported. > > Ok, I'll check whether SpamAssassin supports status propagation in this way. Thank you.
> > When one has just one content filter I know that it's enough to print the > > command using some sprintf-like function, but I don't know how to do it > > when there are many chained content filters. > > Is that a question about UNIX command pipes? > > Except the SpamAssassin filter (which is the first, by the way), yes. The rest are bash/python scripts. Thank you, Roger > Wietse >
