Xref: utzoo comp.mail.misc:2916 comp.mail.sendmail:1355
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!jhunix!andy
From: andy@jhunix.HCF.JHU.EDU (Andy S Poling)
Newsgroups: comp.mail.misc,comp.mail.sendmail
Subject: Re: What is the most acceptable format for "firstname lastname" localpart?
Summary: first_last my choice
Message-ID: <4170@jhunix.HCF.JHU.EDU>
Date: 9 Feb 90 18:04:39 GMT
References: <8349@c3pe.UUCP>
Reply-To: andy@jhunix.UUCP (Andy S Poling)
Followup-To: comp.mail.misc
Distribution: usa
Organization: The Johns Hopkins University - HCF
Lines: 32

In article <8349@c3pe.UUCP> charles@c3pe.UUCP (charles Green) writes:
>I'm setting up a convenient name structure for users on one of our subdomains.
>For simplicity, I felt the easiest way to allow fullnames would be to have
>
>	firstname.lastname@sub.dom.ain
>
>look in /usr/lib/aliases to see what "firstname.lastname" mapped to.
>However, one of our 'sendmail' programs complains about me trying to alias
>"non-local" names when I run 'newaliases', while the other happily accepts
>the name and maps it as desired.

If the alias does not resolve to the "local" mailer, then sendmail will
complain about aliasing non-local names.


>So, I ask the net if there is an accepted "standard" for specifying full
>names in the localpart of an address.  Is it "first last"@dom.ain ?
>"first.last"@dom.ain ?  first_last@dom.ain?

This isn't an accepted standard, but I can guarantee that "first last@domain"
and "first.last@domain" will eventually cause problems.  "first_last@domain"
has never been a problem for me and is the method I've chosen to use to
express "fullname addresses".


-Andy

--
Andy Poling                              Internet: andy@gollum.hcf.jhu.edu
Network Services Group                   Bitnet: ANDY@JHUVMS
Homewood Academic Computing              Voice: (301)338-8096    
Johns Hopkins University                 UUCP: mimsy!aplcen!jhunix!gollum!andy