Received: from localhost (maia-2.hub.org [200.46.204.187])
	by postgresql.org (Postfix) with ESMTP id AC4929FA43C
	for <pgsql-www-postgresql.org@postgresql.org>;
	Mon,  5 Feb 2007 23:11:45 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024)
	with ESMTP id 52675-08 for <pgsql-www-postgresql.org@postgresql.org>;
	Mon,  5 Feb 2007 23:11:36 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.4
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by postgresql.org (Postfix) with ESMTP id F0FB29FB31E
	for <pgsql-www@postgresql.org>; Mon,  5 Feb 2007 23:11:41 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l163BbUi027750;
	Mon, 5 Feb 2007 22:11:37 -0500 (EST)
To: Josh Berkus <josh@agliodbs.com>
cc: "Marc G. Fournier" <scrappy@hub.org>, pgsql-www@postgresql.org
Subject: Re: pgsql-announce not being delivered? 
In-reply-to: <200702051906.06942.josh@agliodbs.com> 
References: <200702051424.48423.josh@agliodbs.com>
	<DFAEC97E8ED700B3B7414B60@ganymede.hub.org>
	<200702051906.06942.josh@agliodbs.com>
Comments: In-reply-to Josh Berkus <josh@agliodbs.com>
	message dated "Mon, 05 Feb 2007 19:06:06 -0800"
Date: Mon, 05 Feb 2007 22:11:37 -0500
Message-ID: <27749.1170731497@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200702/75
X-Sequence-Number: 11480

Josh Berkus <josh@agliodbs.com> writes:
> Well, that worked, but it somehow also "unstuck" the previous message.

A bunch of other recent pgsql-announce messages seem to have come
"unstuck" too ...

			regards, tom lane