[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
aliases and piped commands ?
Is there anything unusual regarding pipes in aliases under zmailer?
VERSION: ZMailer router (2.99.25 #2: Mon Aug 5 01:26:17 MDT 1996)
HOST: Linux laddie 2.0.18 #2 Sat Sep 7 12:05:24 MDT 1996 i586
I get a 'signal 11' in the transport queue when testing out a simple list
server (BeroList-1.0.1):
MailQ
0 entries in router queue: idle
1 message in transport queue: working
local/test-list:
338-4032: [signal 11] (retry in 2m5s, expires in 2h54m58s, tries=4)
id <Pine.LNX.3.91.961017234828.10828A-100000@laddie>, 598 bytes, age 4m50s
from James MacKinnon <jmack>
to "| /usr/local/berolist/bin/list"
Yet Berolist performs flawlessly if tested directly from a shell (with a
copy of the above file 338-4032 in the queue/ directory as input):
# list < 338-4032
BeroList 1.0.1 ready...
Sending to list...
Sending...
#
(the message then gets delivered to the list recipients.)
The aliases entry is:
# grep test-list /zmailer/db/aliases
test-list: "| /usr/local/berolist/bin/list"
Is there a special syntax I'm missing here in the aliases file?
None of zmailer logs shows any error diagnostic.
I'm unclear as to when zmailer passes off the message, and what
the format of the headers passed to the pipe is at that point (is it
identical to the queue/ file or is it more primitive, i.e. like the
router/ file ?) - Berolist does look for 'To:' and 'From:' components
in the stream, processes them, and then makes a piped system call (popen)
to sendmail (defined to be zmailer's in this case).
It works fine under a standard unix sendmail. I'm at a loss as to why
zmailer's sendmail doesn't work for this list server.
Any help appreciated,
--
James S. MacKinnon Office: P-139 Avahd-Bhatia Physics Lab
Team Physics Voice : (403) 492-8226
University of Alberta email : Jim.MacKinnon@Phys.UAlberta.CA
Edmonton, Canada T6G 2N5
WWW: http://www.phys.ualberta.ca/~jmack/jmack.html