Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!cs.utexas.edu!uunet!mcvax!unido!isaak!woerz
From: woerz%isaak@isaak.uucp (Dieter Woerz)
Newsgroups: comp.mail.elm
Subject: Re: System aliases
Message-ID: <1023@isaak.UUCP>
Date: 27 Jul 89 23:32:24 GMT
References: <509@wubios.wustl.edu> <177@van-bc.UUCP>
Sender: news@isaak.UUCP
Reply-To: woerz@isaak.UUCP (Dieter Woerz)
Followup-To: comp.mail.elm
Organization: ISA GmbH, Stuttgart, West-Germany
Lines: 38

In article <177@van-bc.UUCP> skl@van-bc.UUCP (Samuel Lam) writes:
>In article <509@wubios.wustl.edu>, phil@wubios.UUCP (J. Philip Miller) wrote:
>>[about system aliases being replaced by the senders's personal
>> aliases with the same name]

>That shouldn't be necessary, since page 3 of the Elm Alias System Users
>Guide says "The major limitation with group aliases is that each of the
>people in the list must be a previously defined alias or a valid mail
>address on the current machine".                     >**<
>
>Listing each local user's mailbox's name in the group's membership
>list should do the job.

There is still a problem. Asume you have the following system alias
file:
    ...
    allusers =  All users of this host  =   a, b, c, d, e, f
    ....

and the sender of the message has the following in his personal
aliases file:
    ...
    c = ... =   c@x.y.z

Then the c@x.y.z get the message that should have reached c on the
local machine.

I don't know about other possible solutions except using some other
alias mechanism (e.g. within sendmail).

>...Sam
>-- 
>Samuel Lam     {alberta,watmath,uw-beaver,cs.ubc.ca}!ubc-cs!van-bc!skl

Dieter Woerz
ISA GmbH, Azenbergstr. 35 D-7000 Stuttgart-1 W-Germany
UUCP:           {pyramid!iaoobel,uunet!unido}!isaak!woerz
BITNET/EARN:    woerz@ds0iff5