Return to BSD News archive
Path: euryale.cc.adfa.oz.au!platinum.sge.net!como.dpie.gov.au!news.gan.net.au!act.news.telstra.net!vic.news.telstra.net!news.mira.net.au!news.netspace.net.au!news.mel.connect.com.au!munnari.OZ.AU!uunet!in3.uu.net!207.22.81.9!europa.clark.net!newsfeed.direct.ca!HSNX.wco.com!jupiter.dnai.com!not-for-mail
From: Michael Sierchio <xhqmh@qanv.pbz>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Mail question
Date: Sat, 28 Jun 1997 22:00:28 -0700
Organization: Oversized Metaphysics
Lines: 89
Message-ID: <33B5EBEC.6DBD@qanv.pbz>
References: <5p47sk$a1r@quail.swcp.com>
Reply-To: xhqmh@qanv.pbz
NNTP-Posting-Host: dnai-204-188-12-155.dialup.dnai.com
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailer: Mozilla 3.01Gold (Win95; U)
To: crs@swcp.com
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:43700
Charlie Sorsby wrote:
> =
> I'm running FreeBSD 2.1.5. My (local) hostname is quail, so named
> for my own amusement only. I like it better than localhost,
> although it is, of course, also known as localhost. I run popclient
> to get my mail from my ISP. I thought that I had sendmail set up
> properly.
> =
> But every once in a while, I get bounced mail because the recipient
> doesn't recognize "quail.swcp.com" -- of course there is no such
> host registered. I thought that sendmail was properly masquerading
> me as swcp.com as a result of:
> =
> DMswcp.com
> =
> in /etd/sendmail.cf which I built using m4 and the files provided.
> =3D ----- Transcript of session follows -----
> =3D ... while talking to a.mx.aol.com.:
> =3D >>> MAIL From:<crs@quail.swcp.com> SIZE=3D535
> =3D <<< 550 <crs@quail.swcp.com>... Sender domain not found in DNS (see=
RFC 1123, sections 5.2.2 and 5.2.18).
1. Didja read the RFC?
RFC1123 MAIL -- SMTP & RFC-822 October 1989
=2E..
5.2.2 Canonicalization: RFC-821 Section 3.1
The domain names that a Sender-SMTP sends in MAIL and RCPT
commands MUST have been "canonicalized," i.e., they must be
fully-qualified principal names or domain literals, not
nicknames or domain abbreviations. A canonicalized name either
identifies a host directly or is an MX name; it cannot be a
CNAME.
=2E..
5.2.18 Common Address Formatting Errors: RFC-822 Section 6.1
Errors in formatting or parsing 822 addresses are unfortunately
common. This section mentions only the most common errors. A
User Agent MUST accept all valid RFC-822 address formats, and
MUST NOT generate illegal address syntax.
o A common error is to leave out the semicolon after a group
identifier.
o Some systems fail to fully-qualify domain names in
messages they generate. The right-hand side of an "@"
sign in a header address field MUST be a fully-qualified
domain name.
For example, some systems fail to fully-qualify the From:
address; this prevents a "reply" command in the user
interface from automatically constructing a return
address.
DISCUSSION:
Although RFC-822 allows the local use of abbreviated
domain names within a domain, the application of
RFC-822 in Internet mail does not allow this. The
intent is that an Internet host must not send an SMTP
message header containing an abbreviated domain name
in an address field. This allows the address fields
of the header to be passed without alteration across
the Internet, as required in Section 5.2.6.
o Some systems mis-parse multiple-hop explicit source routes
such as:
@relay1,@relay2,@relay3:user@domain.
o Some systems over-qualify domain names by adding a
trailing dot to some or all domain names in addresses or
message-ids. This violates RFC-822 syntax.
-- =
Reply-To: rot13(xhqmh@qanv.pbz)
USC Title 47 / Chapt. 5 / Sub. II / =A7 227