X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 333789DCD3A; Wed, 30 Nov 2005 15:40:21 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 10714-02; Wed, 30 Nov 2005 15:40:18 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from hosting.commandprompt.com (128.commandprompt.com [207.173.200.128]) by postgresql.org (Postfix) with ESMTP id 547F59DCD32; Wed, 30 Nov 2005 15:40:15 -0400 (AST) Received: from [192.168.1.55] (fc1smp [66.93.38.87]) (authenticated bits=0) by hosting.commandprompt.com (8.13.4/8.13.4) with ESMTP id jAUJYARv009903; Wed, 30 Nov 2005 11:34:10 -0800 Subject: Re: [GENERAL] What is the deal with mailing lists? From: "Joshua D. Drake" Reply-To: jd@commandprompt.com To: Tom Lane Cc: Joshua Drake , "Jim C. Nasby" , "Psql_General (E-mail)" , PostgreSQL WWW Mailing List In-Reply-To: <211.1133377928@sss.pgh.pa.us> References: <438DE0BA.1050705@commandprompt.com> <20051130182200.GH13642@nasby.net> <211.1133377928@sss.pgh.pa.us> Content-Type: text/plain Organization: Command Prompt, Inc. Date: Wed, 30 Nov 2005 11:47:13 -0800 Message-Id: <1133380033.6635.36.camel@jd.commandprompt.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2 (2.4.2-1.1.fc4.nr) Content-Transfer-Encoding: 7bit X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (hosting.commandprompt.com [192.168.1.101]); Wed, 30 Nov 2005 11:34:10 -0800 (PST) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200511/216 X-Sequence-Number: 8931 On Wed, 2005-11-30 at 14:12 -0500, Tom Lane wrote: > Joshua Drake writes: > >> Anyway, next time you're seeing a delay take a look at the headers and > >> see if you can pin down what the bottleneck is. > > > Thank you for that... except that, I was talking about HOUR[n] delays not 13 > > minutes. > > Yeah, so ... where's the blockage according to your Received: headers? > > Personally I've been seeing list turnaround on the order of one minute, > across all the lists, since Marc fixed whatever he fixed about a week > ago (that was before the server changeover). It would seem that the > problem is with a forwarder upstream of you ... I actually think I might know one part of it at least. Which is I only whitelist the hub (and my own) relays... Which means if it hits any other relay, then that message will get greylisted. I have asked marc for the other relay ips so I can whitelist them and see if the problem persists. Joshua D. Drake > > regards, tom lane -- The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: PLphp, PLperl, ODBCng - http://www.commandprompt.com/