🚀 go-pugleaf

In article <1992Oct15.184319.38325@slate.mines.colorado.edu>  
cartley@slate.mines.colorado.edu (Craig Artley) writes:
> In article <1992Oct13.220907.40827@slate.mines.colorado.edu>  
cartley@slate.mines.colorado.edu (Craig Artley) writes:
> >If I send mail to the outside world from one of the mail clients,
> >shouldn't it still appear to be from cartley@"mailhost", rather than
> >cartley@"client"?  The reason I ask is that the name of the mailhost is
> >likely to be a permanent feature, while some of the clients may be only
> >temporary (due to name changes, network changes, etc.).  Therefore, I
> >would prefer that outgoing mail contains the name of the permanent
> >mailhost rather than the client.
> >
> >I suspect that this would be an easy thing to do with the sendmail
> >configuration file.  Does anyone know how to do it?

I took a look at this a while ago (on 2.2), but never tested the idea.  I  
believe that (with some NetInfo trickery) you can persuade a normal mail  
system (mailhost + clients) to do this.  The problem is, that if a mail  
client finds a remote site in the NetInfo hosts table, the default  
sendmail files will send the mail point to point, bypassing mailhost.   
However, if the site is unknown to NetInfo, it will be forwarded to the  
mailhost.

So, if this (untested) theory is true, define remote sites only in the  
mailhosts local domain.  If you need the site defined in the global domain  
for any reason (ftp, telnet) then use a different name that you won't unse  
in a mail address.

If this is correct, it should be easy to test.  And if so, what does it  
tell you about NeXT's internal mail setup?

Paul
-- 
Paul Lynch
P & L Systems                   (NeXTmail) paul@seer.demon.co.uk
Tel: (0494)671501                      paull@cix.compulink.co.uk
Fax: (0494)680228                       76711.451@compuserve.com