The World of Computer Software/World_Of_Computer_Software-02-387-Vol-3of3.iso/t/toadkit.z36/UUCPGATE.HOW

Text File | 1992-08-14 | 16KB | 309 lines

               Use of the UUCP <===> Toadnet Gateway

           cheswicks.toadnet.org <===> 86:86/[e-mail]

                -=Netmail=- to Internet and Back again!

  I) To send mail FROM a Toadnet <==> UUCP Gateway TO some one on a UUCP
     (or Internet) site.

     A) What you must know

        1) The site name of the UUCP node the user is on.

        2) The login name or mail alias (the mailbox name) that the
           user you want to send to uses there.

        3) The path to the system the recipient is on *if that machine
           is not in the UUCP maps.* It is assumed that the UFGATE site
           is sending mail to a "smart" UUCP node which knows how to
           get mail to all other registered UUCP nodes. Or the domain
           ("at style") name of the recepient's system.


         You should get the first two pieces of information from the
        person that you want to send mail to and the third one should
        be given to you either by the Sysop of the Gateway you are
        using OR by the person you are sending mail to. In this
        documentation we will use  Toadnet's Gateway of Cheswick's
        (86:86/200), also known as cheswicks.toadnet.org.

          As an example, let's say you want to send mail to Lisa
        Gronke. She has an account on wustl and her login there is
        gronke. Let's also say that you want to send this mail from
        Cheswick's  (Toadnet 86:8012/3). Cheswick's UUCP/USENET Host is
        wugate.wustl.edu. (Washington U. St. Louis)

     B) With these bits of information do the following steps

        1) Go to the Net-Mail area on whatever bbs you are using.

        2) Enter a message to node 86:86/200 (that's Cheswick's Toadnet
           Gateway address).

        3) If the system asks you if you want the message to be killed
           after sending, PLEASE say yes.

        4) Address the message to UUCP. The line prior to the body of
           the message will probably look like:
           From: yourname
           To: uucp,86:86/200 Toadnet <=> UUCP Gateway.
           Re: whatever the topic is
           ----------------------------------------------------------



        5) As the very FIRST line of your message you must enter a
           special line that will tell the gateway software how to send
           the message.  This is the To: line and for the example above
           it would look like this: "To: [e-mail]" (without
           the quotes). The actual path is "wugate.wustl.edu.gronke" and
           "To: " is a keyword that MUST be there as shown or the
           Gateway won't process the message. You could also use the
           path "wugate!gronke" if you are on a system that handles
           smart paths. If you are not sure, try the short path first,
           and if that fails try again with the entire path.

           Our message now looks like:

           From: yourname
           To: uucp,86:86/200 Toadnet <=> UUCP Gateway.
           Re: whatever the topic is
           ----------------------------------------------------------
           To: [e-mail]


        6) Enter the rest of your message as you normally would. When
           you're finished, save it and it will be sent to your friend
           automagically.


        An example mail sending session, based on the previous examples,
        follows:


 II) To send mail from a UUCP Site TO a user that calls a Toadnet
     system.

  IIa) The "smart" way, or RFC822 @ style.

        If the gateway site has a registered map entry, and you send
        mail from or to a "smart" mail site, use these steps instead.
        They are also the steps to use for sending mail from the
        Internet to FidoNet. Note that this is the "smart" way because
        you don't have to provide routing information - how to get the
        mail to its intended recipient is figured out by the system.
        *You should never mix ! and @ addressing, unpredictable results
        _will_ occur!!!!*

     A) The address of a Toadnet looks like this: 86:8012/2.0. Usually
        the 86: and .0 are left off, but they are there by default.
        That address can be translated as "Zone 86, Net 8012, Toadnet
        Node 2, Point 0." or p0.f2.n8012.z86. Add the Toadnet domain of
        .toadnet.org to the end of that, chop off the p0 (it is again, a
        default) and you have f2.n8012.z86.toadnet.org - the "Fully
        Qualified Domain Name" of a Toadnet Node. Another example is
        86:8105/4.3 which would be written as p3.f4.n8105.z86.toadnet.org
        (since there is a point number other than 0, we have to specify
        it). Note also that we are only using zone 86.

     B) So, lets say you wanted to send mail to Allen Sandifer at
        86:8012/2, you would address your letter to
        [e-mail] and you shouldn't have to
        worry about it from there. Note that this address will most
        likely work on the Internet. This address will be automaticly
        interpreted and routed via the correct gateway, so you won't
        have to specify any paths. All you need to know is the Toadnet
        address and logonid of the person you are trying to reach.


     C) If you are using a system that just insists on ! paths only,
        you can use the address f2.n8012.z86.toadnet.org!allen.sandifer
        *if* you have your mail routed via a "smart" mail site. If you
        don't, you will have to give enough path to get from where you
        are to cheswicks, then ! on from there. As the entire UUCP net is
        in a state of transition from the ! paths to the @ paths, this
        will be a problem for a while. Again I state: *You should never
        mix ! and @ addressing, unpredictable results _will_ occur!!!!*


III) Other features of the UUCP Gateway software (UFGATE)

     A) User Alias
        If you are sending and/or receiving a large volume of mail
        to/from UUCP sites then you may want to ask your UFGATE site
        Sysop to set up a UUCP alias for you. This is especially
        helpful if you have a long and/or difficult to spell name.
        It's easier to remember a six or seven letter name (this is
        what UUCP people are used to also) than a full name which may
        NOT be easy to remember. The UFGATE software on the UFGATE site
        node will handle all the translations automatically.

     B) Out of area mail forwarding
        If you are on a UUCP system, you may want to arrange for full
        mail forwarding to all of Toadnet. This will cost you some
        money for the messages to be sent outside your local area, but
        may be worth the cost. Contact your local UFGATE site for
        further details.

IV) Things to consider:

        As with sending mail to any UUCP or Internet site, some or all
        of this may not apply to your site. If you know that it won't
        work you can route mail to another site that you know will use
        the addresses correctly, and hope for the best.

        Mail from a Toadnet node to another Toadnet node can't be sent
        in this way. We (being Toadnet) still have to pay our own way.

        The Domain of toadnet.org only includes those nodes listed in
        the official FidoNet nodelist as published by 86:86/2 or their
        designated deputy. It does not include any other networks
        that may use the FidoNet protocols to communicate.

        The Internet can not be used for profit. Mail sent via this
        system that gets routed to ARPANET, MILNET, NSFnet, etc, can
        not contain advertisements, sales literature, or other
        profit-making "things" unless in a direct reply to a query from
        an ARPANET or MILNET site that is working on a grant from DARPA
        or other authorized government agency.

V) Glossary:

        ARPA style address: an address of the form "user@system" or
        user@domain. It is considered archaic to make the user rather
        than the computer route mail. Many UUCP systems now have "smart
        mailers" that can handle ARPA style addresses in addition to
        the traditional UUCP "bang paths". See the document on Internet
        addressing for a more complete description. This is also called
        "at sign syntax." The latter form, user@domain, is known as
        domain addressing.  The particular kind is ARPA Internet domain
        addressing, or RFC973 domain addressing.  There are others, for
        example that used in JANET, the British national research
        network.

        ARPANET: The Defense Advanced Research Projects Agency
        Network.  A major portion of the Internet. Soon to be replaced
        by the DRI (Defense Research Internet).

        At sign syntax: See "ARPA style address."

        BANG PATH: A UUCP node connects to only a limited number of
        other UUCP nodes. The bang path is the series of nodes the mail
        will pass through to reach the remote user. The node names are
        separated by exclamation marks (nicknamed "bangs"). The first
        node in the path must be a "link" on the local system, the
        second node must be linked to the first, etc. etc. The last
        name in the path is the user name on the remote system. The
        bang path must not contain any spaces and is usually all lower
        case.

        Internet:  The Internet is a set of networks all running the
        TCP/IP protocols, sharing the same underlying network address
        space as well as the same name space, and interconnected into
        an internet.  BITNET, UUCP, and JANET are not part of this
        internet because they don't use the same protocols.  They are
        only interconnected for mail.  This makes the combination of
        their interconnections of that kind what many people call a
        metanetwork.

        internet: (with a little i) is any old internet.  The Internet,
        with definite article and capital I, is a specific Internet,
        usually the one we are referring to above, whose proper name is
        the ARPA Internet.  There are others, such as the XEROX
        Internet.  There are also other TCP/IP internets.

        Toadnet: a network of systems that use the FidoNet protocol to
        transfer FidoNet (Matrix) mail and other things (EchoMail,
        files).  Most of the Toadnet nodes are BBS running software
        under MS-DOS. A Toadnet address is usually of the form
        zone:net/fidonode (eg 86:8012/2). Toadnet routing is theoretically
        direct ... node 86:8012/2 dials up node 86:8401/1 and transfers
        mail addressed to users at the destination system. Toadnet
        (Matrix) mail is usually free to the user when sent to a node in
        the SAME net and requires that the user have funds on deposit
        when sent to a node in a DIFFERENT net. Toadnet Netmail users
        mostly use their real name (eg Lisa Gronke).

        GATEWAY: a system that is a node in two (or more) networks.
        The two networks may use the same protocol or different
        protocols. The gateway has a name/address in EACH network and
        has to be running an implementation of each protocol. A
        gateway, sensu strictu, should forward material received from
        one network to addressees in the other network.

        MAIL: electronic text, typically private, addressed to a
        specific person. FidoNet calls this function "FidoNet (Matrix)
        mail". Not all Toadnet nodes offer the function to users. UUCP
        calls this function "mail". In both Toadnet and UUCP, mail can
        be sent to a user on the same node OR to a user on a remote
        node. Mail is distinguished from "broadcast messages" which are
        called "EchoMail" on FidoNet systems and "USENET News" on UUCP
        systems.

        MILNET: A specific military network within the Internet.

        NETWORK: a group of computers that communicate using the SAME
        protocol. A network is a real entity with a name, history,
        administration, financing and addressing/routing scheme in
        addition to the protocol.

        NODE: a {computer, machine, system, BBS} that is part of a
        network is often called a node or a site.

        NSFnet: National Science Foundation Network. Another part of
        the Internet. An internet in itself.

        PROTOCOL: the set of rules by which two computers communicate.
        Users do not need to know anything but the NAME of the protocol
        but should distinguish between the name of a PROTOCOL and the
        name of NETWORK that uses the protocol. We are concerned here
        with two protocols: the FidoNet protocol and the UUCP (Unix to
        Unix CoPy) protocol. Each protocol is historically associated
        with a certain {computer, operating system} but CAN be
        implemented on just about any hardware.  To complete your
        confusion, the PROGRAM that IMPLEMENTS a specific protocol on a
        particular computer sometimes also has the same name. And to
        make things even more fun, sometimes a network built out of the
        protocol is named after it, as with the UUCP network.

        SMART MAILER: Mailing program(s) that know(s) how to route
        messages to other UUCP/Internet nodes. They use maps compiled
        by the UUCP project to route mail more intelligently, meaning
        the user often doesn't have to provide a route. SMail and
        Sendmail are programs that are smart mailers. Many UUCP sites
        have them, or know how to send mail to a site that runs one.

        UFGATE: A collection of software written by Tim Pozar, Garry
        Paxinos and John Galvin that allow Fido compatible BBSs to
        exchange UUCP mail with other UUCP sites. Also included are
        programs for the processing of Netnews - UUCP's older-brother
        equivalent to EchoMail.

        UFGATE site: A Toadnet node that is running the UFGATE software
        (or any other software that emulates the UFGATE system).

        USENET: The combined group of systems (a network as it were)
        that share Netnews with each other. It uses UUCP and other
        protocols for transmitting news between machines. It is not
        limited only to the UUCP network or the Internet.

        UUCP: Unix-Unix-CoPy. A protocol set for transferring files over
        dialup lines. It is also the name of a network much like
        FidoNet.  (Only much bigger, and older.)

        UUCP Network: the network of systems that use the UUCP protocol
        to transfer mail and other things (USENET news, files). [
        "USENET network" is sometimes incorrectly used as a synonym but
        specifically refers to the subset of UUCP, Internet, Bitnet,
        etc. nodes that subscribe to USENET news.] Most of the UUCP
        nodes are unix minicomputers at universities or high-tech
        companies. A UUCP node has a cryptic name (eg bucket). UUCP
        routing is "store and forward" whereby the mail is passed from
        system to system until it reaches its destination. Classic UUCP
        address are "bang paths" from the originating node to the
        destination node (eg reed!percival!bucket!lisag). UUCP mail is
        almost always free to the user. UUCP users use a one word alias
        name (eg lisag).