Hey All; > -----Original Message----- > From: John Simpson [mailto:[EMAIL PROTECTED] > Sent: Friday, September 28, 2007 3:22 PM > To: vchkpw@inter7.com > Subject: Re: [vchkpw] Possible problem with nested pipes in vpopmail > 5.4.18? > > On 2007-09-27, at 2116, Tren Blackburn wrote: > > > > However as soon as I append another pipe like so: > > > > cat .qmail-default > > > > |/home/vpopmail/etc/qmail-pipe |/home/vpopmail/bin/vdelivermail '' > > bounce-no-mailbox > > with a line like this, qmail-local will see the "return value" for the > line as whatever came from vdelivermail... and vdelivermail WILL run, > regardless of what qmail-pipe may or may not send to it. > > like tom said, if your "qmail-pipe" doesn't alter the message, then put > the call to "qmail-pipe" on one line, and the call to "vdelivermail" on > the next line. in that case, any non-zero exit from qmail-pipe will > prevent qmail-local from running vdelivermail. > > and if qmail-pipe DOES alter the message, then qmail-pipe needs to > execute vdelivermail as a child process, sending the altered message to > vdelivermail's stdin, using the normal pipe(), fork(), and file handle > shuffling routine (or if qmail-pipe is written in perl, 'open > (O,"|vdelivermail ...")' will fire up the child process and do the file > handle shuffling for you, and you can just print the modified message > to file handle O.)
Thanks for the help and ideas. I ended up using maildrop to deal with this. It wasn't nearly as painful as I expected, and seems to deal with things much more efficiently then my shell scripting skills would have been able to. Cheers! Tren
