Text 10166, 131 rader
Skriven 2018-11-06 14:43:38 av Björn Felten (2:203/2)
     Kommentar till en text av Björn Felten (2:203/2)
Ärende: FTS-0004.002 -- RFC (second attempt)
============================================
Björn Felten -> All skrev 2014-11-07 00:57:
 BF> FTS-0004 Echomail Specification

 BF> WHAT IS ECHOMAIL?

 BF> Echomail is a technique to permit several nodes on the Fidonet
 BF> network to share messages. All systems sharing a given conference see
 BF> any messages entered into the Echo by any of the participating
 BF> systems.

 BF> HOW IT WORKS

 BF> Echomail is functionally compatible with Netmail. In general, the
 BF> process is:

 BF> 1. A message is entered into a designated area on a FidoNet
 BF> compatible system.

 BF> 2. This message is "Exported" along with some control information
 BF> to each system "linked" to the Echo through the originating
 BF> system.

 BF> 3. Each of the receiving systems "Import" the message into the
 BF> proper Echomail area.

 BF> 4. The receiving systems then "Export" these messages, along with
 BF> additional control information, to each of their conference
 BF> links.

 BF> 5. Return to step 3.

 BF> Following the steps literally would mean messages would never stop
 BF> being exported and transmitted to other systems. The information
 BF> contained in the 'control information' section is used to prevent
 BF> transmitting the same message more than once to a single system.


 BF> CONTROL INFORMATION

 BF> There are five pieces of control information associated with an
 BF> Echomail message. Some are optional, some are not. The following
 BF> control fields determine how Echomail is handled:

 BF> 1. Area line

 BF> This is the first line of an Echomail message. Its actual appearance
 BF> is:

 BF> AREA:ECHO

 BF> Where ECHO the name of the conference. This line is added when an
 BF> Echo is being "Exported" to another system. It is based upon
 BF> information found in a configuration file for the designated message
 BF> area. This field is REQUIRED by the receiving system to "Import" a
 BF> message into the correct Echomail area.

 BF> 2. Tear Line

 BF> This line is near the end of a message and consists of three dashes
 BF> (---) followed by an optional program specifier. This is used to show
 BF> the first program used to add Echomail compatible control information
 BF> to the message. The tear line generated looks like:

 BF> --- <a small product-specific banner>

 BF> This line is optional.

 BF> 3. Origin line

 BF> This line appears near the bottom of a message and gives a small
 BF> amount of information about the system where it originated. It looks
 BF> like:

 BF> * Origin: The EchoMail BBS (1:132/101)

 BF> The " * Origin: " part of the line is a constant field. This is
 BF> followed by the name of the system as taken from a config file. The
 BF> complete network address (1:132/101 in this case) is added by the
 BF> program inserting the line. The field is generated at the same time as
 BF> the tear line, and therefore may either be generated at the time of
 BF> creation or during the first "export" processing.

 BF> 4. Seen-by Lines

 BF> There can be many seen-by lines at the end of Echomail messages. They
 BF> are used to determine the systems that are to receive the exported
 BF> messages. The format of the line is:

 BF> SEEN-BY: 132/101 113 136/601 1014/1

 BF> The net/node numbers correspond to the net/node numbers of the
 BF> systems having already received the message. In this way a message is
 BF> never sent to a system twice. An Echomail system must NEVER send a
 BF> message to a system that is already in the SEEN-BY line(s).

 BF> The line is added if it is not already a part of the message.

 BF> 5. PATH Lines

 BF> These are the last line(s) in a Echomail message. It appears as
 BF> follows:

 BF> ^aPATH: 132/101 1014/1

 BF> Where the ^a stands for Control-A (ASCII character 1) and the
 BF> net/nodes listed correspond to those systems having processed the
 BF> message before it reached the current system. This is not the same as
 BF> the seen-by lines, because those lines list all systems the message
 BF> has been sent to, while the path line contains all systems having
 BF> actually processed the message.

 BF> METHODS OF SENDING ECHOMAIL

 BF> Each message exported from an Echomail area has one message generated
 BF> for each receiving system. This mail is then sent the same as any
 BF> other network mail.

 BF> --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16)
 BF> Gecko/20101125
 BF> * Origin: news://felten.yi.org (2:203/2)


-- 




..

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
 * Origin: news://eljaco.se (2:203/2)