From: a2824as@cd1.lrz-muenchen.de (Michael Storz)
Subject: Re:      No "Date: "-line?
Reply-To: Michael.Storz@lrz.lrz-muenchen.dbp.de
Organization: Leibniz-Rechenzentrum Muenchen, Germany
Date: Wed, 19 Aug 1992 18:11:40 GMT

In article <9208170323.AA20745@SERVER.uwindsor.ca>,         Scott Ophof <ophof@SERVER.UWINDSOR.CA> writes:
|> Would someone tell me the rationale behind X.400 gateways dropping
|> the "Date:"-line from the header of mail from outside X.400 going
|> to an X.400 site?
|> 

This is nonsense, X.400 gateways do NOT drop the information of the Date field.
If the gateway is compatible to RFC 987/1148/1327 then the following happens:

    Date:
        This is used to set the first component of
        MTA.PerMessageTransferFields.trace-information
        (MTA.TraceInformationElement).  The 822-MTS originator is
        mapped into an MTS.ORAddress, and used to derive
        MTA.TraceInformationElement.global-domain-identifier.  The
        optional components of
        MTA.TraceInformationElement.domain-supplied-information are
        omitted, and the mandatory components are set as follows:

          MTA.DomainSuppliedInformation.arrival-time
             This is set to the date derived from Date:

          MTA.DomainSuppliedInformation.routing-action
             Set to relayed.

        The first element of
        MTA.PerMessageTransferFields.internal-trace-information is
        generated in an analogous manner, although this can be
        dropped later in certain circumstances (see the procedures
        for "Received:").  The
        MTA.InternalTraceInformationElement.mta-name is derived from
        the 822.domain in the 822 MTS Originator address.

And from X.400 to RFC 822 the following is done: 
   MTA.ReportTransferEnvelope.trace-information
        and
   MTA.ReportTransferEnvelope.internal-trace-information
        Mapped onto the extended RFC 822 field "X400-Received:", as
        described in Section 5.3.7.  The first element is also used
        to generate the "Date:" field, and the EBNF.report-point.
 

|> As I see it, this line contains information the *user* includes in
|> her/his/its mail, ie. MUA-data.  It's *not* MTA-related data.
|> At least I have never taken it as such...  Am I *that* far off-base?
|> 

Wrong, the Date field is not to be used by the user. It is set at submission
time when the MUA hands the message over to the MTA.

|> And why doesn't X.400 include a timestamp when it started processing
|> the item?  Even surface mail includes this time, date, and location
|> in their cancellation of the postage stamps...
|> 

Wrong, see above. The field arrival time of the first trace element is the
timestamp you are looking for.
 
BTW.: The next time you don't know something ask the net but don't make such
silly statements or show a prove for these statements.

-- 

Michael Storz
================================================================================
                                      !   X.400 : G=michael;S=storz;OU1=lrz;
   Leibniz-Rechenzentrum              !           P=lrz-muenchen;A=dbp;C=de
   Barer Str. 21                      !   RFC822: storz@lrz.lrz-muenchen.dbp.de
   8000 Muenchen 2                    !   Fax   : ++ 49 89 2809460
   Germany                            !   Tel   : ++ 49 89 2105 7420
================================================================================
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU