Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 14 Nov 2001 22:37:03 -0500
From:      Jim Durham <durham@w2xo.pgh.pa.us>
To:        "Louis A. Mamakos" <louie@TransSys.COM>, walton@digger.net
Cc:        Greg Lehey <grog@FreeBSD.ORG>, mobile@FreeBSD.ORG
Subject:   Re: Sending mail to FreeBSD.org (was: FreeBSD lockup accessing serial port on Thinkpad)
Message-ID:  <200111150337.fAF3b4u32892@w2xo.pgh.pa.us>
In-Reply-To: <200111141433.fAEEX2E71690@whizzo.transsys.com>
References:  <20011114060923.89146.qmail@aerre.pair.com> <200111141433.fAEEX2E71690@whizzo.transsys.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 14 November 2001 09:33 am, Louis A. Mamakos wrote:
> > I send to mail.pacbell.net (aka mta7.pltn13.pbi.net,
> > mta5.snfc21.pbi.net, mta6.snfc21.pbi.net). From the look of the bounce
> > messages, they are leaving off the hostname and sending just the domain
> > (pltn13.pbi.net or snfc21.pbi.net). Which is good and proper:
> >
> >
> >   RFC 821:  "HELO <SP> <domain> <CRLF>"
> > (Though it goes on to contradict itself with "The argument field
> > contains the host name of the sender-SMTP", ALL examples given use a
> > domain name.)
> >
> > RFC 1123: "The sender-SMTP MUST ensure that the <domain> parameter
> > in a HELO command is a valid principal host domain name for the client
> > host. [...] The HELO receiver MAY verify that the HELO parameter really
> > corresponds to the IP address of the sender. However, the receiver MUST
> > NOT refuse to accept a message, even if the sender's HELO command fails
> > verification."
> >
> > RFC 2821: "The argument field contains the fully-qualified domain name
> > of the SMTP client if one is available."
> >
> > ...and others.
>
> No, you mis-interpret the specification.  <domain> refers to a domain name,
> e.g., the fully qualified domain name of the host.  It's not what might
> othewise be called the "sub-domain".  Unless pltn13.pbi.net resolves to
> something useful (which apparently it does not), this isn't going to be
> accepted. The HELO command is supposed to identify the actual end-system
> host submitting the message to produce accurate adivisory information and
> proper Received: header lines.  It's not intended to be some generic domain
> identifier.
>
However, 1123 *does* say that "the receiver must not refuse to accept a 
message", etc, etc. I noticed that hub.freebsd.org is postfix. Sendmail would
accept the message, but probably append a header saying "Possibly Forged" or 
something of that sort. It sounds like that is the intent of the RFC.

-Jim

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111150337.fAF3b4u32892>