Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!sdd.hp.com!think.com!snorkelwacker.mit.edu!bloom-beacon!dont-send-mail-to-path-lines
From: schaefer@cse.ogi.EDU (Barton E. Schaefer)
Newsgroups: comp.mail.mush
Subject: Re: alias name "/pathname"?
Message-ID: <9106142301.AA17119@cse.ogi.edu>
Date: 14 Jun 91 23:01:36 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: Z-Code Software Corp.
Lines: 25

On Jun 11, 11:10pm, Tim Cook wrote:
} Subject: alias name "/pathname"?
}
} >  alias name namelist         set "name" to the value of namelist
} > 
} > A "namelist" consists of one or more addresses.  An address may
} > be a name already set to another list, a valid user, a file or
} > a program.  Filenames must be full pathnames, i.e., they must
} > begin with a '/' (or with a ~, which expands to some home dir).
} 
} Have these last two features (where a name may be a file or program) been
} implemented?  I have tried setting up an alias that points to a file, which
} in turn contains a list of addresses, one per record, but mush does not
} send anything when I use the alias.  The copy it saves for me (because I
} have $record set), contains a blank "To:" header.

Setting the alias to a file doesn't read the namelist from the file,
it actually sends the message to that file.  The intent is to allow
mail sent to an alias to be recorded in a file specific to that alias,
different than the generic one named in $record.  So, yes, the features
have been implemented, but not in the way you interpreted the doc.

-- 
Bart Schaefer                                           schaefer@zipcode.com
Z-Code Software Corporation                             schaefer@cse.ogi.edu