From owner-freebsd-chat Wed Dec 20 1: 5: 3 2000 From owner-freebsd-chat@FreeBSD.ORG Wed Dec 20 01:05:02 2000 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from ducky.nz.freebsd.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 1054A37B400 for ; Wed, 20 Dec 2000 01:05:01 -0800 (PST) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id WAA32444; Wed, 20 Dec 2000 22:04:56 +1300 (NZDT) Message-Id: <200012200904.WAA32444@ducky.nz.freebsd.org> From: "Dan Langille" Organization: langille.org To: "Crist J. Clark" Date: Wed, 20 Dec 2000 22:05:03 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: No cable modems?? Reply-To: dan@langille.org Cc: freebsd-chat@FreeBSD.ORG, Stephen McKay Priority: normal In-reply-to: <20001220010215.R96105@149.211.6.64.reflexcom.com> References: <20001220035135.A3783@cae88-102-101.sc.rr.com>; from dmaddox@sc.rr.com on Wed, Dec 20, 2000 at 03:51:35AM -0500 X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 20 Dec 2000, at 1:02, Crist J. Clark wrote: > Yeah, that is common, but that's not what is happening here. The name > and address do not match. You would expect it is possible multiple > names to map to one IP address, but here we have a machine giving a > name which corresponds to a _different_ IP than the one from which the > connection is coming. It looks like it is lying about being > Mail6.sc.rr.com. > > But I am not sure if that is even the problem or not. FWIW, I had exactly the same problem with my former ISP about a year or two ago. My mail was rejected from freebsd.org and the problem was the above situation. -- Dan Langille The FreeBSD Diary - http://www.freebsddiary.org/ NZ ADSL - http://www.unixathome.org/adsl/ NZ Broadband - http://www.unixathome.org/broadband/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message