mailaddr(7) [centos man page]

MAILADDR(7)							Linux User's Manual						       MAILADDR(7)

NAME

       mailaddr - mail addressing description

DESCRIPTION

       This manual page gives a brief introduction to SMTP mail addresses, as used on the Internet.  These addresses are in the general format

	    user@domain

       where a domain is a hierarchical dot-separated list of subdomains.  These examples are valid forms of the same address:

	    eric@monet.berkeley.edu
	    Eric Allman <eric@monet.berkeley.edu>
	    eric@monet.berkeley.edu (Eric Allman)

       The domain part ("monet.berkeley.edu") is a mail-accepting domain.  It can be a host and in the past it usually was, but it doesn't have to
       be.  The domain part is not case sensitive.

       The local part ("eric") is often a username, but its meaning is defined by the local software.  Sometimes it is	case  sensitive,  although
       that is unusual.  If you see a local-part that looks like garbage, it is usually because of a gateway between an internal e-mail system and
       the net, here are some examples:

	    "surname/admd=telemail/c=us/o=hp/prmd=hp"@some.where
	    USER%SOMETHING@some.where
	    machine!machine!name@some.where
	    I2461572@some.where

       (These are, respectively, an X.400 gateway, a gateway to an arbitrary internal mail system that lacks  proper  internet	support,  an  UUCP
       gateway, and the last one is just boring username policy.)

       The  real-name  part  ("Eric Allman") can either be placed before <>, or in () at the end.  (Strictly speaking the two aren't the same, but
       the difference is beyond the scope of this page.)  The name may have to be quoted using "", for example, if it contains ".":

	    "Eric P. Allman" <eric@monet.berkeley.edu>

   Abbreviation.
       Many mail systems let users abbreviate the domain name.	For instance, users at berkeley.edu may get away with "eric@monet" to send mail to
       Eric Allman.  This behavior is deprecated.  Sometimes it works, but you should not depend on it.

   Route-addrs.
       In  the	past,  sometimes  one had to route a message through several hosts to get it to its final destination.	Addresses which show these
       relays are termed "route-addrs".  These use the syntax:

	    <@hosta,@hostb:user@hostc>

       This specifies that the message should be sent to hosta, from there to hostb, and finally to hostc.  Many hosts disregard  route-addrs  and
       send directly to hostc.

       Route-addrs  are very unusual now.  They occur sometimes in old mail archives.  It is generally possible to ignore all but the "user@hostc"
       part of the address to determine the actual address.

   Postmaster.
       Every site is required to have a user or user alias designated "postmaster" to which problems with the mail system may be  addressed.   The
       "postmaster" address is not case sensitive.

FILES

       /etc/aliases
       ~/.forward

SEE ALSO

       binmail(1), mail(1), mconnect(1), aliases(5), forward(5), sendmail(8), vrfy(8)

       RFC 2822 (Internet Message Format)

COLOPHON

       This  page is part of release 3.53 of the Linux man-pages project.  A description of the project, and information about reporting bugs, can
       be found at http://www.kernel.org/doc/man-pages/.

4.2 Berkeley Distribution					    2004-09-15							       MAILADDR(7)

mailaddr(7)						 Miscellaneous Information Manual					       mailaddr(7)

Name
       mailaddr - mail addressing description

Description
       Mail  addresses	are  based on the ARPANET protocol listed in the SEE ALSO section of this reference page.  In addition, the DECnet address
       format can be used, if DECnet is installed on your system.

       To send mail to DECnet users, use the following address format:
       nodename::username
       In this case, nodename is the name of the DECnet system, or host, on which the target user resides.

       Addresses based on the ARPANET protocol use the following general format:
       user@domain
       A domain is a hierarchical dot-separated list of subdomains.  For example, the following address is interpreted from right to left:
       eric@monet.Berkeley.ARPA
       In the previous example, the message is directed to the ARPA name tables (which do not correspond exactly to the  physical  ARPANET).   The
       message then proceeds to the Berkeley gateway, after which it is directed to the local host When the message reaches it is delivered to the
       user

       Unlike some other forms of addressing, this does not imply any routing.	Thus, an address that is specified as an ARPA address  can  travel
       by an alternate route if that route is more convenient or efficient.  For example, from Berkeley, the message could go directly to over the
       Ethernet, rather than using the Berkeley ARPANET gateway.

       Abbreviations.  In some instances, you do not have to type an entire domain name.  Generally, any information that follows  the	first  dot
       may  be	omitted  if the sending and receiving domains are the same.  For example, a user on calder.Berkeley.ARPA can eliminate the .Berke-
       ley.ARPA when sending to eric@monet, because the sending and receiving hosts are the same.

       Other abbreviations are permitted when conflicts do not exist.  For example, Berkeley ARPANET hosts can	be  accessed  without  adding  the
       .ARPA, if their names do not conflict with a local host name.

       Compatible  Addresses.	To  provide compatibility with the previous mail system, some old address formats are converted to the new format.
       In particular, host::user is converted to user@host providing consistency with the command.

       The syntax host!user is converted to user@host.UUCP.  Before being sent on, user@host.UUCP is normally  converted  back	to  the  host!user
       form. This conversion is done for compatibility with older UUCP hosts.

       The  current  implementation  cannot automatically route messages through the UUCP network.  Thus, you must explicitly tell the mail system
       all the hosts your messages must be sent through to arrive at its final destination.

       Case Distinctions.  Domain names (that is, anything following the at sign (@)) can be a combination of upper- and lowercase characters with
       the exception of UUCP hostnames.  Most hosts accept both upper- and lowercase in user names, with the exception of MULTICS sites.

       Differences  with  ARPA Protocols.  Although the UNIX addressing scheme is based on the ARPA mail addressing protocols, there are some sig-
       nificant differences.

       Currently, the only top level domain defined by ARPA is the .ARPA domain itself.  This is further restricted to having only  one  level	of
       host  specifier.   That	is, the addresses that ARPA accepts must be in the format user@host.ARPA (where `host' is one word).  For example,
       the following address is not legal under the ARPA protocols:
       eric@monet.Berkeley.ARPA
       Thus, the previous address would be converted to a different format on output to the ARPANET.  For example:
       eric%monet@Berkeley.ARPA
       Route-addrs.  In some instances, a message must be routed through several hosts to reach its final destination.	Usually,  this	action	is
       invisible  to  the  sender;  however,  it is sometimes desirable to route a message manually.  Addresses that are moved manually are called
       route-addrs.  The syntax is as follows:
       <@hosta,@hostb:user@hostc>
       The previous example directs the message to hosta, to hostb, and finally to hostc.  This route is used regardless of a more efficient  path
       to hostc.

       Route-addrs  occur  frequently  on  return addresses, because they are generally augmented by the software at each host.  It is possible to
       ignore all but the user@host part of the address to determine the actual sender.

       Postmaster.  Every site must have a user or user alias designated as postmaster to which problems with the mail system can be addressed.

       CSNET.  To send messages to CSNET, use the following syntax:
       user.host@UDel-Relay

See Also
       mail(1), sendmail(8)
       Crocker, D. H., Standard for the Format of Arpa Internet Text Messages, RFC822

																       mailaddr(7)