On Tue, 7 Jan 2003, Jason R. Mastaler wrote: > Chris Hardie <[EMAIL PROTECTED]> writes: > > >> Does it now work? > > > > No: > > I don't know what to tell you. I can't reproduce the problem using an > almost identical setup. Has anyone else seen this problem?
I've got some additional data on this issue. Refresher: TMDA isn't able to deliver mail (via DELIVERY) to procmail, returning IOError: failure delivering message to command "/usr/local/bin/procmail -p /home/chris/.procmailrc_tmda" (command "/usr/local/bin/procmail -p /home/chris/.procmailrc_tmda" exited 1 ()) So, instead of delivering to procmail, I wrote a little perl script that would do a little logging/debugging while reading the message from STDIN and writing it back out to a file. I get the exact same error with this setup, and by all appearances, the perl script isn't even firing up. So, it's not TMDA+procmail that's failing, it's TMDA+any piped command in DELIVERY. That would seem to suggest a few possibilities: -The TMDA process is somehow being restricted from opening a new pipe -The pipecmd in Util.py is somehow failing -The pipe is opening successfully, but the immediately failing That takes things into unfamiliar territory for me ... does anyone have any suggestions? I just upgraded TMDA to 0.68. I'm running it on FreeBSD 4.5 with qmail, and without any special environmental restrictions for my user. Thanks! Chris _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
