Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id PAA01653; Thu, 29 Jun 1995 15:19:46 -0400 X-Resent-To: drums@CS.UTK.EDU ; Thu, 29 Jun 1995 15:19:45 EDT Errors-to: owner-drums@CS.UTK.EDU Received: from po7.andrew.cmu.edu by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id PAA01645; Thu, 29 Jun 1995 15:19:43 -0400 Received: (from postman@localhost) by po7.andrew.cmu.edu (8.6.12/8.6.12) id PAA16459 for drums@cs.utk.edu; Thu, 29 Jun 1995 15:19:32 -0400 Received: via switchmail; Thu, 29 Jun 1995 15:19:29 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Thu, 29 Jun 1995 15:18:45 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Thu, 29 Jun 1995 15:18:42 -0400 (EDT) Received: from BatMail.robin.v2.14.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4c.411 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Thu, 29 Jun 1995 15:18:40 -0400 (EDT) Message-ID: Date: Thu, 29 Jun 1995 15:18:40 -0400 (EDT) From: John Gardiner Myers To: drums@CS.UTK.EDU Subject: mail relay Beak: Is RFC 1123 section 5.2.6 states: > (2) An SMTP mail "relay" forwards a message within an SMTP > mail environment as the result of an explicit source route > (as defined in section 3.6 of RFC-821). The SMTP relay > function uses the "@...:" form of source route from RFC- > 822 (see Section 5.2.19 below). this text does not adequately describe the function needed by minimal SMTP clients--those which need to inject or gateway messages into the Internet, but which do not implement queues or MX record processing. Such clients usually connect to a single configured SMTP server and deliver all mail there, relying on that server to accept, queue, and deliver the mail to arbitrary addresses. The wording above would appear to require such clients to use explicit source routes in the RCPT commands, in violation of the SHOULD NOT directive later in the same section. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up