1990. Mail through the Internet and grassroots services on free

bulletin boards (like FidoNet) is not included in their figure. The annual rate of increase in the number of messages is over 30% and increasing. If a given email service charges you US$30 per hour, it will cost you a meager US$0.075 to send one typewritten letter (size A- 4, or around 2,200 characters). See chapter 15 for a breakdown of this cost. If you live in Norway, and send the letter by ordinary mail to a recipient in Norway, postage alone is US$0.53 (1992). The cost is seven times higher than using email. To send the same letter from Norway to the United States by ordinary mail will cost 11 times more. This letter takes several days to reach the destination, while email messages arrive almost instantly. Often, you can send email messages to several recipients in one operation - without paying extra for the pleasure. Compare this to sending to several parties by fax! You do not have to buy envelopes and stamps, fold the sheet, put it into the envelope, and bring it to a mailbox. Just let the computer call your favorite email service to send the letter. The recipient does not have to sit by the computer waiting for your mail. Upon receipt, it will be automatically stored in his mailbox. He can read it when he has time. The recipient can print it locally, and it will be a perfect document, no different to one typed in locally. He can also make corrections or comments, and email onwards to a third party. In this way several people can work jointly on a report, and no time is it re-typed from scratch. When you receive several messages in the morning, you can very quickly create replies to them one at the time at your keyboard, and then send them in one go. No need to feed five different pieces of paper into a fax machine or envelopes for five different people. Where you can find a telephone, you can also read mail. In most countries, communicating through email is easy and economical. By the way, the simple but miraculous thing about email is that you can quote easily and exactly the point to which you are replying. This is a revolution in communication, no? How to send email? ------------------- This is what it normally takes for a CompuServe user to send me a message: Type GO MAIL to get to the "post office," and then type COMPOSE. "Start writing," says CompuServe. Type your message manually, or send a file (text or binary). Type /EXIT when done. "To whom?" asks CompuServe. You enter: "Odd de Presno 75755,1327," or just my mailbox number (75755,1327). CompuServe asks you to enter Subject. You type: "Hello, my friend!" Your message has been sent. A few seconds later, the message will arrive in my mailbox. If I am online to CompuServe at the moment, I will probably read it right away. If not, it will stay there until I get around to fetch it. Above, we used the term "normally takes to send." Please note that many users never ever TYPE these commands! They use various types of automatic software to handle the mechanics of sending and receiving mail (see Chapter 16). Other systems require different commands to send email. Ulrik at the University of Oslo (Norway) is a Unix system. So is The Well in San Francisco. On such systems, mail is normally sent using these commands: Type "mail [email protected]". When the computer asks for "Subject:," enter "Hello, my friend!" Type your message or send it. When done, enter a period (.) in the beginning of a line. Ulrik will reply with "Cc:" to allow you to 'carbon copy' the message to other people. If you don't want that, press ENTER and the message is on its way. While I wrote this book, I had to go to Japan. A simple command allowed me to redirect all incoming mail to CompuServe. As a result I could read and send mail by calling a local CompuServe number in several Japanese cities. Though the commands for sending email differ between systems, the principle is the same. All systems will ask you for an address and the text of your message. On some, the address is a code, on others a name (like ODD DE PRESNO). Most systems will ask for a Subject title. Many will allow you to send copies of the message to other recipients (Cc:). Some services allow you to send binary files as email. Binary files contain codes based on the binary numeration system. Such codes are used in computer programs, graphics pictures, compressed spreadsheets and text files, and sound files. Many online services let you send messages as fax (to over 15 million fax machines), telex (to over 1.8 million telex machines), and as ordinary paper mail. We have tested this successfully on CompuServe, MCI Mail and other services. On CompuServe, replace "Odd de Presno 75755,1327" with ">FAX: 4737027111". My fax number is +47 370 27111. On MCI Mail type "CREATE:". MCI asks for "To:," and you type "Odd de Presno (Fax)". MCI asks for "Country:". You enter "Norway". By "RECIPIENT FAX NO" enter "37027111" (the code for international calls). The country code for Norway, 01147, is added automatically. By "Options?," press ENTER. When MCI Mail asks for more recipients, press ENTER. Type your message and have it sent. To send a telex, you'll need the recipient's telex number, an answerback code, and the code of the recipient's country. If the message is meant for telex number 871161147, answerback ZETO, and country Russia (country code SU), enter ">TLX:871161147 ZETO SU" when sending from CompuServe. By entering ">POSTAL", CompuServe will send your mail to a business associate in California or Brazil as a professional laser- printed letter. It will take you through the process of filling out the various address lines. The letter may well arrive faster than through ordinary mail. When the recipient is using another mailbox system -------------------------------------------------- When the recipient is using your mailbox service, writing addresses is simple. Not so when your email has to be forwarded to mailboxes on other online services. The inter-system email address consists of a user name, a mailbox system code, and sometimes also routing information. The problem is that there is no universal addressing format. Finding out how to write a given address may be surprisingly difficult. Some services are not set up for exchange of email with other services. This is the case with my bulletin board, the Saltrod Horror Show. To send mail to a user of this system, you'll have to call it directly and enter it there. This bulletin board is not connected to the outside world for exchange of mail. If your favorite system lets you send mail to other services, make a note about the following: * You need to know the exact address of your recipient, and whether he's using this mailbox regularly. Many users have mailboxes that they use rarely or never. For example, don't try to send mail to my mailbox on Dow Jones/News Retrieval. I only use this service sporadically. Think of the easiest way for a recipient to respond before sending a message to him or her. * You need to know how to rewrite the recipient's address to fit your system. For example, you may have to use a domain address to send through Internet, and a different form when sending through an X.400 network. (More about this later.) * The recipient's mailbox system may be connected to a network that does not have a mail exchange agreement with your system's network(s). Sometimes, you can use a commercial mail relay service to get your message across (see chapter 9). Users of the Internet can send messages to recipients on the Dialcom network through the DASnet relay service. * Sometimes, you need to know how to route a message through other systems to arrive at its destination. For example, a message sent from the Ulrik computer in Oslo must be routed through a center in London to get to Dominique Christian on the Difer system in Paris (France), Internet -------- is the name of a computer network (here called "INTERNET"), and a term used of a global web of systems and networks that can exchange mail with each other (here called "Internet"). INTERNET is a very large network that has grown out of ARPANET, MILNET, and other American networks for research and education. This core network has many gateways to other systems, and it's when we include these systems and their connections that we call it the Internet. Others call it WorldNet or the Matrix. Internet users can exchange mail with users on networks like EUnet, JANET, Uninett, BITNET, UUCP, CompuServe, MCI Mail, EcoNet, PeaceNet, ConflicNet, GreenNet, Web, Pegasus, AppleLink, Alternex, Nicarao, FredsNaetet, UUNET, PSI, Usenet, FidoNet and many others. We therefore say that these networks are also "on the Internet." If you have access to the Internet, you can send email to users of online services all over the world. You can send to people using Bergen By Byte and Telemax in Norway, TWICS in Tokyo, and Colnet in Buenos Aires. Now is the time to take a closer look at the art of addressing mail through the Internet. Domain name addressing ---------------------- On the Internet, the general form of a person's email address is: [email protected] My main, international Internet mailbox address is: [email protected] You read the address from left to right. First, the local name of the mailbox (my name abbreviated). Next, the name of the mailbox system or another identification code (in this case EXTERN, to show that I have no affiliation with the University), the name of the institution or company (here UIO or "Universitetet i Oslo"), and finally the country (NO for Norway). People have sent mail to my mailbox from New Zealand, Zimbabwe, Guatemala, Peru, India, China, Greece, Iceland, and Armenia using this address. Some users must send their messages through a gateway to the Internet. In these cases, the address may have to be changed to reflect this: Users of AppleLink use [email protected]@INTERNET# . Those on JANET use opresno%[email protected]. On SprintMail, use ("RFC-822": , SITE:INTERNET) . CompuServe subscribers use >INTERNET:[email protected] . The core of these address formats is "[email protected]", in one way or the other. We call this basic addressing format a Domain Naming System. "EXTERN.UIO.NO" is a domain. The domain may also contain reference to the name of a company or an organization, like in twics.co.jp, compuserve.com, or IGC.ORG. The CO, COM, and ORG codes identify TWICS, CompuServe and IGC as companies/organizations. To send mail from the Internet to my CompuServe mailbox, use: [email protected] Normally (except on AppleLink), a domain address can only contain one @-character. When an address has to be extended with gateway routing information, replace all @-characters to the LEFT in the address by %-characters. Here is an example: BITNET uses a different addressing method (USER@SYSTEM). Let's assume that you are subscribed to the club for lovers of Japanese food ([email protected], see chapter 6). You have a mailbox on INTERNET, and want to send a recipe to the other members using the address J-FOOD-L. On some Internet systems, you can simply use the address: [email protected] , and your mailbox system will take care of the routing for you. If this addressing method doesn't work, you can use different gateways into BITNET depending on where you live. The preferred method is to route through a gateway near to you. If living in North America, you may route CUNYVM.CUNY.EDU using the following address: J-FOOD-L%[email protected] The rightmost @ in this address is maintained. The one to the LEFT has been replaced with a %. The term ".BITNET" tells the gateway machine where to forward the message. The following will happen: First, the message will be sent to system CUNYVM at the EDUcation site CUNY. CUNYVM investigates the address, and discovers that the message is for BITNET. It cuts off all text to the right of "JPNKNU10," and replaces the % with an @. The message is forwarded to the mailbox J-FOOD-L on the BITNET system JPNKNU10 at the Kinki University in Japan. Bang addressing --------------- "Bang" is American for "exclamation point" (!). The UUCP network uses this variation of the domain addressing scheme. Example: User Jill Small on Econet in San Francisco used to have the address pyramid!cdp!jsmall . Read this address from right to left. The name of her mailbox is to the right. The name of the organization is in the middle. "Pyramid" is the name of the network. Some email systems can use bang addresses directly. (Note that the ! character has a special function on Unix computers. Here, you may have to type the address as pyramid\!cdp\!jsmall to avoid unwanted error messages. The \ character tells Unix to regard the next character as a character, and not as a system command. This character may also have to precede other special characters.) Other systems do not accept bang addresses directly. Here, the users must send such messages through a gateway. The American host UUNET is a frequently used gateway. If routing through UUNET, you may write the address like this: [email protected] If your system absolutely refuses to accept exclamation points in addresses, try to turn the address into a typical Internet address. Write the address elements in the Internet sequence (left to right). Replace the exclamation points with %-s, like this: jsmall%cdp%[email protected] This method works most of the time. When it works, use this addressing form. Bang paths may fail if an intermediate site in the path happens to be down. (There is a trend for UUCP sites to register Internet domain names. This helps alleviate the problem of path failures.) Some messages must be routed through many gateways to reach their destination. This is the longest address that I have used, and it did work: [email protected] It used to be the Internet address of a user in Colorado, U.S.A.. Today, he can be reached using a much shorter address. If you are on UUCP/EUnet, you may use the following address to send email to Odd de Presno: extern.uio.no!opresno. Addressing international electronic mail sometimes looks like black magic. To learn more, read some of the books listed in appendix 5. We have found "The Matrix" by John S. Quarterman to be particularly useful. The conference INFONETS (General network forum) is another source. Here, the INTERNET postmasters discuss their addressing problems. Activity is high, and you will learn a lot about the noble art of addressing. (This is not the place to ask for Olav Janssen's Norwegian email address, though. This question should be sent to a Norwegian postmaster.) You can subscribe to Infonets by sending the following mail: To: [email protected] Subject: (You can write anything here. It will be ignored.) TEXT: SUB INFONETS Your-first-name Your-last-name If your mailbox is on another network, alter the address to route your subscription correctly to this LISTSERV. | Hint: You can search the database of old INFONETS messages by | | email to [email protected]. See "Directories of services | | and subscribers" below for information about how to search | | LISTSERV databases. | While the global matrix of networks grows rapidly, it is still behind in some lesser-developed nations and poorer parts of developed nations. If interested in these parts of the world, check out GNET, a library and a journal for documents about the efforts to bring the net to lesser-developed nations. Archived documents are available by anonymous ftp from the directory global_net at dhvx20.csudh.edu (155.135.1.1). Chapter 12 has information on how to use FTP if you only have mail access to the Internet. To subscribe to a conference discussing these documents, send a request to [email protected]. cc:Mail gateways ---------------- Many Local Area Networks have been connected to the global Matrix of networks. CompuServe offers a cc:Mail gateway. Lotus cc:Mail is a PC Lan based email system used in corporate, government and other organizations. When sending from CompuServe Mail to a cc:Mail user through this gateway, a typical address may look like this: >mhs:pt-support@performa To send to this user from the Internet through CompuServe's MHS gateway, write the address like this: [email protected] Other vendors of LAN gateways use other addressing methods. X.400 addressing ---------------- X.400 is a standard for electronic mail developed by CCITT. It is used on large networks like AT&T Mail, MCI Mail, Sprintnet, GE Information System, Dialcom, and Western Union, and on other public and private networks throughout the world. EDI (Electronic Data Interchange) uses X.400 as a transport mechanism for coordination of electronic part ordering, stock control and payment. X.400 is used to connect EDI systems between companies and suppliers. The X.400 addressing syntax is very different from domain addressing. To send a message from an X.400 mailbox to my address ([email protected]), you may have to write it like this: (C:NO,ADMD:uninett,PRMD:uninett,O:uio,OU:extern,S:opresno) Alas, it's not so standard as the domain addressing schemes. On other X.400 networks, the address must be written in one of the following formats - or in yet other ways: (C:US,A:Telemail,P:Internet,"RFC-822":) ("RFC-822": , SITE:INTERNET) '(C:USA,A:TELEMAIL,P:INTERNET,"RFC-822":extern.uio.no>) DEL' (site: INTERNET,ID: extern.uio.no>) "RFC-822=opresno(a)extern.uio.no @ GATEWAY]INTERNET/TELEMAIL/US" To send an Internet message to a mailbox I once had on the X.400 host Telemax in Norway, I had to use the following address: /I=D/G=ODD/S=PRESNO/O=KUD.DATASEKR/@PCMAX.telemax.no To send from Internet to Telemail in the US, I have used this address: /PN=TELEMAIL.T.SUPPORT/O=TELENET.MAIL/ADMD=TELEMAIL/C=US/@sprint.com If you need to route your message through gateways, then complexity increases. One Norwegian UUCP user had to use the following address to get through: nuug!extern.uio.no!"pcmax.telemax.no!/I=D/G=ODD/S=PRESNO/O=KUD.DATASEKR/" To send a message from an X.400 system to my CompuServe mailbox, I have used the following address elements: Country = US ADMD = CompuServe PRMD = CSMail DDA = 75755.1327 The addressing methods used on X.400 systems vary. Another example: Some use the code C:USA rather than the ISO country code C:US. MCI Mail uses C:NORWAY, C:USA, and C:SWEDEN. Here are some important X.400 codes: C the ISO country code (on most services) ADMD domain code for public system (abbreviation A) PRMD domain code for connected private system (abbreviation P) O organization name OU organization unit S surname (last name) G given name (first name) I initials (in the name) DDA domain-defined attributes, keywords defined and used by the individual systems to specify mailboxes (user name, list, station, user code, etc.), direct delivery devices (attention name, telex addresses, facsimile, etc.) PN personal name (a) the character @ cannot be used when routing messages from X.400 to Internet. Try (a) instead. (p) the character % cannot be used when routing messages from X.400 to Internet. Try (p) instead. (b) the character ! (used in "bang" addresses). (q) the character " used in email addresses. RFC-822 this code tells X.400 that an Internet domain address follows. Does not work on all X.400 systems. Returned mail ------------- When an email address is incorrect in some way (the system's name is wrong, the domain doesn't exist, whatever), the mail system will bounce the message back to the sender. The returned message will include the reason for the bounce. A common error is addressing mail to an account name that doesn't exist. Let's make an error when sending to [email protected]. Enter "[email protected]" instead of "[email protected]". This address is wrong. Below, we've printed the complete bounced message. It contains a lot of technical information. Most lines have no interest. Also, the message is much larger than the original message, which contained three lines only. When browsing the bounced message, note that it has three distinct parts: (1) The mail header of the bounced message itself (here, the 13 first lines), (2) The text of the error report (from line 14 until the line "Original message follows:"), and (3) the mailer header and text of your original message (as received by computer reporting the error): From [email protected] Fri Dec 18 12:54:03 1992 Return-Path: Received: from vm1.NoDak.edu by pat.uio.no with SMTP (PP) id <[email protected]>; Fri, 18 Dec 1992 12:53:54 +0100 Received: from NDSUVM1.BITNET by VM1.NoDak.EDU (IBM VM SMTP V2R2) with BSMTP id 9295; Fri, 18 Dec 92 05:53:27 CST Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.07) with BSMTP id 3309; Fri, 18 Dec 92 05:53:26 CST Date: Fri, 18 Dec 92 05:53:26 CST From: Network Mailer To: [email protected] Subject: mail delivery error Status: R Batch SMTP transaction log follows: 220 NDSUVM1.BITNET Columbia MAILER R2.07 BSMTP service ready. 050 HELO NDSUVM1 250 NDSUVM1.BITNET Hello NDSUVM1 050 MAIL FROM: 250 ... sender OK. 050 RCPT TO: 250 ... recipient OK. 050 DATA 354 Start mail input. End with . 554-Mail not delivered to some or all recipients: 554 No such local user: PISTSERV 050 QUIT 221 NDSUVM1.BITNET Columbia MAILER BSMTP service done. Original message follows: Received: from NDSUVM1 by NDSUVM1.BITNET (Mailer R2.07) with BSMTP id 3308; Fri, 18 Dec 92 05:53:25 CST Received: from pat.uio.no by VM1.NoDak.EDU (IBM VM SMTP V2R2) with TCP; Fri, 18 Dec 92 05:53:23 CST Received: from ulrik.uio.no by pat.uio.no with local-SMTP (PP) id <[email protected]>; Fri, 18 Dec 1992 12:53:24 +0100 Received: by ulrik.uio.no ; Fri, 18 Dec 1992 12:53:18 +0100 Date: Fri, 18 Dec 1992 12:53:18 +0100 From: [email protected] Message-Id: <[email protected]> To: [email protected] Subject: test index kidlink The first part of the bounced message is usually of no interest. Hidden in the second part you'll find the following interesting line: 554 No such local user: PISTSERV Ah, a typo! If your original message was long, you're likely to be pleased by having the complete text returned in the third part of the bounced message. Now, you may get away with a quick cut and paste, before resending it to the corrected address. The text and codes used in bounced messages vary depending on what type of mailbox system you're using, and the type of system that is bouncing your mail. Above, [email protected] returned the full text of my bounced mail. Some systems just send the beginning of your original text, while others (in particular some X.400 systems) send nothing but a note telling you the reason for the bounce. | Note: When you fail to understand why a message is being | | bounced, contact your local postmaster for help. Send him | | a copy of the complete text of the bounced message up to | | and including the line "Subject:" at the bottom. | | You do not have to send him the text of your original | | message! | Replying to an Internet message ------------------------------- On the Internet, electronic messages have a common structure that is common across the network. On some systems, you can reply by using a reply command. If this feature is not available, use the sender's address as given in the mail header. The bounced message contained two mail headers: the header of my original message (in part three), and the header of the bounced message (in part one). The 'good' reply address is laid out in the 'From:' header. Thus, this message contains the following two 'good' addresses: From: Network Mailer From: [email protected] The Network Mailer located the second address line above in my original message, and used this address when sending the bounced message. (Note: there is no point in sending a message back to [email protected] since this is the address of an automatic mail handling program. Write to [email protected] to talk to a "real person" at this computer center.) The exact order of a message's header may vary from system to system, but it will always contain the vital 'From:' line. | Note: Exercise caution when replying to a message sent by | | a mailing list. If you wish to respond to the author only, | | make sure that the only address you're replying to is that | | person's. Don't send it to the entire list! | Directories of services and subscribers --------------------------------------- There is no complete global directory of available electronic addresses. On many systems, however, you can search lists of local users. | Normally, you'd be better off by calling the recipient for | | his or her email address. | Sometimes, the information given you by the recipient is not enough. Maybe the address needs an extension for the message to be routed through gateways to the destination. Another typical problem is that the syntax of the address is wrong. Perhaps you made a mistake, when you wrote it down (KIDCAFE became KIDSCAFE). The return address in the received messages' mailer headers may be wrong. It may use a syntax that is illegal on you email system, or it may suggest a routing that is unknown to your system. When trying to send mail to this address, the Mailer-Daemon complains: "This is a non-existent address." Again, the first person to contact for help is your local postmaster. On most Internet hosts this is simple. If you have a mailbox on the ULRIK computer at the University of Oslo, send a request for help to [email protected] . If you are on COLNET in Buenos Aires, send to [email protected] . POSTMASTER is also the address to turn to on BITNET. Users of FidoNet or RelayNet, should write to SYSOP. It may not be that simple to locate the postmaster on UUCP. The postmaster ID may exist on some systems, but often he's just a name or a user code. You can get the email address of known Internet systems by sending a message to [email protected] . In the subject of the message, write the command WHOIS host-machine-name. Do not write anything in the text (will be ignored). You will get a report of the desired mailbox computer, and the address of the local postmaster. Example: To: [email protected] Subject: WHOIS AERO.ORG Text: Sometimes, you just don't know the name of a recipient's mailbox computer. When this is the case, start at the "top of the pyramid." Say your desired recipient lives in Germany. The ISO country code for Germany is DE (see appendix 6). Send the message To: [email protected] Subject: WHOIS DOMAIN DE Text: This will give you the email addresses of the main postmasters for this country. Most postmasters are willing to help, but please note that most of them are very busy people. It may take days before they get around to respond to your inquiry. There are over 100 other "whois-servers" in more than 15 countries. The systems whois.nic.ad.jp and whois.ripe.net cover Japan and Europe. The rest of them provide information about local users. (A list is available via anonymous FTP from sipb.mit.edu in the file /pub/whois/whois-servers.list . Chapter 12 has information about how to get this list by email). If your recipient is on UUCP, try [email protected] . To locate the postmaster of the mailbox system "amanpt1", use the following format (write nothing in the text): To: [email protected] Subject: amanpt1 Text: BITNET provides information about connected systems through many sources. Scandinavian users use [email protected] in Finland. Try a LISTSERV on a host closer to where you live. For example, North American users may use [email protected], which is a host in North Dakota. Japanese users should write to the host [email protected]. When retrieving for BITNET host information mail, your search will have to be done in two steps. Here, your commands are NOT to be entered on the Subject line. Enter all commands in the TEXT field (text on the Subject line will be ignored). Example: You want information about the BITNET computer FINHUTC (called a "node in the network"). Your first message should have the following text: // job echo=no database search dd=rules //rules dd * search * in bitearn where node = FINHUTC index LISTSERV sends you the following report: > search * in bitearn where node = FINHUTC --> Database BITEARN, 1 hit. > index Ref# Conn Nodeid Site name ---- ---- ------ --------- 0910 85/11 FINHUTC Helsinki University of Technology, Finland Send a new search message to the LISTSERV containing the same commands as above. Add one line in which you ask for database record number 0910 (given in the column Ref#). Like this: // job echo=no database search dd=rules //rules dd * search * in bitearn where node = FINHUTC index print 0910 LISTSERV will return a report with a lot of information. Here is part of it: Node: FINHUTC Country: FI Internet: FINHUTC.hut.fi Net: EARN Nodedesc: Helsinki University of Technology, Finland P_hsalmine: Harri Salminen;LK-HS@FINHUTC;+358 0 4514318 P_pautio: Petri Autio;POSTMAST@FINHUTC;+358 0 4514318 P_vvoutila: Vuokko Voutilainen;OPR@FINHUTC;+358 0 4514342 Routtab: RSCS (NETSERV,POSTMAST@FINHUTC) For more information about searching BITNET databases, send this message to your favorite LISTSERV, or use the address below: To: [email protected] Subject: nothing TEXT: GET LISTDB MEMO X.400 systems are developing an address directory according to CCITT standard X.500. The plan is to connect several directories. The developers hope that routing of X.400 messages may eventually be done automatically without the user needing to know the identity of the recipient's mailbox computer. X.500 will certainly help X.400 users. The problem is that most email is still carried by other types of systems, and that X.500 has no concern for mail transported through "foreign systems." Dialcom ------- is a commercial, global online service, which have many nodes in Africa and Latin America. To send mail from Dialcom to the Internet you must use commercial gateway-services like DASnet (see appendix 1). To send mail from one Dialcom system to another, use the syntax 6007:EWP002. This address points to mailbox EWP002 on system number 6007. To send mail from Internet to Dialcom user YNP079 on system 10001, use the following address when sending through DASnet: [email protected] Note: Only registered users with DASnet can use this method. FidoNet ------- Users of this global network can send and receive mail to/from the Internet. For example, a FidoNet user may use the following method to send to my Internet address: Send the message to user UUCP at 1:105/42. The first line of the TEXT of the message should contain: To: [email protected] Add a blank line after the address before entering the text of your message. FidoNet addresses are composed by three or four numbers; zone:net/node or zone:net/node.point The FidoNet address 1:105/42 has three elements. "1:" tells that the recipient lives in Zone number 1 (North America). "105/42" refers to Node number 42, which receives mail through Net number