Date: Tue, 29 Sep 1992 20:03:00 CET
From: f.erkinger@link-atu.zer.sub.org
Reply-To: f.erkinger@link-atu.zer.sub.org
Distribution: world
Newsgroups: de.comm.gateways
Subject: Fido Originzeile
Organization: Zerberus Network Area, Germany
Content-Length: 7391    
X-Gateway: UU uzercp [UZERCP V3.99]

Hallo Kai !

 Du schriebst am 26.09.92 zum Thema "Re: Test":

> AR> Bei privaten Mails gibt es keine Originzeile.
>
> Wat et nich allens jibt. Und wie beantwortet man die dann?


Naja, laut Fido Doc's (FTS-0001.015) ist die Absenderadresse eindeutig im
Binaerheader feststellbar. Da sie dort allerdings nur 3D ist gibt es fuer
Nachrichten von Points und Interzonen Nachrichten die Kludges FMPT (From Point)
TOPT (To Point) und INTL (Von zone nach zone). Ausserdem ist noch in
FTS-0009.01 die Kludge MSGID definiert die aber optional ist.

Und die Originzeile (siehe Auschnitt aus FTS-0004.001) ist eine zusaetzliche
Zeile die prinzipiell optional ist, (obwohl manche Leute meinen sie muss sein)
aber genau vorschreibt wie sie auszusehen hat, wenn sie eingefuegt wird.
In allgemeinen fuegen die Prog's bei Netmail keine Originzeile ein, bei
Echomail's immer.


Hier aber drei Auschnitte aus den dazugehoerigen FTS:

Ps.: FTS sind die technischen Beschreibungen des Fidonetzes, zum Unterschied
zu FSC's die 'Empfehlungen' bzw. Ideen darstellen.



Ausschnitt aus FTS-0001.015
----------------------------

 1. Presentation Layer Data Definition : the Packed Message

|     PakdMessage  = 02H 00H           (* message type, old type-1 obsolete *)
                     origNode          (* of message *)
                     destNode          (* of message *)
                     origNet           (* of message *)
                     destNet           (* of message *)
                     AttributeWord
                     cost              (* in lowest unit of originator's
                                          currency *)
                     DateTime          (* message body was last edited *)
                     toUserName{36}    (* Null terminated *)
                     fromUserName{36}  (* Null terminated *)
                     subject{72}       (* Null terminated *)
                     text{unbounded}   (* Null terminated *)


  Message Text
  --------------
      Message text is unbounded and null terminated (note exception below).

      A 'hard' carriage return, 0DH,  marks the end of a paragraph, and must
      be preserved.

      So   called  'soft'  carriage  returns,  8DH,  may  mark  a   previous
      processor's  automatic line wrap, and should be ignored.  Beware  that
      they may be followed by linefeeds, or may not.

      All  linefeeds, 0AH, should be ignored.  Systems which display message
      text should wrap long lines to suit their application.

      If the first character of a physical line (e.g. the first character of
      the  message text, or the character immediately after a hard+  carriage
      return (ignoring any linefeeds)) is a ^A (<control-A>, 01H), then that
      line  is  not  displayed  as  it  contains  control  information.  The
      convention for such control lines is:
        o They begin with ^A
        o They end at the end of the physical line (i.e. ignore soft <cr>s).
        o They begin with a keyword followed by a colon.
        o The keywords are uniquely assigned to applications.
        o They keyword/colon pair is followed by application specific data.

      Current ^A keyword assignments are:
      o TOPT <pt no> - origin point address
      o FMPT <pt no> - origin point address
      o INTL <dest z:n/n> <orig z:n/n> - used for inter-zone address


Ausschnitt aus FTS-0004.001
-----------------------------

          2. Tear Line

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

                                    --- <a small product-specific banner>

               This  field   is  optional   for  most  Echomail  compatible
               processors, and  is added  by the  Conference Mail System to
               ensure complete  compatibility. Some systems will place this
               line in  the message  when it  is first  created, but  it is
               normally added when the message is first "exported."

          3. Origin line

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

                      * Origin: The Conference Mail BBS (1:132/101)

               The "  * Origin:  " part  of the  line is  a constant field.
               This is followed by the name of the system as taken from the
               AREAS.BBS file  or a  file named  ORIGIN located  in the DOS
               directory of  the  designated  message  area.  The  complete
               network address  (1:132/101 in  this case)  is added  by the
               program inserting  the line.  This field is generated at the
               same time  as the  tear line,  and therefore  may either  be
               generated at  the time  of  creation  or  during  the  first
               "export"  processing.   Although  the  Origin  line  is  not
                                                                        ^^^
               required by  all Echomail  processors, it  is added  by  the
               ^^^^^^^^^^^^^^^^
               Conference Mail System to ensure complete compatibility.


Auschnitt aus FTS-0009
------------------------
                               MSGID / REPLY
                  A standard for unique message identifiers
                          and reply chain linkage

Status of this document:

     This FTS (FidoNet(r) Technical Standard) specifies an optional
                                                           ^^^^^^^^
     standard for the FidoNet community.  Implementation of the
     ^^^^^^^^
     protocols defined in this document is not mandatory,  but all
     implementations of these protocols are expected to adhere to this
     standard.  Distribution of this document is unlimited.

     Fido and FidoNet are registered marks of Tom Jennings and Fido
     Software.


MSGID

     A MSGID line consists of the string "^AMSGID:" (where ^A is a
     control-A (hex 01) and the double-quotes are not part of the
     string),  followed by a space,  the address of the originating
     system,  and a serial number unique to that message on the
     originating system,  i.e.:

          ^AMSGID: origaddr serialno

     The originating address should be specified in a form that
     constitutes a valid return address for the originating network.
     If the originating address is enclosed in double-quotes,  the
     entire string between the beginning and ending double-quotes is
     considered to be the orginating address.  A double-quote character
     within a quoted address is represented by by two consecutive
     double-quote characters.  The serial number may be any eight
     character hexadecimal number,  as long as it is unique - no two
     messages from a given system may have the same serial number
     within a three years.  The manner in which this serial number is
     generated is left to the implementor.



Viele Gruesse,
               Felix.

---
 * Origin: Reality.sys corrupted, reboot universe (Y/N) ? (2:310/22.3)