Обсуждение: pgsql-announce not being delivered?
All, I just took a brief survey on IRC and found that 70% of the people there didn't get the release announcement. I didn't get it, nor PWN either. For that matter, I haven't gotten anything on -announce since December. It could be spam filtering issues, but if so they're quite widespread; it seems that most of our community is not getting most of the -announce posts. Any idea how to diagnose this? -- --Josh Josh Berkus PostgreSQL @ Sun San Francisco
Josh Berkus <josh@agliodbs.com> writes:
> I just took a brief survey on IRC and found that 70% of the people there
> didn't get the release announcement. I didn't get it, nor PWN either.
> For that matter, I haven't gotten anything on -announce since December.
FWIW, it took almost 2 hours to come through to me --- see attached
headers. The delay seems entirely the fault of the postgresql.org to
mx1.hub.org hop. Dunno if that helps diagnose anything.
regards, tom lane
------- Forwarded Message
Return-Path: pgsql-announce-owner+M1067@postgresql.org
Delivery-Date: Mon Feb 5 14:27:33 2007
Received: from mx1.hub.org (mx1.hub.org [200.46.208.251])by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id
l15JRWlI013061for<tgl@sss.pgh.pa.us>; Mon, 5 Feb 2007 14:27:33 -0500 (EST)
Received: from postgresql.org (postgresql.org [200.46.204.71])by mx1.hub.org (Postfix) with ESMTP id B564F608724;Mon,
5Feb 2007 15:27:31 -0400 (AST)
Received: from localhost (maia-5.hub.org [200.46.204.182])by postgresql.org (Postfix) with ESMTP id B5E9D9FB2B3for
<pgsql-announce-postgresql.org@postgresql.org>;Mon, 5 Feb 2007 13:32:57 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port
10024)withESMTP id 76302-05 for <pgsql-announce-postgresql.org@postgresql.org>;Mon, 5 Feb 2007 13:32:46 -0400 (AST)
Received: from spooky.sf.agliodbs.com (adsl-63-195-55-98.dsl.snfc21.pacbell.net [63.195.55.98])by postgresql.org
(Postfix)with ESMTP id 31C909FB1BEfor <pgsql-announce@postgresql.org>; Mon, 5 Feb 2007 13:32:47 -0400 (AST)
From: Josh Berkus <josh@postgresql.org>
Organization: PostgreSQL Project
To: pgsql-announce@postgresql.org
Subject: [ANNOUNCE] PostgreSQL security update available now
Date: Mon, 5 Feb 2007 09:32:44 -0800
User-Agent: KMail/1.8.2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200702050932.44529.josh@postgresql.org>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Mailing-List: pgsql-announce
List-Archive: <http://archives.postgresql.org/pgsql-announce>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-announce.postgresql.org>
List-Owner: <mailto:pgsql-announce-owner@postgresql.org>
List-Post: <mailto:pgsql-announce@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-announce>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-announce>
Precedence: bulk
Sender: pgsql-announce-owner@postgresql.org
Reply-To: pgsql-announce-owner@postgresql.org
------- End of Forwarded Message
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. -- Josh Berkus PostgreSQL @ Sun San Francisco
Josh Berkus <josh@agliodbs.com> writes:
> Well, that worked, but it somehow also "unstuck" the previous message.
A bunch of other recent pgsql-announce messages seem to have come
"unstuck" too ...
regards, tom lane
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been working on this this evening, and am talking to Michael (majordmo developer) about it ... I *think* I've narrowed down the problem, and implemented improvements for it, but am waiting to hear back from Michael as to whether there are some sort of 'stats' that record # of recipients actually sent to ... But, I am in the process of diagnosing it ... Just curious, but "haven't gotten anything since December", and you are just mentioning it now ... ? 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 ... - --On Monday, February 05, 2007 14:24:48 -0800 Josh Berkus <josh@agliodbs.com> wrote: > All, > > I just took a brief survey on IRC and found that 70% of the people there > didn't get the release announcement. I didn't get it, nor PWN either. > For that matter, I haven't gotten anything on -announce since December. > > It could be spam filtering issues, but if so they're quite widespread; it > seems that most of our community is not getting most of the -announce > posts. Any idea how to diagnose this? > > -- > --Josh > > Josh Berkus > PostgreSQL @ Sun > San Francisco - ---- 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+vY4QvfyHIvDvMRAmrGAJwJCZCwzQ8PWo3q+xE7n1RVQx8BggCfUkIj n9AYuoPWlaQmHQQuhI0kg18= =cgo1 -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Monday, February 05, 2007 19:06:06 -0800 Josh Berkus <josh@agliodbs.com> 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-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Monday, February 05, 2007 22:11:37 -0500 Tom Lane <tgl@sss.pgh.pa.us> wrote: > Josh Berkus <josh@agliodbs.com> writes: >> Well, that worked, but it somehow also "unstuck" the previous message. > > A bunch of other recent pgsql-announce messages seem to have come > "unstuck" too ... There were three that I approved: Announce from Josh PWN Announce about ht://Dig + PostgreSQL 8.2.2 ... - ---- 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/en4QvfyHIvDvMRAp74AJwPWyHEWI9Nrl5axq3TOY+QbGXwMgCguL6J uEe4j3ngJNmOuksC6eWJjME= =MMf2 -----END PGP SIGNATURE-----
Tom Lane wrote: > Josh Berkus <josh@agliodbs.com> writes: >> Well, that worked, but it somehow also "unstuck" the previous message. > > A bunch of other recent pgsql-announce messages seem to have come > "unstuck" too ... I got a whole heap of other messages from days gone by on various lists. I wonder if Marc just found the missing posts problem people have reported on and off for a while. Regards, Dave.
On Mon, Feb 05, 2007 at 05:37:23PM -0500, Tom Lane wrote: > Josh Berkus <josh@agliodbs.com> writes: > > I just took a brief survey on IRC and found that 70% of the people there > > didn't get the release announcement. I didn't get it, nor PWN either. > > For that matter, I haven't gotten anything on -announce since December. > > FWIW, it took almost 2 hours to come through to me --- see attached > headers. The delay seems entirely the fault of the postgresql.org to > mx1.hub.org hop. Dunno if that helps diagnose anything. This is not uncommon at all - it happens all the time. Not just for -announce, happens for all the lists. Has been reported many times before. //Magnus
Magnus Hagander wrote:
> On Mon, Feb 05, 2007 at 05:37:23PM -0500, Tom Lane wrote:
>> Josh Berkus <josh@agliodbs.com> writes:
>>> I just took a brief survey on IRC and found that 70% of the people there
>>> didn't get the release announcement. I didn't get it, nor PWN either.
>>> For that matter, I haven't gotten anything on -announce since December.
>> FWIW, it took almost 2 hours to come through to me --- see attached
>> headers. The delay seems entirely the fault of the postgresql.org to
>> mx1.hub.org hop. Dunno if that helps diagnose anything.
>
> This is not uncommon at all - it happens all the time. Not just for
> -announce, happens for all the lists. Has been reported many times
> before.
It has also been complained about on multiple occassions by many
different people.
Joshua D. Drake
>
> //Magnus
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/