From: Kai_Henningsen@ms.maus.de (Kai Henningsen)
Newsgroups: de.comm.gateways
Subject: Re: Envelopes mit ZCONNECT
Date: 27 Sep 92 12:27:00 GMT
Article-I.D.: MS.A48790
Organization: MausNet
X-Gateway: MausGate/News 1.13

pm> Von : p.mandrella@sps-hh.zer.de (Fr, 25.09.92 23:48)
pm> Name: Peter Mandrella
pm> Box : Stack's Point Server, Hamburg,FRG
pm> MId : <4mOyZCrsU~@SPS-HH.zer.sub.org>

pm> Envelope-Adressierung mittels ZCONNECT - ein Vorschlag
pm> Version 1, Peter Mandrella, 23.09.92, 05:10-06:50 :-)

Heiko hat ja schon geschrieben, warum das so nicht gehen kann. Hier vielleicht
zum besseren Verstaendnis ein paar Beispiele, wie sowas unter RFC konkret
aussieht (aus RFC 821; S: heisst senden, R: empfangen - das ist eine
Dialoganwendung; Anmerkungen von mir hinter ***):

   A Typical SMTP Transaction Scenario

      This SMTP example shows mail sent by Smith at host USC-ISIF, to
      Jones, Green, and Brown at host BBN-UNIX.  Here we assume that
      host USC-ISIF contacts host BBN-UNIX directly.  The mail is
      accepted for Jones and Brown.  Green does not have a mailbox at
      host BBN-UNIX.

      -------------------------------------------------------------

         R: 220 BBN-UNIX.ARPA Simple Mail Transfer Service Ready
         S: HELO USC-ISIF.ARPA
         R: 250 BBN-UNIX.ARPA
*** sozusagen Login fertig
         S: MAIL FROM:<Smith@USC-ISIF.ARPA>
         R: 250 OK
*** das war Envelope-From
         S: RCPT TO:<Jones@BBN-UNIX.ARPA>
         R: 250 OK
*** Envelope-To, erste Adresse
         S: RCPT TO:<Green@BBN-UNIX.ARPA>
         R: 550 No such user here
*** oho, jetzt muss der USC-Mailer eine Fehlermail an Smith schicken
         S: RCPT TO:<Brown@BBN-UNIX.ARPA>
         R: 250 OK
*** ... dritte ...
         S: DATA
*** Envelope fertig, es folgt der Header und der Body (hier nicht im Einzelnen
dargestellt)
         R: 354 Start mail input; end with <CRLF>.<CRLF>
         S: Blah blah blah...
         S: ...etc. etc. etc.
         S: .
         R: 250 OK
*** Mail fertig
         S: QUIT
         R: 221 BBN-UNIX.ARPA Service closing transmission channel
*** Logout
                               Scenario 1

      -------------------------------------------------------------

[...]


   Relayed Mail Scenario

      -------------------------------------------------------------

         Step 1  --  Source Host to Relay Host

            R: 220 USC-ISIE.ARPA Simple Mail Transfer Service Ready
            S: HELO MIT-AI.ARPA
            R: 250 USC-ISIE.ARPA

            S: MAIL FROM:<JQP@MIT-AI.ARPA>
            R: 250 OK

            S: RCPT TO:<@USC-ISIE.ARPA:Jones@BBN-VAX.ARPA>
            R: 250 OK
*** diesmal mit Header und Body
            S: DATA
            R: 354 Start mail input; end with <CRLF>.<CRLF>
            S: Date: 2 Nov 81 22:33:44
            S: From: John Q. Public <JQP@MIT-AI.ARPA>
            S: Subject:  The Next Meeting of the Board
            S: To: Jones@BBN-Vax.ARPA
            S:
            S: Bill:
            S: The next meeting of the board of directors will be
            S: on Tuesday.
            S:                                              John.
            S: .
            R: 250 OK

            S: QUIT
            R: 221 USC-ISIE.ARPA Service closing transmission channel


         Step 2  --  Relay Host to Destination Host

            R: 220 BBN-VAX.ARPA Simple Mail Transfer Service Ready
            S: HELO USC-ISIE.ARPA
            R: 250 BBN-VAX.ARPA

            S: MAIL FROM:<@USC-ISIE.ARPA:JQP@MIT-AI.ARPA>
            R: 250 OK

            S: RCPT TO:<Jones@BBN-VAX.ARPA>
            R: 250 OK
*** hier kommt die beruehmte Received:-Zeile in's Spiel ...
            S: DATA
            R: 354 Start mail input; end with <CRLF>.<CRLF>
            S: Received: from MIT-AI.ARPA by USC-ISIE.ARPA ;
               2 Nov 81 22:40:10 UT
            S: Date: 2 Nov 81 22:33:44
            S: From: John Q. Public <JQP@MIT-AI.ARPA>
            S: Subject:  The Next Meeting of the Board
            S: To: Jones@BBN-Vax.ARPA
            S:
            S: Bill:
            S: The next meeting of the board of directors will be
            S: on Tuesday.
            S:                                              John.
            S: .
            R: 250 OK

            S: QUIT
            R: 221 USC-ISIE.ARPA Service closing transmission channel

                               Scenario 3

      -------------------------------------------------------------


So laeuft das im Internet taeglich bestimmt ein paar hunderttausend Mal oder mehr
:-)

MfG Kai