X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 1CAD9D1B351 for ; Tue, 1 Jun 2004 14:13:43 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 16777-08 for ; Tue, 1 Jun 2004 14:13:42 -0300 (ADT) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by svr1.postgresql.org (Postfix) with ESMTP id CDE8ED1B344 for ; Tue, 1 Jun 2004 14:13:40 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 918164A285; Tue, 1 Jun 2004 14:13:41 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 8E6B549FF8; Tue, 1 Jun 2004 14:13:41 -0300 (ADT) Date: Tue, 1 Jun 2004 14:13:41 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Greg Stark Cc: pgsql-general@postgresql.org Subject: Re: Problems with pgsql mail servers? In-Reply-To: <87vfib6y20.fsf@stark.xeocode.com> Message-ID: <20040601141203.N99557@ganymede.hub.org> References: <87vfib6y20.fsf@stark.xeocode.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/54 X-Sequence-Number: 61437 On Tue, 1 Jun 2004, Greg Stark wrote: > > Bret Busby writes: > >> For some strange reason, the message above, took somewhat over >> three months to come through, maybe due to the To address in the header >> (?). > > I also just received a message from a pgsql mailing list dated Feb 12. The > delay seemed to be in the queue on ns.pcbuddy.net [66.132.188.173]. And > someone commented a few months ago that I was unknowingly responding to a > long-dead thread, presumably due to a similar occurrence. > > Is it possible these mail servers aren't running their queues regularly? If a > network failure causes a delivery failure on the first attempt messages will > sit in a queue until they're retried. If qmail isn't configured to run its > queue regularly then they'll languish there. 'k, way back, I removed 66.132.191.19 out of the list of mail relays ... IP isn't the same, but they may have changed the IP since ... but we haven't been relaying through it in awhile ... so we aren't adding to its queue ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664