Re: Writing an after-queue content filter in php

2009-09-14 Thread Mathias Tausig
I just found the problem. At the very beginning of the script, I had a newline between #!/usr/bin/php5 and

Re: Writing an after-queue content filter in php

2009-09-14 Thread Mathias Tausig
Am Freitag, den 11.09.2009, 16:10 +0200 schrieb Mikael Bak: > Mathias Tausig wrote: > > I just tried to replace the "\n" with "\r\l", but to no avail. The same > > problem remains. > > I can be wrong here, but shouldn't that be "\r\n" ?

Re: Writing an after-queue content filter in php

2009-09-11 Thread Mathias Tausig
Am Freitag, den 11.09.2009, 08:38 -0400 schrieb Wietse Venema: > Mathias Tausig: > > Am Donnerstag, den 10.09.2009, 10:18 -0400 schrieb Wietse Venema: > > [...] > > > This is an output buffering problem. You need to flush output > > > after each reply, perhap

Re: Writing an after-queue content filter in php

2009-09-11 Thread Mathias Tausig
Am Donnerstag, den 10.09.2009, 10:18 -0400 schrieb Wietse Venema: [...] > This is an output buffering problem. You need to flush output > after each reply, perhaps by calling the flush() function. > Hy! No, I am afraid that this is not the problem. I am sendig you a few details of my setup Her

Writing an after-queue content filter in php

2009-09-10 Thread Mathias Tausig
Hy! I want to write an after-queue content filter for my postfix installation which is invoked by spawn (according to the FILTER_README from postfix.org). My problem is, that the input/output part simply does not work. I am sending a "220 localhost SMTP foo" to STDOUT at the beginning of the scri