Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!batcomputer!itsgw!steinmetz!uunet!tiamat!jim
From: jim@tiamat.fsc.com (Jim O'Connor)
Newsgroups: comp.mail.elm
Subject: Re: group reply includes sender
Summary: apparently, it's smail2.5 that's not fully RFC822 compliant
Message-ID: <395@tiamat.fsc.com>
Date: 19 Feb 89 20:56:40 GMT
References: <290@wubios.wustl.edu> <937@csd4.milw.wisc.edu> <4726@pbhyf.PacBell.COM>
Organization: Filtration Sciences Corp., Chattanooga, TN
Lines: 31

In article <4726@pbhyf.PacBell.COM>, rob@pbhyf.PacBell.COM (Rob Bernardo) writes:
> In article <5121@b-tech.ann-arbor.mi.us> zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) writes:
> +
> +Elm does needs an option to fully qualify all addresses.  People using
> +elm + smail 2.5 have problems with mail going out with things like "Cc: jon"
> +which confuses some sites.

I came across this, before installing elm, when switching from smail2.5 to 
smail3.  Headers which looked like "To: jim" under smail2.5 were suddenly
showing up as "To: jim@fsc2086.fsc.com" under smail3.  Since "jim" was getting
mapped to "jim@tiamat.fsc.com" in the alias file, I wasn't sure I liked this.
But as the smail3 author pointed out to me, smail3 was doing this correctly,
according to RFC822.  Apparently, it's smail2.5 that is not being fully
compatible by not qualifying any address that has not already been
qualified.

> If I understand you correctly, I don't think that would work.
> 
> It seems to me that if smail 2.5 has it's own alias database and it
> translates the address "jon" into something more universally meaningful,
> it is up the smail to rewrite the headers of the message as well.

Even if "jon" isn't mapped to some other address, as I understand it, it is the
responsibility of the delivery agent to fully qualify all addresses.  smail3
performs that function very well.

------------- 
James B. O'Connor			jim@tiamat.fsc.com
Filtration Sciences Corporation		615/821-4022 x. 651

*** Altos users unite! mail to "info-altos-request@tiamat.fsc.com" ***