Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id A94E19FA22A for ; Mon, 5 Feb 2007 23:35:18 -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 19179-02 for ; Mon, 5 Feb 2007 23:35:17 -0400 (AST) Received: from hub.org (hub.org [200.46.204.220]) by postgresql.org (Postfix) with ESMTP id D47909F98D3 for ; Mon, 5 Feb 2007 23:35:17 -0400 (AST) Received: from localhost (unknown [200.46.204.187]) by hub.org (Postfix) with ESMTP id 8EBE6118C2CD for ; Mon, 5 Feb 2007 23:35:11 -0400 (AST) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 61446-07; Mon, 5 Feb 2007 23:35:07 -0400 (AST) Received: from ganymede.hub.org (blk-137-79-174.eastlink.ca [24.137.79.174]) by hub.org (Postfix) with ESMTP id 869A1118B3A0; Mon, 5 Feb 2007 23:35:07 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 5554A5D03A; Mon, 5 Feb 2007 23:35:18 -0400 (AST) Date: Mon, 05 Feb 2007 23:35:18 -0400 From: "Marc G. Fournier" To: Josh Berkus cc: pgsql-www@postgresql.org Subject: Re: pgsql-announce not being delivered? Message-ID: <6DCEC396FF17C7A7357D18F3@ganymede.hub.org> In-Reply-To: <200702051906.06942.josh@agliodbs.com> References: <200702051424.48423.josh@agliodbs.com> <200702051906.06942.josh@agliodbs.com> X-Mailer: Mulberry/4.0.7 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/78 X-Sequence-Number: 11483 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Monday, February 05, 2007 19:06:06 -0800 Josh Berkus wrote: > Marc, > >> Can you resend the announce you sent this morning ... ? I hate to have it >> sent out twice, but its important enough, and I believe that I've corrected >> the major problem causing the failed delivery, and would rather not have to >> wait until the next announce goes out ... > > Well, that worked, but it somehow also "unstuck" the previous message. So a > lot of people are about to get 2 copies of the release, and I'm about to get > a lot of annoyed e-mail. Oh, well, at least it's working now. > > Possibly related: previously I was getting the false "duplicate posting" > messages. I'm not getting them now. Ya, any 'duplicate postings' get held by moderator ... that 'unstuck' one was me, figuring that it would be faster to pass that one through ... thought I had sent you a 'found a copy' message fast enough to avoid you resending :( sorry about that ... - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFx/d24QvfyHIvDvMRAg25AKDfgEEjd/fVPP8dIJIBV6fqEIc+JwCfW0Dh zQCjjxT+dhpC9wgDJknBjZo= =ry5a -----END PGP SIGNATURE-----