1 Internet

 VMS MAIL on this system may be used to send and receive mail to the 
 worldwide uucp (uucp to uucp copy) and Internet networks, and to other 
 networks gatewayed to them.  See the UUCP topic for more details. 

1 UUCP

 VMS MAIL on this system may be used to send and receive mail to the 
 worldwide uucp (uucp to uucp copy) and Internet networks, and to other 
 networks gatewayed to them.  

2 Sending_Mail

 Users on uucp and Internet sites generally have addresses of the form

	username@systemname

 where "systemname" is usually (but not always) a series of names separated 
 by dots, e.g.

	jeh@crash.cts.com

 To send mail to such an address, use VMS MAIL in the usual way, but answer
 the "To:" prompt with an entry of the form UUCP%"username@systemname".
 For example, 

	MAIL> SEND
	To: UUCP%"jeh@crash.cts.com"
	Subject: this is a test

 This format is specific, and the quotes must be used exactly as
 shown in the examples.  A missing trailing quote will cause VMSmail 
 to exit with an error message (earlier versions would simply hang;
 type ctrl-Y to escape).  

 Some uucp users have "bang form" addresses which consist of a series of
 uucp hostnames, separated by !'s (which are pronounced "bang" when reading
 such addresses aloud), with their username at the end, as in 

	decwrl!simpact!jeh

 These addresses may also be used, as follows:

	MAIL> SEND
	To: UUCP%"decwrl!simpact!jeh"
	Subject: this is a test

 See the "Addressing" topic for information on more complex addresses.

2 Receiving_Mail

 To tell people how to send mail to you, you will have to give them your
 network address.  In the Internet address form

	user@system

 the "user" part is simply your VMS username.  The "system" part is, 
 however, *not* the local DECnet nodename (at least not usually).  

 To find out your system's name in Internet terms, issue the following 
 command from the DCL prompt:

	$ SHOW LOGICAL UUCP_DOMAIN_NAME

 The translation of this logical name is your system's name from the 
 Internet's point of view.  Thus, if this name translates to the string 

	crash.cts.com

 (it won't, because that name is already in use, but never mind; this is 
 just an example), and your user name is JSMITH, your network address is

	jsmith@crash.cts.com

 When you send network mail, you usually want your recipient to be able 
 to reply to you.  The uucp mailer will automatically precede your 
 message with an Internet-compatible "From:" line that shows your address; 
 this will usually allow replies to work correctly.  However, some network 
 "gateways" modify the "From" information in such a way as to make the 
 mail unreplyable.  It is therefore advisable to include your network 
 address in the text of your message (usually as part of your "signature"; 
 see the entry for "Signatures").

2 More_on_Addressing

 For most Internet sites, anywhere that VMSmail asks for an address, you can
 respond with 

        UUCP%"user@site"

 where site is usually something like machine.organization.domain,
 but may be as simple as a uucp host name, and user is a username on 
 that system.

 A series of uucp addresses may be used, separated by commas, and possibly
 mixed with local and remote (reached via DECNet) user names, as follows:

	MAIL> SEND
	To: UUCP%"jeh@crash.cts.com",UUCP%"ta2@esther",LABVAX::SYSTEM
	Subject: this is a test

 Under VMS Version 5, uucp addresses may also be used in response to the CC:
 prompt.

 If someone gives you an address like

	remhost!user

 you can generally use a VMSmail "To:" address of

       	UUCP%"user@remhost"

 If you get something in the more complex form shown previously,

 	well-known-host!intermediate-host!...!...!theirhost!user

 you can try sending to UUCP%"user@theirhost" first; if that
 doesn't work, just wrap UUCP%"..." around the whole mess.  You
 needn't worry about how to get to well-known-host:  If it's
 well-known it'll be in the maps, and the mailer will figure out
 the path from your system.

 If your addressee has given you an address like

 	{wkh1, wkh2, wkh3}!theirhost!user

 you cannot pass this to Mail directly.  What they are telling you is
 that each of the systems wkh1, wkh2, and wkh3 talk to theirhost, but
 you are supposed to figure out how to get to one of the "well-known-
 hosts" mentioned (your choice as to which).  So try something like

       	UUCP%"wkh2!theirhost!user"

 The aforementioned techniques will often fail for @-form addresses when
 networks other than uucp or Internet are involved (and sometimes
 even then).  This is particularly true of Bitnet, which uses
 Internet-style addresses and otherwise looks like part of the
 Internet, but isn't really.

 The general solution is to "send the mail through a gateway".  A
 later version of this document will expound upon the
 possibilities.  For now, refer to the files in [.DOC.ADDRESSING],
 which are mostly a collection of questions and answers on these
 issues that have appeared on the net.  If you do not have access
 to these files (or don't know exactly where they are), contact your
 uucp system manager.

3 Percent_Signs

 Many addresses include imbedded percent signs; for example:

       	TNIELAND%FALCON@AAMRL.AF.MIL

 There are differences of opinion as to how this should be
 interpreted.  In general it usually is interpreted with
 everything to the left of the "@" as being a "funny username", so
 the mail is sent to

       	TNEILAND%FALCON   at   AAMRL.AF.MIL

 on the assumption that aamrl.af.mil will know what to do with it.
 (In this particular case, they do.)

 Troubles may arise when addresses of this form are handed to uucp
 (any uucp, not just ours).  For uucp transmission we must convert
 everything to bang-path notation, so we end up with something
 like

       	neighbor!...!AAMRL.AF.MIL!TNEILAND%FALCON

 This works fine when I send mail to this address (actually I send
 to UUCP%"TNIELAND%FALCON@AAMRL.AF.MIL"), but Tom Allebrandi's
 uucp "neighbor" hates to see !'s and %'s in the same address, and
 either bounces it as undeliverable or does horrible things to it.
 Tom gets around this by converting the % to a !  himself, sending
 to

        UUCP%"FALCON!TNEILAND@AAMRL.AF.MIL"

 This workaround succeeds in this particular case because aamrl
 knows to handle falcon!tneiland just as it would handle
 tneiland%falcon.  In the general case, success depends on the
 capabilities of the target Internet host.  The entry on "mixed_addresses"
 discusses addresses of this form in more detail.

3 Mixed_Addresses

 Sometimes you will see an address of the form

       	uuhost!user@inethost.company.com

 Such an address, combining "!" and "@" notation (with maybe some
 "%"s thrown in for good measure), is referred to as a "mixed
 mode" address.  These addresses are often used by uucp sites
 (uuhost in this example) who do not have registered domain names,
 but have a uucp connection to a nearby host
 (inethost.company.com) who does.  In general more sites will know
 how to get to inethost.company.com than to uuhost, so they are
 trying to make it easy for people to send mail to them.

 If someone -- particularly someone on the Internet -- is having
 trouble sending mail to you, you might try telling them to use
 such an address.  For example, if you know of an Internet site
 (isite.dom.ain) that reaches you reliably via uucp, you might
 suggest that they try

       	yourhostname!you@isite.dom.ain

 meaning "send mail to isite.dom.ain, who will send it to
 yourhostname!you".

 Addresses of this form should not, in general, be published "at
 large" as your "standard" address, but only given out to
 individual correspondents to solve particular problems.  DECUS
 uucp will generally do the right thing when asked to send mail to
 an address like this, but this is not true of all other uucp
 systems.  This is because the interpretation of such an address
 as a mail destination varies depending on the machine sending the
 mail.

 Using the second example above:  If the machine from which mail
 is being sent to you understands "@"-signs (as DECUS uucp
 machines do), this address is equivalent to

        isite.dom.ain!yourhostname!you

 meaning "send it to isite.dom.ain, who will send it to
 yourhostname!you, which is what you want.  (In practice there
 will probably be some additional hosts in the bang-path prior to
 isite.dom.ain .)  But a "pure uucp" machine might send it this
 way:

        yourhostname!isite.dom.ain!you

 which is obviously wrong, since the pure uucp machine likely
 doesn't talk to yourhostname.  (If they do, they can just send to
 yourhostname!you and avoid all this bother.)  Even if the message
 does get to yourhostname, this address tells yourhostname to send
 it to isite.dom.ain, and you don't live there!

 So, in general, it is a bad idea to publicize addresses of this
 form.  If you want an "@" in your e-mail address, make sure your
 site is an Internet domain.  Contact your System Manager for
 assistance in finding out if your site has been set up in this manner.

2 Signature_files

 The majority of uucp users usually include a "signature" file at the
 end of their message.  This helps better identify the person sending
 the message.   Information included usually states the person's
 name, their company, their e-mail address, and possibly a phone number.

 This is usually done as a courtesy, so if someone wants to reply to
 your mail and can't, they can still reach you some way.

 This is done many ways in VMS mail, the simplest being creating a
 small "signature" file (say SIGNATURE.TXT), and using the /EDIT qualifier
 when sending mail.   Then, at the end of the message, use the editor
 INCLUDE command to add this text at the end of the message.

3 Examples

 Here are a few "signature" files.     There is no "format", you are
 free to do whatever you wish.  I include these only to help new users.

       This first example is my own.   I like to keep it simple, and
       I've chosen to include an amusing quote at the end....

 -------------------------------------------------------------------
 Kent C. Brodie - Systems Manager		brodie@mcw.edu
 Medical College of Wisconsin			+1 414 778 4500

 "Gee, I hope these are the right coordinates..." -Chief O' Brien; STTNG


      This second example belongs to Jamie Hanrahan (one of the co-authors
      of DECUS uucp).   Jamie provides more information than I do.

       --- Jamie Hanrahan, Simpact Associates, San Diego CA
 Chair, VMSnet and Internals Working Groups, DECUS VAX Sytems SIG 
 Internet:  jeh@simpact.com, or if that fails, jeh@crash.cts.com
 Uucp:  ...{crash,scubed,decwrl}!simpact!jeh

2 Logical_Names

 The uucp mailer recognizes the following logical name:

	UUCP_PERSONALNAME

 This logical may be equated to a string which the mailer will attach to 
 your address on outgoing mail.  If defined, this logical will override 
 the personal name you've defined within VMSmail; this allows you to have
 different personal names for network vs. local mail.  

 If the NEWS_PERSONALNAME logical is defined, the uucp mailer will use it
 in preference to UUCP_PERSONALNAME; therefore, if you've defined your 
 personal name for NEWS, you needn't define it again for uucp mail.  

2 NEWS

 The VMS uucp implementation supports "netnews", a worldwide conferencing
 system.  See your system manager for more information.  

2 Acknowledgements

 "DECUS uucp", as it is known, was developed by the VMSNET
 working group, which is a part of the DECUS organization.

 Although many people have done work on this package (and
 various utilities/parts of previous versions), the
 following three people organized their efforts to make this
 a complete package available to the general DECUS user
 community.   All three programmers involved would love to
 hear comments about their work!

 Jamie Hanrahan      Tom Allebrandi II             Mark Pizzolato
 Simpact Associates  Inland Steel, Inc.            Infocomm
 jeh@crash.cts.com   ta2@inland.com                uunet!lupine!infopiz!mark

 This HELP file was written by:

 Kent C. Brodie
 Medical College of Wisconsin
 brodie@mcw.edu

