Stars of Shareware: DFÜ und Kommunikation/SOS-DFUE.ISO/programm/texte/internt2.txt

Text File | 1993-11-28 | 19.3 KB | 507 lines

    INTERNT2.TXT
    Created November 27, 1993
    By Benjamin S. Rockwell, Data-Lynx BBS
    Assisted by Shane Anderson, Side-Bar BBS
    19720 bytes total

===========================================================
===========================================================

TABLE OF CONTENTS

This table of contents refers to the actual line number, rather than the
page of a document.  I have done this, to allow for any type of computer
user, with any type of printer, to view this document.

    Introduction.............................    Line 40
    Acknowledgemnets.........................    Line 45
    INTERNET messages into FIDONET...........    Line 68
    FIDONET messages into INTERNET...........    Line 105
    FIDONET <---> COMPUSERVE.................    Line 165
    FIDONET <---> MCIMAIL....................    Line 196
    OTHER E-MAIL NETWORKS....................    Line 235
    NOTE TO ALL SYSOPS.......................    Line 252
    NOTE TO ALL READERS......................    Line 262
    SEARCHLIGHT BBS SPECIFIC INFORMATION.....    Line 280
    ARPANET.TXT..............................    Line 375
    COMPUSRV.TXT.............................    Line 394
    MCIMAIL.TXT..............................    Line 415
    OTHER AVAILABLE INTERNET RELATED FILES...    Line 437
    TO REACH THE AUTHOR......................    Line 486



===========================================================

===========================================================

This document covers the information needed to send messages between
Internet and FidoNet.  It also specializes on down to the usage of
Searchlight BBS and how to set up Searchlight for exporting these same
messages.

Special thanks to the following, without whom, I would still be struggling
to learn this information.  Without them, you would not have this text
file to read in front of you now.

    Shane Anderson (Co-Author and fellow SL Sysop)

    Wilma Morgel (A person devoted, seemingly, to helping all in need of
        computer assistance)

    Brian Heess (My Internet gateway, and question person)

    Christi Rockwell (My sister, without whom, I would never have the
        desire to send messages into the Internet)

    Daniel Prager (Another fellow SL Sysop helping out)




===========================================================

===========================================================

INTERNET messages into FIDONET

This is the easy part, so I shall cover that first!

My FidoNet address is 1:207/227, but for temporary purposes, let's assume
that it is 1:2/3.4.  An Internet location would address their message to
me as follows....

    [e-mail]

You simply read the FidoNet address backwards into the text, and leave
the p, f, n, z, all in there as shown.  It should be all lowercase, so
as to avoid confusion in the addressing.  My actual Internet address
is as follows....

    [e-mail]

Or even shorter, as the point portion of the address may be removed if
there is no point extension.  That would make my real address to be....

    [e-mail]

Just break the address down as shown.  The point portion of it may be
eliminated for brevity if it is non-existent.

My messages take about 2 1/2 to 3 days to come from the Gateway, and this
will differ according to some tricks that are available on the other side,
I am told.  Future revisions of this document will have more information
concerning this, I hope.




===========================================================

===========================================================

FIDONET messages into INTERNET

Running FidoNet is not as simple as the other way around, and can get
confusing.  There is no way to confirm that you are doing it right, other
than to have the person reply to you (as much as a week or so later!)

You must first determine your closest FidoNet <-> Internet gateway.  This
is done by searching the nodelist for the GUUCP nodelist flag.  Type the
following DOS command in, or use a good editor that can handle a file the
size of the nodelist.

FIND "GUUCP" NODELIST.330 > TRY.TXT

Again, the text that you are trying to find is "GUUCP".  It will be amongst
the other flags at the end of each line (such as CM, HST, V42, etc...).  I
copy this information over into another text file, as you can see, to allow
for faster reading.  Find an address as close as possible to you, and jot
it down.  I keep a backup address on hand in case of emergency.

I use FrontDoor, but most front end programs will allow for this sort of
message posting.  You go in, and you choose to create a message.  For the
To: portion of your message, you will type in UUCP.

Then your front end mailer will probably ask you what address to use.  At
this time, only put in the FidoNet address of your gateway.  You may place
anything in the remark field, but the following is crucial.

The message cannot be routed through any other FidoNet site.  I am told    that
the message will have changes made in the tossing structure, and will not
import properly over to Internet.  This will stop your message cold!

Furthermore, in the top line of the text for the message, you will want to
put the following information....

To: user@domain

Again, this must be in the very top line, or it will not work.  user@domain
is the Internet address.  For example, I send messages to my sister at
"[e-mail]" ....  This is her address, and is how she
receives her messages from me.  The address you use MUST be lowercase.  There
is no way to correct that on the way into the Internet, so type it similar to
how I have down below.

So, I actually put in the very first line....

To: [e-mail]

NOTE:  This address has been changed slightly.  Do not actually use this
address, but instead substitute another more appropriate one.

NOTE:  I always do the T in uppercase, and I think it matters, so just in
case, do it just like that!

You must then skip one line, and then type your message.

That's the basics of it.  Messages into Internet will take a matter of hours
after they arrive at the gateway.

===========================================================

FIDONET <---> Compuserve

If you wish to send messages into Compuserve, start just like you would
send into Internet, using the Internet gateway.  When you get to the
message, as before, you just enter a To: line, where you just enter the
address as below, substituting the correct address for the phony one below.
In this example, I am using an address of 71234,567.

To: [e-mail]

Note:    Compuserve account IDs are pairs of octal numbers.
    The ordinary consumer Compuserve user ID begins with a `7' as shown.

Again, this is identical to sending a message into Internet, but the address
is a little different.

The return message from Compuserve would be addressed as follows....

Send To: ">INTERNET:user@domain"

Or if going to me (for instance), the message address would be listed as
follows (ommitting the quotes)

">INTERNET:[e-mail]"

(Author's note:  The information on sending FROM Compuserve to FidoNet has
    not been verified yet, so syntax may be incorrect, use caution until
    this method has been verified by yourself, or by the Author)

===========================================================

FIDONET <---> MCI-Mail

MCI-Mail works similar to the Compuserve method, but there is additional
information involved.  Remember always, that an incorrect address will
not notify you.  Use care in guiding your messages.

For this example, I will use the name John Smith with an address of
(123-4567).

To: [e-mail]
   OR
To: [e-mail]
            (if "JSMITH" is unique)
   OR
To: [e-mail]
            (if "John Smith" is unique; note the "_")
   OR
To: John_Smith/[e-mail]
            (if "John Smith" is NOT unique)

This is the same as sending a message into Compuserve, or into the Internet,
but I must note that the addressing is different.

On the other side of the coin, the following information could be used
to send information to me from MCI-Mail.

At the "To:" prompt type "Benjamin Rockwell (EMS)"
At the "EMS:" prompt type "internet"
At the "Mbx:" prompt type "[e-mail]"

The basic addressing is the same, just has minor revisions on how to route
the message.

(Author's note:  The information on sending FROM MCI-Mail TO FidoNet has
    not been verified yet, so syntax may be incorrect, use caution until
    this method has been verified by yourself, or by the Author)

===========================================================

OTHER E-MAIL NETWORKS

The capabilities to send message to other networks from the Internet is also
possible.  I have another text file available for download (or FREQ) at my
BBS.  The name to use is INTADR.TXT (Magic name of INTADR)

INTADR.TXT also lists the routing to send messages the other way.  INTADR.TXT
was a resource used in the construction of this file, and may not be fully
current, or accurate.

The following major networks, at the time of creation of INTADR.TXT were not
available through accessing Internet.

American Online - Easylink - GEnie - PC-Relay - Prodigy

===========================================================

NOTE TO ALL SYSOPS

Something that is non-specific, and needs to be done on a software by
software basis is the dynamic routing of the messages.  I have it set up
so that all messages going to the gateway are sent directly there.  This
is something crucial, and must be handled this way.

===========================================================
===========================================================

NOTE TO ALL READERS

The next chapter is specifically for usage with Searchlight BBS, a popular
BBS program.  Following that, are some sample text instruction files for
BBS users to read as they are entering in a Netmail message.

I have also included information on reaching myself at the bottom of this
file.  There is also a list of other files that are available by calling,
or sending a File Request (FREQ) to my BBS.

Please send a comment to me, should you have any other ideas, or information
that you feel should be added to this article, or ZIP file.  We appreciate
your assitance in keeping this information current and complete.

===========================================================
===========================================================
===========================================================

Searchlight BBS specific information


From above, you should have already decided your choice for Gateway
over into the Internet.  This will be used in a moment.

Define a user in SLBBS, by logging in as NEW and registering the new
users name as UUCP.  This user should be given a low access, and should
expire either never, or at least a long distance into the future (I chose
12/31/99 as the expiration).

Once this user has an account, you need to set his netmail forwarding address
to the address of the gateway.  In my case, the user record under
2-Sysop/Option/Info looks like the following:

Enter Username : UUCP
Options:
 1. Location ...................... UUCP Gateway
 2. System Type ................... IBM<-->UNIX
 3. Phone No. .....................
 4. Password ...................... <not shown>
 5. Netmail Address ............... 1:102/851

The only important information here is the netmail address.  The other
information is only for reference purposes, and may be modified.  You will
want to use the address for your area, the one that we have mentioned before.

The usage of 1:102/851 is something available to you, however unless you are
in Los Angeles, California, there is most likely a closer, and possibly even
a local call to you.  There are locations spread throughout the United States,
and even some in Australia, France, and the United Kingdom.

Again, security cannot be stressed more, and the user's access level should
be quite low on your system.

You will want to also set up the following in your ALIAS.DEF file, as there
have been times on occasion where the message will come in as .UUCP, for
some really odd reason.  Just add the following line in....

.UUCP = UUCP

This will prevent any weird problems from occurring.

If you wish to get fancy, of course, we can go further!!!

You can set up an Internet E-Mail Command on the menu of your choice.  It
might look something like this:

                          E D I T   C O M M A N D

                      Press F1 to Change Command Type

 1. Command Name .................. Internet
 2. Command Key ................... I
 3. Description ................... Send Internet E-Mail
 4. Access Levels & Graphics [...]
 5. Command Number (1) ............    160
 6. Command Parameters (1) ........ @arpanet.txt
 7. Command Number (2) ............      3
 8. Command Parameters (2) ........
 9. Command Number (3) ............    131
10. Command Parameters (3) ........ /x /n /f /c UUCP
11. Command Number (4) ............      0
12. Command Parameters (4) ........

Now, what this says is the following:  show the information screen
@arpanet.txt - this has brief instructions on how to properly address
messages to the Internet.  If you make a Compuserve or MCI-Mail access
command as well, just substitute the appropriate filename and Command
Name and Key.

Then it says, send mail to the user UUCP, without pausing to verify the
address or anything else - it simply hard codes a message to the "user"
UUCP who has a netmail address of <whatever> your gateway node is...

With this file, I have also included some sample text files to use.  These
will cover the basics, and are not neccessarily inclusive.  If you feel
that there is a clearer way to present this information, please contact
me with your revised wording.

Please note that I have also enclosed a copy of my current .MNU file,
for you to use, and modify.

Something that is non-specific, and needs to be done on a software by
software basis is the dynamic routing of the messages.  I have it set up
so that all messages going to the gateway are sent directly there.  This
is something crucial, and must be handled this way.

THAT'S IT!  Really, that IS it.  When entering a message to UUCP, you need
to use the same convention as you do when sending from a front end mailer.
Again, that is to place the REAL address or "To:" line on the very first
text line of your message followed by two carriage returns.

===========================================================
===========================================================
ARPANET.TXT

On the very first line of your message, you need to type the address of
the Internet recipient of your message.  Using all lowercase letters, except
for the T in To:, you must enter the address absolutely correctly for it to
arrive properly.  You must hit the carriage return twice after the address,
so that the routing software is able to correctly identify the proper address
to use.

This is an example of an address to use.  This is not a real address.

To: [e-mail]

Translate the Internet address into the above line, and your message will
be sent properly.

Thank you.
===========================================================
===========================================================
COMPUSRV.TXT

On the very first line of your message, you need to type the following
information.

Type "To: " exactly like that, then the numerical address of the Compuserve
recipient of your message.  At the end of the numerical address, you must
then type "@compuserve.com".  You must hit the carriage return twice after
the address, so that the routing software is able to correctly identify
the proper address to use.

This is an example of an address to use.  This is not a real address.

To: [e-mail]

Translate the Compuserve numerical address into the above line, and your
message will be sent properly.

Thank you.
===========================================================
===========================================================
MCIMAIL.TXT

On the very first line of your message, you need to type the following
information.

Type "To: " exactly like that, then the numerical address of the MCI-Mail
recipient of your message.  At the end of the numerical address, you must
then type "@mcimail.com".  You must hit the carriage return twice after
the address, so that the routing software is able to correctly identify
the proper address to use.

This is an example of an address to use.  This is not a real address.

To: [e-mail]

Translate the MCI-Mail address into the above line, and your message will
be sent properly.  Please ask the Sysop for additional ways to address
this message to your MCI-Mail recipient.

Thank you.
===========================================================

LIST OF RELATED FILES AVAILABLE

Data-Lynx BBS has started a storage of Inter-Net related files.  These
files are available by FREQ, or by regular callers downloading.

        LIST OF INTERNET RELATED FILES
    ===================================================

        INTERNET.TXT - A how-to file for sending messages to
            Internet from a FidoNet location.

        INTERNT2.TXT - Combines INTERNET.TXT, ARPANET.TXT,
            COMPUSRV.TXT, MCIMAIL.TXT and OTHERFIL.ES into
            one file for release together, unzipped.

        ARPANET.TXT - A sample file to place up on your BBS
            with instructions for users on accessing Internet

        COMPUSRV.TXT - A sample file to place up on your BBS
            with instructions for users on accessing Compuserve

        MCIMAIL.TXT - A sample file to place up on your BBS
            with instructions for users on accessing MCI-Mail

        NETMAIL.MNU - Searchlight BBS sample menu

        INTADR.TXT - Accessing various E-Mail networks from Internet
            and vice versa.  Many of these methods will work
            the same way with the Fidonet, if used properly.

        UUCPTAG1.ZIP - A utility to enhance messages being sent
            to Internet automatically.  Will add a tag-line,
            and return message instructions.

        ACCESS.ZIP - Take a guided tour of the Internet

        FIDOUNIX.ZIP - Fido <-> Unix (Internet) FAQ

        INT_GUID.ZIP - Internet Mailing Guide v. 1.1

        ZEN10.ZIP - Zen and the Art of the Internet

        UUCP-RA.ZIP - Remote Access Mail Tosser.


===========================================================

===========================================================

TO REACH THE AUTHOR

If you have a problem with understanding any portion of this file, I may be
reached at the following locations....

FidoNet address...        1:207/227
Searchlight Address...        250:400/1496
Internet Address (as above!)...    [e-mail]

Shane Anderson is available for answering questions as well at the following
addresses....

FidoNet address....        1:102/819
Internet Address....        [e-mail]

Please send a comment to me, should you have any other ideas, or information
that you feel should be added to this article, or ZIP file.  We appreciate
your assitance in keeping this information current and complete.

===========================================================