Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 485069F981C for ; Wed, 7 Nov 2007 05:06:06 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 66598-06 for ; Wed, 7 Nov 2007 05:05:57 -0400 (AST) Received: from cronos.madness.at (madness.at [217.196.146.217]) by postgresql.org (Postfix) with ESMTP id D9C4F9F981B for ; Wed, 7 Nov 2007 05:05:56 -0400 (AST) Received: from congw.dc1.conova.com ([217.196.145.250] helo=[192.168.1.61]) by cronos.madness.at with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1Ipgqd-0002vB-23; Wed, 07 Nov 2007 10:05:52 +0100 Message-ID: <47318017.2070503@kaltenbrunner.cc> Date: Wed, 07 Nov 2007 10:06:31 +0100 From: Stefan Kaltenbrunner User-Agent: Icedove 1.5.0.14pre (X11/20071018) MIME-Version: 1.0 To: Andreas 'ads' Scherbaum CC: pgsql-www@postgresql.org Subject: Re: what is up with the PG mailing lists? References: <25716.1193887595@sss.pgh.pa.us> <26669.1193891360@sss.pgh.pa.us> <47299585.7030402@hagander.net> <47299957.5020605@postgresql.org> <2968.1193919208@sss.pgh.pa.us> <20071101080959.49f3087b@scratch> <20071101152333.GM27676@crankycanuck.ca> <4729F105.30704@hagander.net> <20071101084752.64ac3936@scratch> <20071101171452.GT27676@crankycanuck.ca> <20071106204448.c2eb562d.adsmail@wars-nicht.de> <28131.1194378609@sss.pgh.pa.us> <226C39A675D734B74354263D@ganymede.hub.org> <4730CF84.80201@hagander.net> <20071106233723.41f606f4.adsmail@wars-nicht.de> In-Reply-To: <20071106233723.41f606f4.adsmail@wars-nicht.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/151 X-Sequence-Number: 12929 Andreas 'ads' Scherbaum wrote: > On Tue, 06 Nov 2007 17:37:18 -0400 Marc G. Fournier wrote: > >> - --On Tuesday, November 06, 2007 21:33:08 +0100 Magnus Hagander >> wrote: >> >>> Marc G. Fournier wrote: >>>> 'k, I'm confused ... the only name that should be referenced in any config >>>> file is maia.hub.org, which breaks down as: >>>> >>>> Name: maia.hub.org >>>> Address: 200.46.204.184 >>>> Name: maia.hub.org >>>> Address: 200.46.204.183 >>>> >>>> So, how/where are ppl seeing 200.46.204.187 :( >>> dig -x 200.46.204.187 >>> >>> returns >>> 187.204.46.200.in-addr.arpa. 18000 IN PTR maia-2.hub.org. >>> >>> Similar for -1. >> Right, and? > > ads@iridium:/home/ads > dig -x maia-2.hub.org. > dig: '.org.hub.maia-2.in-addr.arpa.' is not a legal name (empty label) -x implies a reverse/PTR lookup so you need to supply an ip-address ... > > > And where this came from? > > Nov 1 20:30:53 base postfix/smtpd[11763]: warning: smtpd_peer_init: 200.46.204.187: address not listed for hostname maia-2.hub.org > Nov 1 20:30:54 base postfix/smtpd[11763]: NOQUEUE: reject: RCPT from unknown[200.46.204.187]: 450 : Helo command rejected: Host not found; from= to= proto=ESMTP helo= > > a) the ip-address has an invalid (missing) ptr record > b) this server is knowing itself by maia-2.hub.org, which cannot resolved > (but matches the invalid ptr record) well this problem (200.46.204.187 having a PTR of maia-2.hub.org but forward resolution is not correct/missing) seems to be fixed now (and you log entry is now nearly a week old) Stefan