From owner-freebsd-hackers Tue Apr 25 17:11:03 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA24620 for hackers-outgoing; Tue, 25 Apr 1995 17:11:03 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA24609 for ; Tue, 25 Apr 1995 17:10:56 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id RAA00471; Tue, 25 Apr 1995 17:06:49 -0700 From: "Rodney W. Grimes" Message-Id: <199504260006.RAA00471@gndrsh.aac.dev.com> Subject: Re: MX record problem To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Tue, 25 Apr 1995 17:06:48 -0700 (PDT) Cc: dunn@ferrum.edu, freebsd-hackers@FreeBSD.org In-Reply-To: <9504252324.AA05177@brasil.moneng.mei.com> from "Joe Greco" at Apr 25, 95 06:24:05 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1756 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > I'm hoping that somebody could give me some direction with this MX > > record error... I'm sure that I had this working, but last week I > > started getting mail like this: > > > > ---CUT HERE--- > > From daemon Tue Apr 25 11:55:05 1995 > > Received: from localhost (localhost) by panther.ferrum.edu (8.6.9/8.6.9)... > > From: Mail Delivery Subsystem > > Subject: Returned mail: Local configuration error > > Message-Id: <199504251555.LAA04252@panther.ferrum.edu> > > To: postmaster > > Status: OR > > > > ----- The following addresses had delivery problems ----- > > dunn@ferrum.edu (unrecoverable error) > > > > ----- Transcript of session follows ----- > > 554 MX list for ferrum.edu. points back to panther.ferrum.edu > > 554 dunn@ferrum.edu... Local configuration error > > ---CUT HERE--- > > Hi Jim, > > This probably is not an "MX record error" per se, but rather a mail > configuration problem. panther.ferrum.edu does not recognize mail being > sent to "ferrum.edu" as belonging to itself, and attempts to send it via the > network - only to discover that the most preferential route is back to > itself! > > I typically use the sendmail.cw feature to set a list of hostname aliases > within /etc/sendmail.cw that I wish to be known as. There are other ways to > do it, but I'm not convinced any are as easy and/or portable. This person also has a DNS configuration problem, from when his mail hit my box: gndrsh named[81]: Lame delegation to '' from [192.80.214.100] (server for 'ferrum.EDU'?) on query on name 'ferrum.edu' -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD