Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id E52DE9FB256 for ; Wed, 7 Feb 2007 18:21:31 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 94526-06 for ; Wed, 7 Feb 2007 18:21:20 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id 947C29FA15F for ; Wed, 7 Feb 2007 18:21:20 -0400 (AST) Received: from [192.168.199.197] (c213-100-160-41.swipnet.se [213.100.160.41]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by svr2.hagander.net (Postfix) with ESMTP id 3DBD7DCC3E3; Wed, 7 Feb 2007 23:21:19 +0100 (CET) Message-ID: <45CA50E1.6090109@hagander.net> Date: Wed, 07 Feb 2007 23:21:21 +0100 From: Magnus Hagander User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: "Marc G. Fournier" CC: Kevin Hunter , PostgreSQL www Subject: Re: email is fast! References: <200702020546.l125kPN11116@momjian.us> <20070202082145.GC20955@svr2.hagander.net> <45C8FDA1.7050903@earlham.edu> In-Reply-To: X-Enigmail-Version: 0.94.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/142 X-Sequence-Number: 11547 >>> Well, yeah, it's much better, and quite often it is that fast. And then >>> suddenly something happens and you have a 4-6 hour delay on a couple of >>> mails, while others go through. But the speed-when-things-are-working is >>> good, yes :-P >> Being a fairly new lurker to the Postgresql lists, what is the reason for the >> speed delay? I, too, have a 3-5 hour delay, but I thought it was something >> to do with my end and greylisting. Now I'm not sure . . . :/ > > Just to follow up this one ... Kevin sent me an email including the full > headers for one that took 12 hours to be delivered ... using the QUEUE ID, I > checked the logs and it turns out that the mail server couldn't resolve the MX > the first and second time it tried to deliver, but succeeded on the third ... This sounds scaringly close to the problem we had on wwwmaster with it not delivering emails. Resolving separately looked fine, but sendmail couldn't resolve. Could it be symptoms of the same problem? //Magnus