XBR1YD14%DDATHD21.BITNET@wiscvm.ARPA (YD14@BR1.THDNET) (01/09/86)
We at DDATHD21.BITNET received a mail with the following header: > Received: from columbia.edu by wiscvm.wisc.edu on 01/07/86 at 13:19:50 CST > Received: by columbia.edu (5.31/5.10) id AA06692; Tue, 7 Jan 86 14:18:14 EST > From: phri!pluto!warren@columbia.edu > Received: by phri.UUCP (4.12/4.7) > id AA23384; Tue, 7 Jan 86 13:57:29 est > Date: Tue, 7 Jan 86 13:57:29 est > Message-Id: <8601071857.AA23384@phri.UUCP> > To: XBR1YD22%DDATHD21.BITNET@wiscvm.wisc.edu > Subject: ( deleted due to data security ) > In-Reply-To: your article <902@caip.RUTGERS.EDU> The header is OK. But the mail was not addressed to "XBR1YD22" as specified in the RFC-header. The mail was delievered to "SEISMO!X". The ARPA <-> BITNET gateway at WISCVM truncates f.e. the user field "SEISMO!XBR1YD22" of "SEISMO!XBR1YD22@DDATHD21.BITNET" to "SEISMO!X" because only 8 characters are allowed in BITNET. Some mailer must have forgotten to remove the "SEISMO!" in the transport information. Whose mailer doesn't process such mails correctly? Reinhard Goeth Technical University of Darmstadt Fed. Rep. of Germany ARPA address: XBR1YD14%DDATHD21.BITNET@WISCVM.WISC.EDU BITNET address: XBR1YD14 @ DDATHD21 (no NETDATA please)
roy@phri.UUCP (Roy Smith) (01/11/86)
> We at DDATHD21.BITNET received a mail with the following header: > [...] > > Message-Id: <8601071857.AA23384@phri.UUCP> > [...] > Whose mailer doesn't process such mails correctly? For what it's worth, I'm fairly sure it came through here OK. I've got the following entries in my sendmail log files: Jan 7 13:57:31 localhost: 23384 sendmail: AA23384: message-id=<8601071857.AA23384@phri.UUCP> Jan 7 13:57:32 localhost: 23384 sendmail: AA23384: from=pluto!warren, size=1152, class=0 Jan 7 13:57:40 localhost: 23387 sendmail: AA23384: to=columbia!seismo!XBR1YD22%DDATHD21.BITNET@WISCVM.WISC.EDU, delay=00:00:11, stat=Sent -- Roy Smith <allegra!phri!roy> System Administrator, Public Health Research Institute 455 First Avenue, New York, NY 10016