Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TvDQY-0007PH-Tt for pgsql-www@arkaria.postgresql.org; Tue, 15 Jan 2013 20:48:11 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1TvDQX-0000zK-Lu for pgsql-www@arkaria.postgresql.org; Tue, 15 Jan 2013 20:48:09 +0000 Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TvDQW-0000yU-N8 for pgsql-www@postgresql.org; Tue, 15 Jan 2013 20:48:08 +0000 Received: from mail-wi0-f178.google.com ([209.85.212.178]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TvDQU-0006j7-La for pgsql-www@postgresql.org; Tue, 15 Jan 2013 20:48:07 +0000 Received: by mail-wi0-f178.google.com with SMTP id hn3so568312wib.11 for ; Tue, 15 Jan 2013 12:48:05 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=N/DHRkrNyZIQ/fRL8anH3G+jYKQWfjT2K6VqsBX8K64=; b=NYD5FAGirg4Nul27QHUum2d3qbmK9GfpMS+78jlvFlDMnV47UDUiy1I71KE/1/8/T0 XWQ4pZb+mVQNUFsseHPBVWzOdFtgyPboVoImSDF/R5gicqltWrgFR3lLOkpTsVMHFi/7 YysPtVSA3nfxt4cIOl7irxlC+09J/VLoe9OgLqBnOKMxHRHJ2Y38QauPlSxAr56cJ5cB C40e4COB5VbrgVu4CkDiYiKxdDua1TebCfWxUiame7iCZxORjh8fpILck/wMrudODGDW 0lSQH22ql7qaX9Xtgb8a9dIlBBZrDyyAqUE55tT3X7Cro8lBGQiz6tsl0qlchcoDlGXz fvXA== MIME-Version: 1.0 Received: by 10.194.235.6 with SMTP id ui6mr144612616wjc.12.1358282885077; Tue, 15 Jan 2013 12:48:05 -0800 (PST) Received: by 10.194.21.7 with HTTP; Tue, 15 Jan 2013 12:48:05 -0800 (PST) In-Reply-To: <2493.1358282742@sss.pgh.pa.us> References: <2493.1358282742@sss.pgh.pa.us> Date: Tue, 15 Jan 2013 21:48:05 +0100 Message-ID: Subject: Re: Bogus duplicate-message complaints from PG mail lists From: Magnus Hagander To: Tom Lane Cc: PostgreSQL WWW Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlATOrdayTW5BdWGHNLic9QVPg6MKwTY1WhjmR/KfSoBnCQLT3JtiLIKpKw/LkWPqAxPcff X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-www Precedence: bulk Sender: pgsql-www-owner@postgresql.org On Tue, Jan 15, 2013 at 9:45 PM, Tom Lane wrote: > Several times over the past couple of days, I have gotten complaints > like the one attached about duplicate message IDs. I can see from my > sendmail daemon's log that I sent only one copy of this, and the > complaint is dated about twenty minutes after the fact, so I'm pretty > sure the duplicate is not of my making. > > Usually when I get this type of thing I can tell from the Received: > lines that it's the fault of some list subscriber's MUA re-submitting > a message to the lists. But the Received: lines in this example and > the last couple don't show that the message has gone anywhere outside > postgresql.org. So I'm thinking it's a recently-introduced glitch in > the mail list server arrangements. Hi! Stefan and Alvaro were looking into this earlier, and it looks like a weird networking issue that we've had for a couple of days into one of our hosting boxes. Exactly what it's coming from is unknown at this point, but it seems to soimetimes cause a connection drop - which yet more sometimes happens in a position where the sending box never gets the acknowledgement that tht email was sent - and thus retries. Hopefully the ycan add some more details to the discussion, but I wanted to throw out a quick "yeah, confirmed, we've seen something is afoot" message. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-www mailing list (pgsql-www@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www