Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 61CC49F9455 for ; Thu, 1 Nov 2007 17:40:46 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 19326-02-2 for ; Thu, 1 Nov 2007 17:40:25 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from main2.mycybernet.net (main2.mycybernet.net [209.222.63.140]) by postgresql.org (Postfix) with ESMTP id 459BA9FC4AB for ; Thu, 1 Nov 2007 16:59:22 -0300 (ADT) Received: from 227-54-222-209.mycybernet.net ([209.222.54.227] helo=crankycanuck.ca) by main2.mycybernet.net with esmtp (Exim 4.62) (envelope-from ) id 1IngC6-0006BZ-Nt for pgsql-www@postgresql.org; Thu, 01 Nov 2007 15:59:10 -0400 Received: by crankycanuck.ca (Postfix, from userid 1000) id 5D23A4050; Thu, 1 Nov 2007 15:59:03 -0400 (EDT) Date: Thu, 1 Nov 2007 15:59:03 -0400 From: Andrew Sullivan To: pgsql-www@postgresql.org Subject: Re: what is up with the PG mailing lists? Message-ID: <20071101195903.GW27676@crankycanuck.ca> References: <2968.1193919208@sss.pgh.pa.us> <20071101080959.49f3087b@scratch> <20071101152333.GM27676@crankycanuck.ca> <4729F105.30704@hagander.net> <1127E6493CBA8A29F343C4D7@ganymede.hub.org> <4729F7D2.6050608@hagander.net> <20071101092806.3b1fa452@scratch> <10898.1193944992@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10898.1193944992@sss.pgh.pa.us> User-Agent: Mutt/1.5.9i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/41 X-Sequence-Number: 12819 On Thu, Nov 01, 2007 at 03:23:12PM -0400, Tom Lane wrote: > Well, the current problems seem to be entirely inside hub.org, and so > all this banter about DNS etc seems not relevant. A handy example is Could be. The main point is to get examples of the sort you just provided -- if we can get a nice collection, then it becomes reasonably likely we'll track the issue. That said, I'm not suggesting that DNS _is_ the problem, merely that it could be. Of course, if Marc is using the same DNS for internal and external DNS queries, and the externals are under attack, then his internal DNS is hosed. Or if there's a reverse tree somewhere in the path that isn't working 100% of the time, and the mail servers are all trying to do reverse lookups. (This is a remarkably common source of breakage, I have learned as a result of my work on a current internet draft.) Mail gremlins are notorious for their difficulty in debugging partly because of all the horrible interaction with DNS. Add a couple different name servers, 3 MX records, and the occasional bad reverse path, and you're into serious pain, especially after your spam filter proceeds to do much of it all over again. Even a single hop can be expensive then. But I do think there's something going on in the suspicious hop, and only Marc can diagnose it. A -- Andrew Sullivan | ajs@crankycanuck.ca "The year's penultimate month" is not in truth a good way of saying November. --H.W. Fowler