X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Herb Maeder <maeder-cygml AT maeder DOT org>
In-reply-to:	Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com> 's message of Tue, 28 Oct 2008 10:38:21 EDT.
Subject:	Re: Apologies for multiple messages (Please Help!)
Date:	Tue, 28 Oct 2008 13:41:22 -0700
Message-ID:	<67994.1225226482@maeder.org>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On 28 Oct 2008 10:38:21 EDT, Christopher Faylor wrote:
> >>Please correct me if I am wrong, but this type of thing has happened to
> >>the list before, right?  I seem to remember it happening to someone
> >>else a while back, but I cannot find it in the archives at the moment.
> >
> >Sure.  Not allot but it has happened before.  I think Chris usually
> >puts a block on things like this to stop it, if nothing else is
> >possible.
> 
> I do but I was on vacation (in Italy!) last week.  Someone eventually
> notified the overseers mailing list about this.  Someone there *should*
> have been able to block the messsages from arriving.  I don't know if
> that is what happened or if things were fixed on the sending end but
> sending email to either postmaster or overseers will contact the right
> people.

Neither postmaster nor overseers ever responded, AFAIK.

I think the sending end eventually gave up.  I got the bounce message
included at the end of this message, after which the duplicated messages
stopped.  I'm still not sure what was happening under the hood (on either
side) though.

One thing we suspect is that the lack of a Message-ID field in the header
reduces the ability of the receiving side to automatically stop posting
these duplicated messages to the list.

As such, making the Message-ID field a requirement for posting to the
cygwin mailing lists might not be a bad idea.  

FYI, over the last month, the only message that came in without the
Message-ID field (besides my own) was spam.

Herb.


From MAILER-DAEMON Fri Oct 24 21:44:33 2008
Return-Path: <>
Delivered-To: maeder-cygml AT maeder DOT org
Received: (qmail 71304 invoked for bounce); 24 Oct 2008 21:44:33 -0000
Date: 24 Oct 2008 21:44:33 -0000
From: MAILER-DAEMON AT bouncehost
To: maeder-cygml AT maeder DOT org
Subject: failure notice
Status: RO
X-Status: 
X-Keywords:                 
X-UID: 4208

Hi. This is the qmail-send program.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<cygwin AT cygwin DOT com>:
Connected to 209.132.176.174 but connection died. Possible duplicate! (#4.4.2)
I'm not going to try again; this message has been in the queue too long.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -