Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 154C19FB2DE for ; Thu, 1 Nov 2007 04:12:25 -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 78938-02 for ; Thu, 1 Nov 2007 04:12:18 -0300 (ADT) 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 9FDAF9FB30E for ; Thu, 1 Nov 2007 04:12:10 -0300 (ADT) Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and authenticated) by svr2.hagander.net (Postfix) with ESMTP id 5CA42DCCA0D; Thu, 1 Nov 2007 08:12:09 +0100 (CET) Message-ID: <47297C51.10305@hagander.net> Date: Thu, 01 Nov 2007 08:12:17 +0100 From: Magnus Hagander User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: Bruce Momjian CC: Tom Lane , pgsql-www@postgresql.org Subject: Re: what is up with the PG mailing lists? References: <200711010402.lA142K628651@momjian.us> In-Reply-To: <200711010402.lA142K628651@momjian.us> 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/7 X-Sequence-Number: 12785 Bruce Momjian wrote: > Tom Lane wrote: >> I've seen enormously erratic performance from the mailing lists all day >> today --- delivery time for individual messages is up to several hours, >> but completely inconsistent. Is it just me, or are other people seeing >> the same? > > I see the same. My posting to core took +2 hours to arrive and there > are only a few subscribers. > This is all fairly normal behavior for our lists :-( The mails are usually stuck in a queue somewhere at hub.org. Sometimes it's the antispam queue, somtimes it's just the slow network connection to the panama server, sometimes somewhere else - I don't think it's been fully diagnosed since it keeps happening quite often. You can usually get a decent pointer as to where it's stuck by looking at the Received-headers in the message. //Magnus