Received: from localhost (unknown [200.46.204.184])
	by postgresql.org (Postfix) with ESMTP id 9E60B9F9FBE;
	Thu,  1 Nov 2007 06:30:37 -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 87171-01; Thu,  1 Nov 2007 06:30:26 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.5
X-Greylist: from auto-whitelisted by SQLgrey-1.7.5
Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226])
	by postgresql.org (Postfix) with ESMTP id 4EE989F9FCA;
	Thu,  1 Nov 2007 06:30:30 -0300 (ADT)
Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and
	authenticated) by svr2.hagander.net (Postfix) with ESMTP id
	8944CDCC9E8; Thu,  1 Nov 2007 10:30:29 +0100 (CET)
Message-ID: <47299CBE.8030403@hagander.net>
Date: Thu, 01 Nov 2007 10:30:38 +0100
From: Magnus Hagander <magnus@hagander.net>
User-Agent: Thunderbird 2.0.0.6 (X11/20070728)
MIME-Version: 1.0
To: Dave Page <dpage@postgresql.org>
CC: Tom Lane <tgl@sss.pgh.pa.us>, "Marc G. Fournier" <scrappy@hub.org>,
	pgsql-www@postgresql.org
Subject: Re: what is up with the PG mailing lists?
References: <25716.1193887595@sss.pgh.pa.us>
	<DADF296033D290EF9634F611@ganymede.hub.org>
	<26669.1193891360@sss.pgh.pa.us> <47299585.7030402@hagander.net>
	<47299957.5020605@postgresql.org>
In-Reply-To: <47299957.5020605@postgresql.org>
X-Enigmail-Version: 0.95.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200711/14
X-Sequence-Number: 12792

Dave Page wrote:
> Magnus Hagander wrote:
>> Tom Lane wrote:
>>> "Marc G. Fournier" <scrappy@hub.org> writes:
>>>> I haven't noticed, but haven't been watchign for it ... can you send me full 
>>>> headers of one such affected?  This  one here seemed to be 'within minutes' :(
>>> Here's headers from a message I sent to -core today, which had about an
>>> hour turnaround ...
>> That one is clearly sitting waiting to go through the hub.org antispam
>> for about an hour (between 18:33 ADT and 19:35 ADT).
>>
>> Oh, and the message you sent with this info just took about over 4 hours
>> to get here, which happens fairly often. Headers from this one:
> 
> It sat in the mod queue until I approved it earlier.

Ah, that may explain some of the delays I've been seeing. But only those
between those two hops (postgresql -> hub) I guess.

//Magnus