Hmmm, it just doesn't work for me. So i am using "argv=/usr/bin/script test" so that it works.
The thing to note is that I don't need the envelope sender or recipient - maybe in the future, but for now, I really don't need it. Imagine a transport which literally dumped the incoming email to a file on disk - would you then need the envelope sender or recipient? I just want the completely raw email in a certain cirumstance. Anyway, I'll try to figure out why it's not working with anything after after the command in argv line. Matt Wietse Venema wrote: > Matt Galloway: > >> Hi, >> >> I've been playing with my own transport in Postfix and I have >> successfully managed to get it working using pipe to pipe the mail to my >> script. However, I notice it only works when I have something after the >> command in the argv line. >> >> i.e.: >> argv=/usr/bin/script >> >> This doesn't work, but: >> argv=/usr/bin/script $sender >> >> or: >> argv=/usr/bin/script something >> >> these both work. >> >> When I say the first doesn't work, I mean that the mail isn't present on >> STDIN for the script. Is this behaviour normal? >> > > When I test Postfix with the following master.cf entry: > > syslog unix - n n - - pipe > flags=FORD null_sender=uucp user=uucp argv=logger > > This executes the logger command and updates logfiles as expected. > > BTW, a mail handling script that ignores the envelope sender or > recipient is broken by design with 99.9999% certainty. > > Wietse > >
