From owner-freebsd-questions Wed Feb 4 11:43:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22267 for questions-outgoing; Wed, 4 Feb 1998 11:43:05 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from buffnet4.buffnet.net (buffnet4.buffnet.net [205.246.19.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22211 for ; Wed, 4 Feb 1998 11:42:41 -0800 (PST) (envelope-from shovey@buffnet.net) Received: (from root@localhost) by buffnet4.buffnet.net (8.7.5/8.7.3) id OAA18584; Wed, 4 Feb 1998 14:37:10 -0500 (EST) Received: from buffnet11.buffnet.net(205.246.19.55) by buffnet4.buffnet.net via smap (V2.0) id xma018573; Wed, 4 Feb 98 14:37:03 -0500 Date: Wed, 4 Feb 1998 14:36:59 -0500 (EST) From: Steve Hovey To: chas cc: questions@FreeBSD.ORG Subject: Re: why must POP clients have a resolvable IP ? what about dynamic IPs ? In-Reply-To: <3.0.32.19980204144059.0093b100@peace.com.my> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe questions" It doesnt have to do with dynamic IPs - it has to do with that ISP failing to set up proper in-addr.arpa in his name service. On Wed, 4 Feb 1998, chas wrote: > I'm sure we've all seen this error message before : > > >> popper[14612]: (v2.2) Unable to get canonical name of client, err = 0 > > And checking the archives again, the explanation is : > > [snip] > "This means it can't get the domain name of the IP that is using popper. > Try doing a nslookup on the IP, if it fails that is the reason." > "You need to put the IP address of your client in the named or hosts." > [/snip] > > But the people who are collecting their mail via POP from our mailserver > are accessing the web through the local ISP (which is not us.) and hence > they have dynamic IPs. Is there any way to solve this in such circumstances ? > > Thank you very much, > > chas > > > ------------------------------------------------------------------ Steve Hovey Chief Engineer BuffNET More Than Just a Connection! ------------------------------------------------------------------