Path: utzoo!attcan!uunet!samsung!uakari.primate.wisc.edu!sdd.hp.com!usc!orion.oac.uci.edu!ucivax!gateway From: mac@dit.upm.es (Manuel Alvarez-Campana Fernandez-Corredor) Newsgroups: comp.protocols.iso.x400.gateway Subject: Traces from rfc-822 to x.400 and back to rfc-822? Message-ID: Date: 25 Oct 90 18:21:12 GMT Distribution: comp Organization: Dept. Ingenieria de Sistemas Telematicos, UPM, Madrid, Spain. Lines: 22 Approved: usenet@ICS.UCI.EDU Posting-Front-End: GNU Emacs 18.41.36 of Wed Jun 15 1988 on greco (berkeley-unix) x-attn: jns X-Previously-To: comp-protocols-iso-x400-gateway@goya.dit.upm.es ReSent-To: ifip-gtwy@ICS.UCI.EDU In rfc-987, a rfc-822 traces field (Received:) is mapped in x400 trace. The problem I see is that if a message which has crossed a gateway from rfc-822 to x.400 goes back to rfc-822 (this is perfectly normal), x400 traces are mapped in the extended header "X400-Trace:" and not in "Received:", independently on if it was originated in x.400 or rfc-822. This means that loops can only be detected in X.400 world, doesn't it? Manuel. -- .-----------------------------.--------------------------------. | Manuel Alvarez-Campana | EUnet: | | Dept. Ingenieria Telematica | mac@dit.upm.es | | ETSIT - UPM | X.400: | | Ciudad Universitaria s/n | C=es;ADMD= ;PRMD=iris;O=upm; | | 28040 - MADRID | OU=dit;OU=cactus;SUR=mac; | `--------------------------------------------------------------'