[Fwd: failure notice]

[Fwd: failure notice]

[Stan Shebs]

I love the irony - can't deliver the original, but the failure
notice works fine... Presumably this is easy to fix. -s

-------- Original Message --------
Subject: failure notice
Date: 7 Jul 2000 15:52:59 -0000
From: MAILER-DAEMON@sourceware.cygnus.com
To: shebs@sources.redhat.com

Hi. This is the qmail-send program at sourceware.cygnus.com.
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.

<xconq-webpages-cvs@sources.redhat.com>:
ezmlm-reject: fatal: List address must be in To: or Cc: (#5.7.0)

--- Below this line is a copy of the message.

Return-Path: <shebs@sources.redhat.com>
Received: (qmail 19661 invoked by uid 94); 7 Jul 2000 15:52:59 -0000
Date: 7 Jul 2000 15:52:59 -0000
Message-ID: <20000707155259.19660.qmail@sourceware.cygnus.com>
From: shebs@sources.redhat.com
To: xconq-webpages-cvs@sources.redhat.com
Subject: htdocs ftp.html

Files modified in the xconq repository. Log entry:

Mention tcl/tk lib download

[Fwd: failure notice]

[Stan Shebs]

I love the irony - can't deliver the original, but the failure
notice works fine... Presumably this is easy to fix. -s

-------- Original Message --------
Subject: failure notice
Date: 7 Jul 2000 15:52:59 -0000
From: MAILER-DAEMON@sourceware.cygnus.com
To: shebs@sources.redhat.com

Hi. This is the qmail-send program at sourceware.cygnus.com.
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.

<xconq-webpages-cvs@sources.redhat.com>:
ezmlm-reject: fatal: List address must be in To: or Cc: (#5.7.0)

--- Below this line is a copy of the message.

Return-Path: <shebs@sources.redhat.com>
Received: (qmail 19661 invoked by uid 94); 7 Jul 2000 15:52:59 -0000
Date: 7 Jul 2000 15:52:59 -0000
Message-ID: <20000707155259.19660.qmail@sourceware.cygnus.com>
From: shebs@sources.redhat.com
To: xconq-webpages-cvs@sources.redhat.com
Subject: htdocs ftp.html

Files modified in the xconq repository. Log entry:

Mention tcl/tk lib download

Re: [Fwd: failure notice]

[Jim Kingdon]

> <xconq-webpages-cvs@sources.redhat.com>:
> ezmlm-reject: fatal: List address must be in To: or Cc: (#5.7.0)

Thanks for the bug report.  Should be fixed now.  Please keep
reporting problems like this (as promptly as possible - I don't start
my new job until Monday and I have relatively little to do with myself
other than sourceware until then).

Technical details: I edited /qmail/lists-cvs/*/editor to add -T to the
ezmlm-reject line.  These ones don't need check-for-listname because
they already have local-mail-only.

Stan: you interested in an xconq game probably today or tomorrow?
Given the current speed of the remote protocol that probably requires
physical proximity, but since I now live in Mountain View, that
shouldn't be hard to arrange.

Re: [Fwd: failure notice]

[Jim Kingdon]

> <xconq-webpages-cvs@sources.redhat.com>:
> ezmlm-reject: fatal: List address must be in To: or Cc: (#5.7.0)

Thanks for the bug report.  Should be fixed now.  Please keep
reporting problems like this (as promptly as possible - I don't start
my new job until Monday and I have relatively little to do with myself
other than sourceware until then).

Technical details: I edited /qmail/lists-cvs/*/editor to add -T to the
ezmlm-reject line.  These ones don't need check-for-listname because
they already have local-mail-only.

Stan: you interested in an xconq game probably today or tomorrow?
Given the current speed of the remote protocol that probably requires
physical proximity, but since I now live in Mountain View, that
shouldn't be hard to arrange.

Re: [Fwd: failure notice]

[Chris Faylor]

Jim,
I just fixed one of these in the cygwin-webpages-cvs mailing list.
I wonder if some of the other cvs mailing lists are similarly affected.

I thought it was best to change the contents outhost to *.sources.redhat.com.
Is that the best way to deal with this for the CVS lists?

cgf

On Fri, Jul 07, 2000 at 12:43:29PM -0400, Jim Kingdon wrote:
>> <xconq-webpages-cvs@sources.redhat.com>:
>> ezmlm-reject: fatal: List address must be in To: or Cc: (#5.7.0)
>
>Thanks for the bug report.  Should be fixed now.  Please keep
>reporting problems like this (as promptly as possible - I don't start
>my new job until Monday and I have relatively little to do with myself
>other than sourceware until then).
>
>Technical details: I edited /qmail/lists-cvs/*/editor to add -T to the
>ezmlm-reject line.  These ones don't need check-for-listname because
>they already have local-mail-only.
>
>Stan: you interested in an xconq game probably today or tomorrow?
>Given the current speed of the remote protocol that probably requires
>physical proximity, but since I now live in Mountain View, that
>shouldn't be hard to arrange.

Re: [Fwd: failure notice]

[Chris Faylor]

Jim,
I just fixed one of these in the cygwin-webpages-cvs mailing list.
I wonder if some of the other cvs mailing lists are similarly affected.

I thought it was best to change the contents outhost to *.sources.redhat.com.
Is that the best way to deal with this for the CVS lists?

cgf

On Fri, Jul 07, 2000 at 12:43:29PM -0400, Jim Kingdon wrote:
>> <xconq-webpages-cvs@sources.redhat.com>:
>> ezmlm-reject: fatal: List address must be in To: or Cc: (#5.7.0)
>
>Thanks for the bug report.  Should be fixed now.  Please keep
>reporting problems like this (as promptly as possible - I don't start
>my new job until Monday and I have relatively little to do with myself
>other than sourceware until then).
>
>Technical details: I edited /qmail/lists-cvs/*/editor to add -T to the
>ezmlm-reject line.  These ones don't need check-for-listname because
>they already have local-mail-only.
>
>Stan: you interested in an xconq game probably today or tomorrow?
>Given the current speed of the remote protocol that probably requires
>physical proximity, but since I now live in Mountain View, that
>shouldn't be hard to arrange.

Re: [Fwd: failure notice]

[Jim Kingdon]

> I just fixed one of these in the cygwin-webpages-cvs mailing list.
> I wonder if some of the other cvs mailing lists are similarly affected.

Ah, *that*'s why one of the outhost files was already updated when I
went to edit them all.  I've updated them all en mase (they were almost
all affected as far as I know).

> I thought it was best to change the contents outhost to *.sources.redhat.com.
> Is that the best way to deal with this for the CVS lists?

Nit: outhost isn't a wildcard, it is a single hostname (it gets put
into the headers in outgoing mail in a few places).  So it is
sources.redhat.com not *.sources.redhat.com.

Changing outhost to sources.redhat.com instead of adding -T to
ezmlm-reject is OK as long as you know that everything which is
sending email has been moved to sources.redhat.com.  If some of the
senders might still be using sourceware.cygnus.com, then the -T (plus
local-mail-only or check-for-listname) solution is how to handle it.

Re: [Fwd: failure notice]

[Jim Kingdon]

> I just fixed one of these in the cygwin-webpages-cvs mailing list.
> I wonder if some of the other cvs mailing lists are similarly affected.

Ah, *that*'s why one of the outhost files was already updated when I
went to edit them all.  I've updated them all en mase (they were almost
all affected as far as I know).

> I thought it was best to change the contents outhost to *.sources.redhat.com.
> Is that the best way to deal with this for the CVS lists?

Nit: outhost isn't a wildcard, it is a single hostname (it gets put
into the headers in outgoing mail in a few places).  So it is
sources.redhat.com not *.sources.redhat.com.

Changing outhost to sources.redhat.com instead of adding -T to
ezmlm-reject is OK as long as you know that everything which is
sending email has been moved to sources.redhat.com.  If some of the
senders might still be using sourceware.cygnus.com, then the -T (plus
local-mail-only or check-for-listname) solution is how to handle it.

Re: [Fwd: failure notice]

[Chris Faylor]

On Fri, Jul 07, 2000 at 09:46:01PM -0400, Jim Kingdon wrote:
>> I just fixed one of these in the cygwin-webpages-cvs mailing list.
>> I wonder if some of the other cvs mailing lists are similarly affected.
>
>Ah, *that*'s why one of the outhost files was already updated when I
>went to edit them all.  I've updated them all en mase (they were almost
>all affected as far as I know).
>
>> I thought it was best to change the contents outhost to *.sources.redhat.com.
>> Is that the best way to deal with this for the CVS lists?
>
>Nit: outhost isn't a wildcard, it is a single hostname (it gets put
>into the headers in outgoing mail in a few places).  So it is
>sources.redhat.com not *.sources.redhat.com.

Yeah, I was just using '*' as a shorthand.

>Changing outhost to sources.redhat.com instead of adding -T to
>ezmlm-reject is OK as long as you know that everything which is
>sending email has been moved to sources.redhat.com.  If some of the
>senders might still be using sourceware.cygnus.com, then the -T (plus
>local-mail-only or check-for-listname) solution is how to handle it.

Yes.  I figured that the cvs mailing lists fell into the former category.

cgf

Re: [Fwd: failure notice]

[Chris Faylor]

On Fri, Jul 07, 2000 at 09:46:01PM -0400, Jim Kingdon wrote:
>> I just fixed one of these in the cygwin-webpages-cvs mailing list.
>> I wonder if some of the other cvs mailing lists are similarly affected.
>
>Ah, *that*'s why one of the outhost files was already updated when I
>went to edit them all.  I've updated them all en mase (they were almost
>all affected as far as I know).
>
>> I thought it was best to change the contents outhost to *.sources.redhat.com.
>> Is that the best way to deal with this for the CVS lists?
>
>Nit: outhost isn't a wildcard, it is a single hostname (it gets put
>into the headers in outgoing mail in a few places).  So it is
>sources.redhat.com not *.sources.redhat.com.

Yeah, I was just using '*' as a shorthand.

>Changing outhost to sources.redhat.com instead of adding -T to
>ezmlm-reject is OK as long as you know that everything which is
>sending email has been moved to sources.redhat.com.  If some of the
>senders might still be using sourceware.cygnus.com, then the -T (plus
>local-mail-only or check-for-listname) solution is how to handle it.

Yes.  I figured that the cvs mailing lists fell into the former category.

cgf

[Fwd: failure notice]

[Mark Mitchell]

[-- Attachment #1: Type: text/plain, Size: 108 bytes --]

Why did this get flagged as spam?

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713

[-- Attachment #2: failure notice --]
[-- Type: message/rfc822, Size: 2160 bytes --]

From: MAILER-DAEMON@mail.codesourcery.com
To: mark@codesourcery.com
Subject: failure notice
Date: 19 Feb 2007 21:11:30 -0000

Hi. This is the qmail-send program at mail.codesourcery.com.
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.

<gcc-patches@gcc.gnu.org>:
209.132.176.174 failed after I sent the message.
Remote host said: 552 spam score exceeded threshold

--- Below this line is a copy of the message.

Return-Path: <mark@codesourcery.com>
Received: (qmail 17209 invoked from network); 19 Feb 2007 21:11:24 -0000
Received: from unknown (HELO ?192.168.0.4?) (mitchell@127.0.0.2)
  by mail.codesourcery.com with ESMTPA; 19 Feb 2007 21:11:24 -0000
Message-ID: <45DA1274.5000800@codesourcery.com>
Date: Mon, 19 Feb 2007 13:11:16 -0800
From: Mark Mitchell <mark@codesourcery.com>
Organization: CodeSourcery, Inc.
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Kazu Hirata <kazu@codesourcery.com>
CC:  gcc-patches@gcc.gnu.org
Subject: Re: [patch] common.opt: Remove -ftree-lrs.
References: <200702172354.l1HNsXgd006908@sparrowhawk.codesourcery.com>
In-Reply-To: <200702172354.l1HNsXgd006908@sparrowhawk.codesourcery.com>
X-Enigmail-Version: 0.94.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Kazu Hirata wrote:

> I am not sure if I should follow the normal deprecation process.
> Please let me know if I should.
> 
> Bootstrapped on i686-pc-linux-gnu.  OK to apply?
> 
> Kazu Hirata
> 
> 2007-02-18  Kazu Hirata  <kazu@codesourcery.com>
> 
> 	* common.opt (-ftree-lrs): Remove.
> 	* doc/invoke.texi (-ftree-lrs): Likewise.

The documentation patch is OK.  However, we should continue to recognize
(and ignore) the option, for backwards compatibility with old Makefiles.

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713

Re: [Fwd: failure notice]

[Christopher Faylor]

Mark Mitchell wrote:
>Why did this get flagged as spam?

That email address was in the spamassassin blacklist.  I'm not sure how
this could have happened but, since your message was flagged as spam on
my system too, I probably added it somehow during one of my many updates
to the blacklist throughout the day.  This may have been due to my
missing a valid email address when adding spam to the bayes
filter/blacklist.

Anyway, you are removed from the black list and added to the white list.
Sorry for the glitch.

cgf

Re: [Fwd: failure notice]

[Mark Mitchell]

Christopher Faylor wrote:
> Mark Mitchell wrote:
>> Why did this get flagged as spam?

> Anyway, you are removed from the black list and added to the white list.

Thanks!

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713

[Fwd: failure notice]

[Corinna Vinschen]

Hi,

can anybody explain this?  The message has been successfully delivered
to the mailing list archive, see

  http://cygwin.com/ml/cygwin-apps/2004-08/msg00099.html

I got the same message already when I've sent this message:

  http://cygwin.com/ml/cygwin-apps/2004-08/msg00095.html

What does that mean?  Is the message now only in the archive but not
sent out to the subscribers?


Corinna

----- Forwarded message from MAILER-DAEMON at sourceware dot org -----
> Date: 18 Aug 2004 16:05:20 -0000
> From: MAILER-DAEMON at sourceware dot org
> Subject: failure notice
> To: vinschen at redhat dot com
> 
> Hi. This is the qmail-send program at sourceware dot org.
> 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-apps at cygwin dot com>:
> ezmlm-send: fatal: message already has a Mailing-List header (maybe I should be a sublist) (#5.7.2)
> 
> --- Enclosed are the original headers of the message.

> Date: Wed, 18 Aug 2004 17:54:09 +0200
> From: Corinna Vinschen <vinschen at redhat dot com>
> Subject: Re: [ANN] Updated: rsync-2.6.2-2
> To: CygWin-Apps <cygwin-apps at cygwin dot com>
> Reply-To: cygwin-apps at cygwin dot com
> 
> (Body suppressed)


----- End forwarded message -----

Re: [Fwd: failure notice]

[Ian Lance Taylor]

Corinna Vinschen <vinschen@redhat.com> writes:

> can anybody explain this?  The message has been successfully delivered
> to the mailing list archive, see
> 
>   http://cygwin.com/ml/cygwin-apps/2004-08/msg00099.html
> 
> I got the same message already when I've sent this message:
> 
>   http://cygwin.com/ml/cygwin-apps/2004-08/msg00095.html
> 
> What does that mean?  Is the message now only in the archive but not
> sent out to the subscribers?

The message did go out to the list--I see it in the ezmlm archives.
If you are on the list, you should have received it.  The headers on
the message in the archive show that the message arrived at sourceware
at 18 Aug 2004 15:53:46 (from the Received header).

The message below arrived at sourceware at 2004-08-18 16:05:11 (from
the qmail logs) and was rejected as shown.

What is strange is that the bounce message is not complete.  It should
have the complete headers, which would help us determine where the
duplicate came from.  The complete headers must include a Mailing-List
header, or the message would not have bounced.  And I don't understand
what emitted the "(Body suppressed)" note.  How did you receive the
bounce message?  Is this a complete copy of it?

Ian

> ----- Forwarded message from MAILER-DAEMON at sourceware dot org -----
> > Date: 18 Aug 2004 16:05:20 -0000
> > From: MAILER-DAEMON at sourceware dot org
> > Subject: failure notice
> > To: vinschen at redhat dot com
> > 
> > Hi. This is the qmail-send program at sourceware dot org.
> > 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-apps at cygwin dot com>:
> > ezmlm-send: fatal: message already has a Mailing-List header (maybe I should be a sublist) (#5.7.2)
> > 
> > --- Enclosed are the original headers of the message.
> 
> > Date: Wed, 18 Aug 2004 17:54:09 +0200
> > From: Corinna Vinschen <vinschen at redhat dot com>
> > Subject: Re: [ANN] Updated: rsync-2.6.2-2
> > To: CygWin-Apps <cygwin-apps at cygwin dot com>
> > Reply-To: cygwin-apps at cygwin dot com
> > 
> > (Body suppressed)
> 
> 
> ----- End forwarded message -----

Re: [Fwd: failure notice]

[Corinna Vinschen]

On Aug 18 13:20, Ian Lance Taylor wrote:
> Corinna Vinschen <vinschen@redhat.com> writes:
> 
> > can anybody explain this?  The message has been successfully delivered
> > to the mailing list archive, see
> > 
> >   http://cygwin.com/ml/cygwin-apps/2004-08/msg00099.html
> > 
> > I got the same message already when I've sent this message:
> > 
> >   http://cygwin.com/ml/cygwin-apps/2004-08/msg00095.html
> > 
> > What does that mean?  Is the message now only in the archive but not
> > sent out to the subscribers?
> 
> The message did go out to the list--I see it in the ezmlm archives.
> If you are on the list, you should have received it.  The headers on
> the message in the archive show that the message arrived at sourceware
> at 18 Aug 2004 15:53:46 (from the Received header).

Yeah, you're right, I got the mail.

> The message below arrived at sourceware at 2004-08-18 16:05:11 (from
> the qmail logs) and was rejected as shown.
> 
> What is strange is that the bounce message is not complete.  It should
> have the complete headers, which would help us determine where the
> duplicate came from.  The complete headers must include a Mailing-List
> header, or the message would not have bounced.  And I don't understand
> what emitted the "(Body suppressed)" note.  How did you receive the
> bounce message?  Is this a complete copy of it?

No, it's not.  Sorry.  I have been hit by the fact that mutt supresses
also header lines in subparts of the message.  The full reply looks as
follows.  Now I see that there was some other server involved, and the
mail has apparently been bounced.  Well, from the spamassassin output
I see that my current dynamic DSL address is listed in some orbs list
but this gives only 0.2 points hit, so that's not the reason for this
bounce.


Corinna

=== SNIP ===
Return-Path: <vinschen@redhat.com>
Received: (qmail 13628 invoked from network); 18 Aug 2004 16:05:10 -0000
Received: from unknown (HELO server.jeroenlandheer.local) (213.46.153.90)
  by sourceware.org with SMTP; 18 Aug 2004 16:05:10 -0000
Received: from server.jeroenlandheer.local ([213.46.153.90]) by server.jeroenlandheer.local with Microsoft SMTPSVC(5.0.2195.6713);
         Wed, 18 Aug 2004 18:01:09 +0200
Received: from server.jeroenlandheer.local ([192.168.4.1]) by server.jeroenlandheer.local with Microsoft SMTPSVC(5.0.2195.6713);
         Wed, 18 Aug 2004 18:01:09 +0200
Received: by server.jeroenlandheer.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
         id MSG08182004-180102-115.MMD@jeroenlandheer.local; Wed, 18 Aug 2004 18:01:02 +0200
Return-path: <cygwin-apps-return-14385-blytkerchan=users.sourceforge.net@cygwin.com>
Envelope-to: ronald@jeroenlandheer.com
Delivery-date: Wed, 18 Aug 2004 08:53:57 -0700
Received: from [66.35.250.206] (helo=sc8-sf-mx1.sourceforge.net)
        by mx.mailix.net with esmtp (Exim 4.24-VA)
        id 1BxSl9-0002P2-Bw
        for ronald@jeroenlandheer.com; Wed, 18 Aug 2004 08:53:55 -0700
Received: from sourceware.org ([12.107.209.250])
        by sc8-sf-mx1.sourceforge.net with smtp (Exim 4.34)
        id 1BxSl7-0002Ne-7D
        for blytkerchan@users.sourceforge.net; Wed, 18 Aug 2004 08:53:54 -0700
Received: (qmail 30690 invoked by alias); 18 Aug 2004 15:53:48 -0000
Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-apps-owner@cygwin.com
List-Unsubscribe: <mailto:cygwin-apps-unsubscribe-blytkerchan=users.sourceforge.net@cygwin.com>
List-Subscribe: <mailto:cygwin-apps-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps@cygwin.com>
List-Help: <mailto:cygwin-apps-help@cygwin.com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps@cygwin.com
Delivered-To: mailing list cygwin-apps@cygwin.com
Received: (qmail 30664 invoked from network); 18 Aug 2004 15:53:46 -0000
Received: from unknown (HELO cygbert.vinschen.de) (80.132.110.8)
  by sourceware.org with SMTP; 18 Aug 2004 15:53:46 -0000
Received: by cygbert.vinschen.de (Postfix, from userid 500)
        id C4FFB57E51; Wed, 18 Aug 2004 17:54:09 +0200 (CEST)
Date: Wed, 18 Aug 2004 17:54:09 +0200
From: Corinna Vinschen <vinschen@redhat.com>
To: CygWin-Apps <cygwin-apps@cygwin.com>
Message-ID: <20040818155409.GN10590@cygbert.vinschen.de>
Reply-To: cygwin-apps@cygwin.com
Mail-Followup-To: CygWin-Apps <cygwin-apps@cygwin.com>
References: <41234183.7080206@lapo.it>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <41234183.7080206@lapo.it>
User-Agent: Mutt/1.4.2i
X-SA-Exim-Mail-From: cygwin-apps-return-14385-blytkerchan=users.sourceforge.net@cygwin.com
Subject: Re: [ANN] Updated: rsync-2.6.2-2
Content-Type: text/plain; charset=us-ascii
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on westvirginia.backend
X-Spam-Report:
        *  0.1 RCVD_IN_SORBS RBL: SORBS: sender is listed in SORBS
        *      [80.132.110.8 listed in dnsbl.sorbs.net]
        *  0.1 RCVD_IN_NJABL RBL: Received via a relay in dnsbl.njabl.org
        *      [80.132.110.8 listed in dnsbl.njabl.org]
X-Spam-Status: No, hits=0.2 required=10.0 tests=RCVD_IN_NJABL,RCVD_IN_SORBS
        autolearn=no version=2.63
X-Spam-Level:
X-SA-Exim-Version: 3.1 (built Thu Oct 23 13:26:47 PDT 2003)
X-SA-Exim-Scanned: Yes
Received-SPF: none (spfquery: domain of cygwin-apps-return-14385-blytkerchan=users.sourceforge.net@cygwin.com does not designate permitted sender hosts) client-ip=66.35.250.206; envelope-from=cygwin-apps-return-14385-blytkerchan=users.sourceforge.net@cygwin.com; helo=;
X-uvscan-result: clean (1BxSl9-0002P2-Bw)
X-OriginalArrivalTime: 18 Aug 2004 16:01:09.0266 (UTC) FILETIME=[93842720:01C4853C]

(Body suppressed)
=== SNAP ===

Corinna

-- 
Corinna Vinschen
Cygwin Co-Project Leader
Red Hat, Inc.

Re: [Fwd: failure notice]

[Ian Lance Taylor]

I have removed the e-mail address blytkerchan@users.sourceforge.net
from the cygwin-apps mailing list, to stop any further mail looping.

Ian

Corinna Vinschen <vinschen@redhat.com> writes:

> On Aug 18 13:20, Ian Lance Taylor wrote:
> > Corinna Vinschen <vinschen@redhat.com> writes:
> > 
> > > can anybody explain this?  The message has been successfully delivered
> > > to the mailing list archive, see
> > > 
> > >   http://cygwin.com/ml/cygwin-apps/2004-08/msg00099.html
> > > 
> > > I got the same message already when I've sent this message:
> > > 
> > >   http://cygwin.com/ml/cygwin-apps/2004-08/msg00095.html
> > > 
> > > What does that mean?  Is the message now only in the archive but not
> > > sent out to the subscribers?
> > 
> > The message did go out to the list--I see it in the ezmlm archives.
> > If you are on the list, you should have received it.  The headers on
> > the message in the archive show that the message arrived at sourceware
> > at 18 Aug 2004 15:53:46 (from the Received header).
> 
> Yeah, you're right, I got the mail.
> 
> > The message below arrived at sourceware at 2004-08-18 16:05:11 (from
> > the qmail logs) and was rejected as shown.
> > 
> > What is strange is that the bounce message is not complete.  It should
> > have the complete headers, which would help us determine where the
> > duplicate came from.  The complete headers must include a Mailing-List
> > header, or the message would not have bounced.  And I don't understand
> > what emitted the "(Body suppressed)" note.  How did you receive the
> > bounce message?  Is this a complete copy of it?
> 
> No, it's not.  Sorry.  I have been hit by the fact that mutt supresses
> also header lines in subparts of the message.  The full reply looks as
> follows.  Now I see that there was some other server involved, and the
> mail has apparently been bounced.  Well, from the spamassassin output
> I see that my current dynamic DSL address is listed in some orbs list
> but this gives only 0.2 points hit, so that's not the reason for this
> bounce.
> 
> 
> Corinna
> 
> === SNIP ===
> Return-Path: <vinschen@redhat.com>
> Received: (qmail 13628 invoked from network); 18 Aug 2004 16:05:10 -0000
> Received: from unknown (HELO server.jeroenlandheer.local) (213.46.153.90)
>   by sourceware.org with SMTP; 18 Aug 2004 16:05:10 -0000
> Received: from server.jeroenlandheer.local ([213.46.153.90]) by server.jeroenlandheer.local with Microsoft SMTPSVC(5.0.2195.6713);
>          Wed, 18 Aug 2004 18:01:09 +0200
> Received: from server.jeroenlandheer.local ([192.168.4.1]) by server.jeroenlandheer.local with Microsoft SMTPSVC(5.0.2195.6713);
>          Wed, 18 Aug 2004 18:01:09 +0200
> Received: by server.jeroenlandheer.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
>          id MSG08182004-180102-115.MMD@jeroenlandheer.local; Wed, 18 Aug 2004 18:01:02 +0200
> Return-path: <cygwin-apps-return-14385-blytkerchan=users.sourceforge.net@cygwin.com>
> Envelope-to: ronald@jeroenlandheer.com
> Delivery-date: Wed, 18 Aug 2004 08:53:57 -0700
> Received: from [66.35.250.206] (helo=sc8-sf-mx1.sourceforge.net)
>         by mx.mailix.net with esmtp (Exim 4.24-VA)
>         id 1BxSl9-0002P2-Bw
>         for ronald@jeroenlandheer.com; Wed, 18 Aug 2004 08:53:55 -0700
> Received: from sourceware.org ([12.107.209.250])
>         by sc8-sf-mx1.sourceforge.net with smtp (Exim 4.34)
>         id 1BxSl7-0002Ne-7D
>         for blytkerchan@users.sourceforge.net; Wed, 18 Aug 2004 08:53:54 -0700
> Received: (qmail 30690 invoked by alias); 18 Aug 2004 15:53:48 -0000
> Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm
> Precedence: bulk
> Sender: cygwin-apps-owner@cygwin.com
> List-Unsubscribe: <mailto:cygwin-apps-unsubscribe-blytkerchan=users.sourceforge.net@cygwin.com>
> List-Subscribe: <mailto:cygwin-apps-subscribe@cygwin.com>
> List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
> List-Post: <mailto:cygwin-apps@cygwin.com>
> List-Help: <mailto:cygwin-apps-help@cygwin.com>, <http://sources.redhat.com/lists.html#faqs>
> Mail-Followup-To: cygwin-apps@cygwin.com
> Delivered-To: mailing list cygwin-apps@cygwin.com
> Received: (qmail 30664 invoked from network); 18 Aug 2004 15:53:46 -0000
> Received: from unknown (HELO cygbert.vinschen.de) (80.132.110.8)
>   by sourceware.org with SMTP; 18 Aug 2004 15:53:46 -0000
> Received: by cygbert.vinschen.de (Postfix, from userid 500)
>         id C4FFB57E51; Wed, 18 Aug 2004 17:54:09 +0200 (CEST)
> Date: Wed, 18 Aug 2004 17:54:09 +0200
> From: Corinna Vinschen <vinschen@redhat.com>
> To: CygWin-Apps <cygwin-apps@cygwin.com>
> Message-ID: <20040818155409.GN10590@cygbert.vinschen.de>
> Reply-To: cygwin-apps@cygwin.com
> Mail-Followup-To: CygWin-Apps <cygwin-apps@cygwin.com>
> References: <41234183.7080206@lapo.it>
> Mime-Version: 1.0
> Content-Disposition: inline
> In-Reply-To: <41234183.7080206@lapo.it>
> User-Agent: Mutt/1.4.2i
> X-SA-Exim-Mail-From: cygwin-apps-return-14385-blytkerchan=users.sourceforge.net@cygwin.com
> Subject: Re: [ANN] Updated: rsync-2.6.2-2
> Content-Type: text/plain; charset=us-ascii
> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on westvirginia.backend
> X-Spam-Report:
>         *  0.1 RCVD_IN_SORBS RBL: SORBS: sender is listed in SORBS
>         *      [80.132.110.8 listed in dnsbl.sorbs.net]
>         *  0.1 RCVD_IN_NJABL RBL: Received via a relay in dnsbl.njabl.org
>         *      [80.132.110.8 listed in dnsbl.njabl.org]
> X-Spam-Status: No, hits=0.2 required=10.0 tests=RCVD_IN_NJABL,RCVD_IN_SORBS
>         autolearn=no version=2.63
> X-Spam-Level:
> X-SA-Exim-Version: 3.1 (built Thu Oct 23 13:26:47 PDT 2003)
> X-SA-Exim-Scanned: Yes
> Received-SPF: none (spfquery: domain of cygwin-apps-return-14385-blytkerchan=users.sourceforge.net@cygwin.com does not designate permitted sender hosts) client-ip=66.35.250.206; envelope-from=cygwin-apps-return-14385-blytkerchan=users.sourceforge.net@cygwin.com; helo=;
> X-uvscan-result: clean (1BxSl9-0002P2-Bw)
> X-OriginalArrivalTime: 18 Aug 2004 16:01:09.0266 (UTC) FILETIME=[93842720:01C4853C]
> 
> (Body suppressed)
> === SNAP ===
> 
> Corinna
> 
> -- 
> Corinna Vinschen
> Cygwin Co-Project Leader
> Red Hat, Inc.

Re: [Fwd: failure notice]

[Ian Lance Taylor]

I have removed the e-mail address blytkerchan@users.sourceforge.net
from the cygwin-apps mailing list, to stop any further mail looping.

Ian

Corinna Vinschen <vinschen@redhat.com> writes:

> On Aug 18 13:20, Ian Lance Taylor wrote:
> > Corinna Vinschen <vinschen@redhat.com> writes:
> > 
> > > can anybody explain this?  The message has been successfully delivered
> > > to the mailing list archive, see
> > > 
> > >   http://cygwin.com/ml/cygwin-apps/2004-08/msg00099.html
> > > 
> > > I got the same message already when I've sent this message:
> > > 
> > >   http://cygwin.com/ml/cygwin-apps/2004-08/msg00095.html
> > > 
> > > What does that mean?  Is the message now only in the archive but not
> > > sent out to the subscribers?
> > 
> > The message did go out to the list--I see it in the ezmlm archives.
> > If you are on the list, you should have received it.  The headers on
> > the message in the archive show that the message arrived at sourceware
> > at 18 Aug 2004 15:53:46 (from the Received header).
> 
> Yeah, you're right, I got the mail.
> 
> > The message below arrived at sourceware at 2004-08-18 16:05:11 (from
> > the qmail logs) and was rejected as shown.
> > 
> > What is strange is that the bounce message is not complete.  It should
> > have the complete headers, which would help us determine where the
> > duplicate came from.  The complete headers must include a Mailing-List
> > header, or the message would not have bounced.  And I don't understand
> > what emitted the "(Body suppressed)" note.  How did you receive the
> > bounce message?  Is this a complete copy of it?
> 
> No, it's not.  Sorry.  I have been hit by the fact that mutt supresses
> also header lines in subparts of the message.  The full reply looks as
> follows.  Now I see that there was some other server involved, and the
> mail has apparently been bounced.  Well, from the spamassassin output
> I see that my current dynamic DSL address is listed in some orbs list
> but this gives only 0.2 points hit, so that's not the reason for this
> bounce.
> 
> 
> Corinna
> 
> === SNIP ===
> Return-Path: <vinschen@redhat.com>
> Received: (qmail 13628 invoked from network); 18 Aug 2004 16:05:10 -0000
> Received: from unknown (HELO server.jeroenlandheer.local) (213.46.153.90)
>   by sourceware.org with SMTP; 18 Aug 2004 16:05:10 -0000
> Received: from server.jeroenlandheer.local ([213.46.153.90]) by server.jeroenlandheer.local with Microsoft SMTPSVC(5.0.2195.6713);
>          Wed, 18 Aug 2004 18:01:09 +0200
> Received: from server.jeroenlandheer.local ([192.168.4.1]) by server.jeroenlandheer.local with Microsoft SMTPSVC(5.0.2195.6713);
>          Wed, 18 Aug 2004 18:01:09 +0200
> Received: by server.jeroenlandheer.local (Microsoft Connector for POP3 Mailboxes 5.00.2195) with SMTP (Global POP3 Download)
>          id MSG08182004-180102-115.MMD@jeroenlandheer.local; Wed, 18 Aug 2004 18:01:02 +0200
> Return-path: <cygwin-apps-return-14385-blytkerchan=users.sourceforge.net@cygwin.com>
> Envelope-to: ronald@jeroenlandheer.com
> Delivery-date: Wed, 18 Aug 2004 08:53:57 -0700
> Received: from [66.35.250.206] (helo=sc8-sf-mx1.sourceforge.net)
>         by mx.mailix.net with esmtp (Exim 4.24-VA)
>         id 1BxSl9-0002P2-Bw
>         for ronald@jeroenlandheer.com; Wed, 18 Aug 2004 08:53:55 -0700
> Received: from sourceware.org ([12.107.209.250])
>         by sc8-sf-mx1.sourceforge.net with smtp (Exim 4.34)
>         id 1BxSl7-0002Ne-7D
>         for blytkerchan@users.sourceforge.net; Wed, 18 Aug 2004 08:53:54 -0700
> Received: (qmail 30690 invoked by alias); 18 Aug 2004 15:53:48 -0000
> Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm
> Precedence: bulk
> Sender: cygwin-apps-owner@cygwin.com
> List-Unsubscribe: <mailto:cygwin-apps-unsubscribe-blytkerchan=users.sourceforge.net@cygwin.com>
> List-Subscribe: <mailto:cygwin-apps-subscribe@cygwin.com>
> List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
> List-Post: <mailto:cygwin-apps@cygwin.com>
> List-Help: <mailto:cygwin-apps-help@cygwin.com>, <http://sources.redhat.com/lists.html#faqs>
> Mail-Followup-To: cygwin-apps@cygwin.com
> Delivered-To: mailing list cygwin-apps@cygwin.com
> Received: (qmail 30664 invoked from network); 18 Aug 2004 15:53:46 -0000
> Received: from unknown (HELO cygbert.vinschen.de) (80.132.110.8)
>   by sourceware.org with SMTP; 18 Aug 2004 15:53:46 -0000
> Received: by cygbert.vinschen.de (Postfix, from userid 500)
>         id C4FFB57E51; Wed, 18 Aug 2004 17:54:09 +0200 (CEST)
> Date: Wed, 18 Aug 2004 17:54:09 +0200
> From: Corinna Vinschen <vinschen@redhat.com>
> To: CygWin-Apps <cygwin-apps@cygwin.com>
> Message-ID: <20040818155409.GN10590@cygbert.vinschen.de>
> Reply-To: cygwin-apps@cygwin.com
> Mail-Followup-To: CygWin-Apps <cygwin-apps@cygwin.com>
> References: <41234183.7080206@lapo.it>
> Mime-Version: 1.0
> Content-Disposition: inline
> In-Reply-To: <41234183.7080206@lapo.it>
> User-Agent: Mutt/1.4.2i
> X-SA-Exim-Mail-From: cygwin-apps-return-14385-blytkerchan=users.sourceforge.net@cygwin.com
> Subject: Re: [ANN] Updated: rsync-2.6.2-2
> Content-Type: text/plain; charset=us-ascii
> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on westvirginia.backend
> X-Spam-Report:
>         *  0.1 RCVD_IN_SORBS RBL: SORBS: sender is listed in SORBS
>         *      [80.132.110.8 listed in dnsbl.sorbs.net]
>         *  0.1 RCVD_IN_NJABL RBL: Received via a relay in dnsbl.njabl.org
>         *      [80.132.110.8 listed in dnsbl.njabl.org]
> X-Spam-Status: No, hits=0.2 required=10.0 tests=RCVD_IN_NJABL,RCVD_IN_SORBS
>         autolearn=no version=2.63
> X-Spam-Level:
> X-SA-Exim-Version: 3.1 (built Thu Oct 23 13:26:47 PDT 2003)
> X-SA-Exim-Scanned: Yes
> Received-SPF: none (spfquery: domain of cygwin-apps-return-14385-blytkerchan=users.sourceforge.net@cygwin.com does not designate permitted sender hosts) client-ip=66.35.250.206; envelope-from=cygwin-apps-return-14385-blytkerchan=users.sourceforge.net@cygwin.com; helo=;
> X-uvscan-result: clean (1BxSl9-0002P2-Bw)
> X-OriginalArrivalTime: 18 Aug 2004 16:01:09.0266 (UTC) FILETIME=[93842720:01C4853C]
> 
> (Body suppressed)
> === SNAP ===
> 
> Corinna
> 
> -- 
> Corinna Vinschen
> Cygwin Co-Project Leader
> Red Hat, Inc.

Re: [Fwd: failure notice]

[Corinna Vinschen]

On Aug 18 13:53, Ian Lance Taylor wrote:
> I have removed the e-mail address blytkerchan@users.sourceforge.net
> from the cygwin-apps mailing list, to stop any further mail looping.

Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Co-Project Leader
Red Hat, Inc.

[Fwd: failure notice]

[Andrew Cagney]

[-- Attachment #1: Type: text/plain, Size: 28 bytes --]

What triggers this?

Andrew

[-- Attachment #2: failure notice --]
[-- Type: message/rfc822, Size: 4042 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 971 bytes --]

Hi. This is the qmail-send program at sources.redhat.com.
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.

<gdb-gnats@sources.redhat.com>:
Sorry, I've been told to reject your posts.
 
If you are not a "spammer", we apologize for the inconvenience.
You can add yourself to the sources.redhat.com "global allow list"
by sending email *from*the*blocked*email*address* to:
  
    global-allow-subscribe-cagney=redhat.com@sources.redhat.com
 
For certain types of blocks, this will enable you to send email without
being subjected to further spam blocking.  This will not allow you to
post to a list if you have been explicitly blocked, if you are posting
an off-topic message, if you are sending an attachment that looks like a
virus, etc.
/Contact postmaster@sources.redhat.com if you have questions about this. (#5.7.2)

--- Enclosed are the original headers of the message.

[-- Attachment #2.1.2: Type: message/rfc822, Size: 1736 bytes --]


(Body suppressed)

Re: [Fwd: failure notice]

[law]

In message <3FB8E7D2.6030203@redhat.com>, Andrew Cagney writes:
 >This is a multi-part message in MIME format.
 >--------------000300030405000306090207
 >Content-Type: text/plain; charset=us-ascii; format=flowed
 >Content-Transfer-Encoding: 7bit
 >
 >What triggers this?
Could be a content issue.  Hard to guess what it might be without any of
the content -- subject lines & message body in particular.  Our spam filters
are pretty aggressive (thank god :-)

jeff

Re: [Fwd: failure notice]

[Andrew Cagney]

> In message <3FB8E7D2.6030203@redhat.com>, Andrew Cagney writes:
>  >This is a multi-part message in MIME format.
>  >--------------000300030405000306090207
>  >Content-Type: text/plain; charset=us-ascii; format=flowed
>  >Content-Transfer-Encoding: 7bit
>  >
>  >What triggers this?
> Could be a content issue.  Hard to guess what it might be without any of
> the content -- subject lines & message body in particular.  Our spam filters
> are pretty aggressive (thank god :-)

I get that all the time.  This:

"Sorry, I've been told to reject your posts."

I believe is new?

Andrew

Re: [Fwd: failure notice]

[Matthew Galgoci]

On Tue, 18 Nov 2003, Andrew Cagney wrote:
> > In message <3FB8E7D2.6030203@redhat.com>, Andrew Cagney writes:
> >  >This is a multi-part message in MIME format.
> >  >--------------000300030405000306090207
> >  >Content-Type: text/plain; charset=us-ascii; format=flowed
> >  >Content-Transfer-Encoding: 7bit
> >  >
> >  >What triggers this?
> > Could be a content issue.  Hard to guess what it might be without any of
> > the content -- subject lines & message body in particular.  Our spam filters
> > are pretty aggressive (thank god :-)
> 
> I get that all the time.  This:
> 
> "Sorry, I've been told to reject your posts."
> 
> I believe is new?

I can see how ac131313 might be seen as a forged random spam by someone just glancing
at headers and quick on the trigger. Or perhaps some spammer has been forging a from of
ac131313@redhat.com. *shrug* I dunno.

It's spam like that this is causing us to look impliment whitelisting of valid @redhat.com 
email addresses at Red Hat.

Anyhow, I'm not sure how the spam filters on sources works, but someone ought to check if andrew's
address somehow got added to a blacklist and possibly whitelist his address.

-- 
Matthew Galgoci
System Administrator
Red Hat, Inc
919.754.3700 x44155

Re: [Fwd: failure notice]

[Ian Lance Taylor]

Matthew Galgoci <mgalgoci@redhat.com> writes:

> It's spam like that this is causing us to look impliment whitelisting of valid @redhat.com 
> email addresses at Red Hat.
> 
> Anyhow, I'm not sure how the spam filters on sources works, but someone ought to check if andrew's
> address somehow got added to a blacklist and possibly whitelist his address.

There is a whitelist already, and the bounce message tells you how to
join it.

However, the global deny list overrides the global allow list.  I'm
not sure why that is.  Chris?

Ian

Re: [Fwd: failure notice]

[Christopher Faylor]

On Tue, Nov 18, 2003 at 11:18:44AM -0500, Ian Lance Taylor wrote:
>Matthew Galgoci <mgalgoci@redhat.com> writes:
>>It's spam like that this is causing us to look impliment whitelisting
>>of valid @redhat.com email addresses at Red Hat.
>>
>>Anyhow, I'm not sure how the spam filters on sources works, but someone
>>ought to check if andrew's address somehow got added to a blacklist and
>>possibly whitelist his address.
>
>There is a whitelist already, and the bounce message tells you how to
>join it.
>
>However, the global deny list overrides the global allow list.  I'm not
>sure why that is.  Chris?

This is so a miscreant can't add themselves to the white list after
being blocked.  I actually had a couple of people try to do this.

I do have vague plans of adding a super-white-list which could not be
overridden by the deny list, though.  Obviously Andrew would be on that
list.  I also need to tighten up the mechanism via which addresses are
automatically added to the black list since a few notables like Michael
Chasttain and Mark Mitchell got added in the last few months when
obviously they shouldn't have been.  It is easy enough to not
automatically add people to the black list who are already on the white
list but I just haven't gotten around to it.

But, actually, I've delayed doing this long enough.  I will add this
functionality this week.  I don't think it would have helped Andrew's
problem, though.  I guess I have to improve the logging for this so that
it is more evident what caused the deny block.

cgf

Re: [Fwd: failure notice]

[Christopher Faylor]

On Tue, Nov 18, 2003 at 09:40:54AM -0500, Andrew Cagney wrote:
>>In message <3FB8E7D2.6030203@redhat.com>, Andrew Cagney writes:
>> >This is a multi-part message in MIME format.
>> >--------------000300030405000306090207
>> >Content-Type: text/plain; charset=us-ascii; format=flowed
>> >Content-Transfer-Encoding: 7bit
>> >
>> >What triggers this?
>>Could be a content issue.  Hard to guess what it might be without any of
>>the content -- subject lines & message body in particular.  Our spam 
>>filters
>>are pretty aggressive (thank god :-)
>
>I get that all the time.  This:
>
>"Sorry, I've been told to reject your posts."
>
>I believe is new?

Something in the From or in the Sender was in the global deny list.  The
global deny list contains a list of email addresses from which we do not
accept email.  I put anyone who sends spam into that list.  I see the
block but I don't understand why it happened since
cagney-BLAH-gnu-BLAH-org is not in the deny list.  The only thing that I
can see that is gdb related that is in the global deny list is:
bug-gdb-BLAH-prep-BLAH-ai-BLAH-mit-BLAH-edu .

This is weird, though, because one message was blocked and another made
it through 21 seconds later from the same user and the same IP address.
So, unless you can explain what the difference is between the two messages
this may have to remain a mystery.

cgf

Re: [Fwd: failure notice]

[Andrew Cagney]

> I get that all the time.  This:
>>
>>"Sorry, I've been told to reject your posts."
>>
>>I believe is new?
> 
> 
> Something in the From or in the Sender was in the global deny list.  The
> global deny list contains a list of email addresses from which we do not
> accept email.  I put anyone who sends spam into that list.  I see the
> block but I don't understand why it happened since
> cagney-BLAH-gnu-BLAH-org is not in the deny list.  The only thing that I
> can see that is gdb related that is in the global deny list is:
> bug-gdb-BLAH-prep-BLAH-ai-BLAH-mit-BLAH-edu .

> This is weird, though, because one message was blocked and another made
> it through 21 seconds later from the same user and the same IP address.
> So, unless you can explain what the difference is between the two messages
> this may have to remain a mystery.

No idea.

I since added myself to the white list.

Andrew

Re: [Fwd: failure notice]

[Christopher Faylor]

On Tue, Nov 18, 2003 at 11:23:14AM -0500, Andrew Cagney wrote:
>>I get that all the time.  This:
>>>
>>>"Sorry, I've been told to reject your posts."
>>>
>>>I believe is new?
>>
>>
>>Something in the From or in the Sender was in the global deny list.  The
>>global deny list contains a list of email addresses from which we do not
>>accept email.  I put anyone who sends spam into that list.  I see the
>>block but I don't understand why it happened since
>>cagney-BLAH-gnu-BLAH-org is not in the deny list.  The only thing that I
>>can see that is gdb related that is in the global deny list is:
>>bug-gdb-BLAH-prep-BLAH-ai-BLAH-mit-BLAH-edu .
>
>>This is weird, though, because one message was blocked and another made
>>it through 21 seconds later from the same user and the same IP address.
>>So, unless you can explain what the difference is between the two messages
>>this may have to remain a mystery.
>
>No idea.
>
>I since added myself to the white list.

"cagney redhat com" has been on the white list since 2003-03-25.
"cagney gnu org" isn't in the white list but it's not in the black list
either and, AFAICT, it never has been.  It looks like "cagney gnu org"
was mentioned in the header.  But, it's still a mystery as to why it was
blocked.

cgf

Re: [Fwd: failure notice]

[Ian Lance Taylor]

Andrew Cagney <ac131313@redhat.com> writes:

> What triggers this?
> 
> Andrew
> From: MAILER-DAEMON@sources.redhat.com
> Subject: failure notice
> To: cagney@redhat.com
> Date: 17 Nov 2003 15:12:29 -0000
> 
> Hi. This is the qmail-send program at sources.redhat.com.
> 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.
> 
> <gdb-gnats@sources.redhat.com>:
> Sorry, I've been told to reject your posts.
>  
> If you are not a "spammer", we apologize for the inconvenience.
> You can add yourself to the sources.redhat.com "global allow list"
> by sending email *from*the*blocked*email*address* to:
>   
>     global-allow-subscribe-cagney=redhat.com@sources.redhat.com
>  
> For certain types of blocks, this will enable you to send email without
> being subjected to further spam blocking.  This will not allow you to
> post to a list if you have been explicitly blocked, if you are posting
> an off-topic message, if you are sending an attachment that looks like a
> virus, etc.
> /Contact postmaster@sources.redhat.com if you have questions about this. (#5.7.2)

The message implies that you got added to the global deny list.  The
easiest way to get added is to send mail to one of various spam-trap
e-mail address.

I just looked, though, and you don't seem to currently be on the
global deny list.  Perhaps somebody already removed you.

Ian

Re: [Fwd: failure notice]

[root]

On Fri, Oct 17, 2003 at 10:40:29AM -0700, Mark Mitchell wrote:
>gcc.gnu.org is rejecting my posts of the GCC 3.3.2 release announcement.
>:-)
>
>I've done the "global override" thing again (although I've done that
>before in the past as well), and it didn't help.
>
>Ideas?

Someone or something added you to the global deny list.  I have removed you.
Btw, if this happens again please:

>Contact gcc-owner@gcc.gnu.org if you have questions about this. (#5.7.2)

since you won't be able to send email to overseers either if you are blocked.

cgf

[Fwd: failure notice]

[Joern Rennecke]

I keep getting failure messages for this specific mail which I sent to
the gcc list some time ago.  It appears that some list relay or news
gateway tries to sumbit the message back to the list.

-------- Original Message --------
Received: from sh-us-ex01.us.w2k.superh.com ([192.168.4.40]) by sh-uk-ex01.uk.w2k.superh.com with Microsoft SMTPSVC(5.0.2195.5329);Tue, 3 Jun 2003 16:29:29 +0100
Received: from smtp.superh.com ([65.219.1.204]) by sh-us-ex01.us.w2k.superh.com with Microsoft SMTPSVC(5.0.2195.5329);Tue, 3 Jun 2003 08:29:28 -0700
Received: from sources.redhat.com (sources.redhat.com [66.187.233.205])by smtp.superh.com (Switch-2.2.0/Switch-2.2.0) with SMTP id h53F9TD20949for <joern.rennecke@superh.com>; Tue, 3 Jun 2003 08:09:29
-0700 (PDT)
Message-Id: <200306031509.h53F9TD20949@smtp.superh.com>
Received: (qmail 29824 invoked for bounce); 3 Jun 2003 15:28:44 -0000
Date: 3 Jun 2003 15:28:44 -0000
From: MAILER-DAEMON@sources.redhat.com
To: joern.rennecke@superh.com
Subject: failure notice
Return-Path: <>
X-OriginalArrivalTime: 03 Jun 2003 15:29:28.0217 (UTC) FILETIME=[EBD19890:01C329E4]

Hi. This is the qmail-send program at sources.redhat.com.
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.

<gcc@gcc.gnu.org>:
ezmlm-send: fatal: message already has a Mailing-List header (maybe I should be a sublist) (#5.7.2)

--- Below this line is a copy of the message.

Return-Path: <joern.rennecke@superh.com>
Received: (qmail 28142 invoked from network); 3 Jun 2003 15:28:15 -0000
Received: from unknown (HELO mike.corpex.com) (195.167.169.39)
  by sources.redhat.com with SMTP; 3 Jun 2003 15:28:15 -0000
Received: from mike by mike.corpex.com with local (Exim 3.36 #1 (Debian))
	id 19ND0I-0002QQ-00
	for <gcc@gcc.gnu.org>; Tue, 03 Jun 2003 15:43:10 +0100
Received: (qmail 13588 invoked by uid 0); 27 May 2003 19:19:25 -0000
MBOX-Line: From gcc.gnu.org!gcc-return-74852-james=westongold.com Tue May 27 20:19:25 2003 remote from mail
Received: from smtp-relay.corpex.com([195.167.168.36]) (7369 bytes) by mail.corpex.com
	via smail with P:esmtp/R:bind_hosts/T:smtp-filter
	(sender: <gcc-return-74852-james=westongold.com@gcc.gnu.org>) 
	id <m19KjCg-0041bDb@mail.corpex.com>
	for <weston1@post.corpex.com>; Tue, 27 May 2003 19:29:42 +0100 (BST)
	(Smail-3.2.0.105 1999-Mar-3 #3 built 1999-Mar-26)
Received: from qmail.corpex.net ([195.167.168.40])
	by smtp-relay.corpex.com with smtp (Exim 3.35 #1 (Debian))
	id 19Kj5W-0004PP-00
	for <weston1@post.corpex.com>; Tue, 27 May 2003 19:22:18 +0100
Received: (qmail 53981 invoked by uid 1009); 22 May 2003 16:47:24 -0000
Delivered-To: james@westongold.com
Received: (qmail 53971 invoked by uid 1009); 22 May 2003 16:47:24 -0000
Received: from sources.redhat.com (66.187.233.205)
  by delivery1.corpex.net with SMTP; 22 May 2003 16:47:24 -0000
Received: (qmail 5278 invoked by alias); 22 May 2003 16:45:06 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:gcc-unsubscribe-james=westongold.com@gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Delivered-To: mailing list gcc@gcc.gnu.org
Received: (qmail 5011 invoked from network); 22 May 2003 16:44:58 -0000
Received: from unknown (HELO ns2.uk.superh.com) (193.128.105.170)
  by sources.redhat.com with SMTP; 22 May 2003 16:44:58 -0000
Received: from sh-uk-ex01.uk.w2k.superh.com (sh-uk-ex01 [192.168.16.17])
	by ns2.uk.superh.com (8.11.6+Sun/8.11.6) with ESMTP id h4MGgjb05868
	for <gcc@gcc.gnu.org>; Thu, 22 May 2003 17:42:47 +0100 (BST)
Received: from superh.com ([192.168.16.50]) by sh-uk-ex01.uk.w2k.superh.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 22 May 2003 17:45:15 +0100
Message-ID: <3ECCFE86.D0C37D89@superh.com>
Date: Thu, 22 May 2003 17:44:54 +0100
From: Joern Rennecke <joern.rennecke@superh.com>
Organization: SuperH UK Ltd.
X-Accept-Language: en
MIME-Version: 1.0
To: gcc@gcc.gnu.org
Subject: RFC: address operand predicates other than address_operand?
Content-Type: multipart/mixed;
 boundary="------------93061F5FE477CE79FB375027"
X-OriginalArrivalTime: 22 May 2003 16:45:15.0783 (UTC) FILETIME=[856C1970:01C32081]

This is a multi-part message in MIME format.
--------------93061F5FE477CE79FB375027
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I think it would make sense to have predicates that
already enforce some of the restrictions that an
EXTRA_ADDRESS_CONSTRAINT places on address.
So, we could either have a target macro that describes
a list of address operand predicates, or one that
recognizes address operand predicates, or have a convention
for predicate names that are generally recognized as
address operand predicates.
Note that such a new target macro would not be in the way
of run-time switching the target, as it is used to generate
the recognizer, which is inherently target-specific, and would
have to be switched anyway.
OTOH, having a convention for predicate names seems simpler
both in implementation and in making for more uniform target
descriptions.  We could just say that every predicate that
contains the substring "address_opeerand" is an address_operand
predicate.  This is pretty easy to implement, as the attached
patch shows.  If there is agreement that this is the way to
go, I'll write up a ChangeLog entry and documentation patch
for it.

-- 
--------------------------
SuperH (UK) Ltd.
2410 Aztec West / Almondsbury / BRISTOL / BS32 4QX
T:+44 1454 465658
--------------93061F5FE477CE79FB375027
Content-Type: text/plain; charset=us-ascii;
 name="address-operand-patch-2"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="address-operand-patch-2"

Index: genrecog.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/genrecog.c,v
retrieving revision 1.125
diff -p -r1.125 genrecog.c
*** genrecog.c	17 May 2003 01:40:41 -0000	1.125
--- genrecog.c	22 May 2003 16:32:25 -0000
*************** validate_pattern (pattern, insn, set, se
*** 623,629 ****
  	    && allows_non_const
  	    && ! special_mode_pred
  	    && pred_name[0] != '\0'
! 	    && strcmp (pred_name, "address_operand") != 0
  	    && strstr (c_test, "operands") == NULL
  	    && ! (set
  		  && GET_CODE (set) == SET
--- 623,629 ----
  	    && allows_non_const
  	    && ! special_mode_pred
  	    && pred_name[0] != '\0'
! 	    && strstr (pred_name, "address_operand") == NULL
  	    && strstr (c_test, "operands") == NULL
  	    && ! (set
  		  && GET_CODE (set) == SET
*************** validate_pattern (pattern, insn, set, se
*** 667,673 ****
  	/* The mode of an ADDRESS_OPERAND is the mode of the memory
  	   reference, not the mode of the address.  */
  	if (GET_CODE (src) == MATCH_OPERAND
! 	    && ! strcmp (XSTR (src, 1), "address_operand"))
  	  ;
  
          /* The operands of a SET must have the same mode unless one
--- 667,673 ----
  	/* The mode of an ADDRESS_OPERAND is the mode of the memory
  	   reference, not the mode of the address.  */
  	if (GET_CODE (src) == MATCH_OPERAND
! 	    && strstr (XSTR (src, 1), "address_operand") == NULL)
  	  ;
  
          /* The operands of a SET must have the same mode unless one
*************** add_to_sequence (pattern, last, position
*** 868,876 ****
  
  	       If we know that the predicate does not allow CONST_INT,
  	       we know that the only way the predicate can match is if
! 	       the modes match (here we use the kludge of relying on the
! 	       fact that "address_operand" accepts CONST_INT; otherwise,
! 	       it would have to be a special case), so we can test the
  	       mode (but we need not).  This fact should considerably
  	       simplify the generated code.  */
  
--- 868,876 ----
  
  	       If we know that the predicate does not allow CONST_INT,
  	       we know that the only way the predicate can match is if
! 	       the modes match (here we used to use the kludge of relying
! 	       on "address_operand" accepting CONST_INT, but that is not
! 	       true for all architectures), so we can test the
  	       mode (but we need not).  This fact should considerably
  	       simplify the generated code.  */
  
*************** add_to_sequence (pattern, last, position
*** 900,906 ****
  	  }
  
  	/* Can't enforce a mode if we allow const_int.  */
! 	if (allows_const_int)
  	  mode = VOIDmode;
  
  	/* Accept the operand, ie. record it in `operands'.  */
--- 900,908 ----
  	  }
  
  	/* Can't enforce a mode if we allow const_int.  */
! 	if (allows_const_int
! 	    || (GET_CODE (pattern) == MATCH_OPERAND
! 		&& strstr (XSTR (pattern, 1), "address_operand") != NULL))
  	  mode = VOIDmode;
  
  	/* Accept the operand, ie. record it in `operands'.  */
*************** maybe_both_true_2 (d1, d2)
*** 1111,1117 ****
  		     mode of the memory, not the operand.  It can only
  		     be used for testing the predicate, so we must
  		     ignore it here.  */
! 		  && strcmp (d1->u.pred.name, "address_operand") != 0)
  		return 0;
  	    }
  	  /* Don't check two predicate modes here, because if both predicates
--- 1113,1119 ----
  		     mode of the memory, not the operand.  It can only
  		     be used for testing the predicate, so we must
  		     ignore it here.  */
! 		  && strstr (d1->u.pred.name, "address_operand") == NULL)
  		return 0;
  	    }
  	  /* Don't check two predicate modes here, because if both predicates

--------------93061F5FE477CE79FB375027--

[Fwd: failure notice]

[Robert Love]

Sorry - more annoyance.

Looks like the CVS web commits alias is not set up.

I do not care whether it is or not... but its broken as-is.

	Robert Love

-----Forwarded Message-----

> From: MAILER-DAEMON@sources.redhat.com
> To: rml@sources.redhat.com
> Subject: failure notice
> Date: 01 Feb 2003 02:26:47 +0000
> 
> Hi. This is the qmail-send program at sources.redhat.com.
> 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.
> 
> <procps-webpages-cvs@sources.redhat.com>:
> Sorry, no mailbox here by that name. (#5.1.1)
> 
> --- Below this line is a copy of the message.
> 
> Return-Path: <rml@sources.redhat.com>
> Received: (qmail 10678 invoked by uid 9360); 1 Feb 2003 02:26:47 -0000
> Date: 1 Feb 2003 02:26:47 -0000
> Message-ID: <20030201022647.10677.qmail@sources.redhat.com>
> From: rml@sources.redhat.com
> To: procps-webpages-cvs@sources.redhat.com
> Subject: htdocs index.html
> 
> Files modified in the procps repository. Log entry:
> 
> silly webpage

Re: [Fwd: failure notice]

[Christopher Faylor]

On Fri, Jan 31, 2003 at 09:32:18PM -0500, Robert Love wrote:
>Sorry - more annoyance.
>
>Looks like the CVS web commits alias is not set up.
>
>I do not care whether it is or not... but its broken as-is.

I just turned it off (I hope).  If this becomes a problem we can set up
the mailing list but it didn't seem like it was worth the effort right
now.

cgf

[Fwd: failure notice]

[Ulrich Drepper]

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Could somebody look at the message at the beginning of the mail?  Some
program/script seems to be missing.

I've also gotten complaints about the message sourceware sends out in
response to a non-authorized posting to a closed mailing list.  It's
said to be less then useful and misleading or even wrong.  Where is the
reply configured?

Thanks,

- --
- ---------------.                          ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE9XcCw2ijCOnn/RHQRAiiiAKCCE1G7R3S7oaap32D9HFtlE9Z4IwCfaDHg
w4Kcx5YQZVPhWPBGdnmHmww=
=t/kc
-----END PGP SIGNATURE-----

[-- Attachment #2: failure notice --]
[-- Type: message/rfc822, Size: 3935 bytes --]

From: MAILER-DAEMON@sources.redhat.com
To: drepper@redhat.com
Subject: failure notice
Date: 17 Aug 2002 03:07:28 -0000
Message-ID: <200208170253.g7H2rVl09333@mx1.redhat.com>

Hi. This is the qmail-send program at sources.redhat.com.
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.

<drepper@sources.redhat.com>:
/bin/sh: sourceware/infra/bin/mlcheck: No such file or directory
I'm not going to try again; this message has been in the queue too long.

--- Below this line is a copy of the message.

Return-Path: <drepper@redhat.com>
Received: (qmail 17839 invoked by alias); 10 Aug 2002 02:07:27 -0000
Delivered-To: libc-hacker-owner@sources.redhat.com
Received: (qmail 17834 invoked from network); 10 Aug 2002 02:07:26 -0000
Received: from unknown (HELO myware.mynet) (24.221.190.179)
  by sources.redhat.com with SMTP; 10 Aug 2002 02:07:26 -0000
Received: from redhat.com (myware.mynet [192.168.7.70])
	(authenticated bits=0)
	by myware.mynet (8.12.3/8.12.3) with ESMTP id g7A277To008349;
	Fri, 9 Aug 2002 19:07:07 -0700
Message-ID: <3D547546.9030301@redhat.com>
Date: Fri, 09 Aug 2002 19:07:02 -0700
From: Ulrich Drepper <drepper@redhat.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020808
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Thomas Bushnell, BSG" <tb@becket.net>
CC: libc-hacker-owner@sources.redhat.com, drepper@cygnus.com, roland@gnu.org
Subject: Re: [MAILER-DAEMON@sources.redhat.com] failure notice
References: <87eldgrjm9.fsf@becket.becket.net>
X-Enigmail-Version: 0.65.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thomas Bushnell, BSG wrote:
> I think I'm on the libc-hacker list as "thomas@gnu.org".  But it might
> also be tb@mit.edu or tb@becket.net.  Regardless, it should be
> tb@becket.net.  Can you please fix it?

I cannot.  But you can send aliases.  The ezmlm manual explains how.

   http://www.de.ezmlm.org/ezman-0.32/ezman1.html#ss1.2

I think it's

   libc-hacker-allow-subscribe-tb=becket.net@sources.redhat.com

what you should use.

- -- 
- ---------------.                          ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE9VHVL2ijCOnn/RHQRAiIAAKC9wkORvtH2dGiwrcd8g65c5F/RiACbBt1m
B7dcu9j8P4KQqcb87H8awNM=
=cctz
-----END PGP SIGNATURE-----

Re: [Fwd: failure notice]

[Christopher Faylor]

On Fri, Aug 16, 2002 at 08:19:12PM -0700, Ulrich Drepper wrote:
>Could somebody look at the message at the beginning of the mail?  Some
>program/script seems to be missing.

It's in ~drepper/.qmail .

I've been slowly changing people over to the new spam blocking system
from the old and I must have screwed up your email forwarding.

I'm very sorry about that.  It's fixed now.

cgf

[Fwd: failure notice]

[Joel Sherrill]

[-- Attachment #1: Type: text/plain, Size: 470 bytes --]


Hi,

I know it looks like GNATS days are numbered but just out of curiousity
why does the "send email to interested parties" link include 
two email addresses that don't work -- nobody@gcc.gnu.org and
gcc-prs@gcc.gnu.org.  

Thanks.

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel@OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985

[-- Attachment #2: Type: message/rfc822, Size: 2888 bytes --]

From: MAILER-DAEMON@sources.redhat.com
To: joel.sherrill@OARcorp.com
Subject: failure notice
Date: 5 Mar 2002 12:14:49 -0000

Hi. This is the qmail-send program at sources.redhat.com.
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.

<gcc-prs@gcc.gnu.org>:
Sender: joel.sherrill@OARcorp.com
This mailing list is not for general discussions.  Please resend your
mail note to a more appropriate list.


--- Below this line is a copy of the message.

Return-Path: <joel.sherrill@OARcorp.com>
Received: (qmail 8719 invoked from network); 5 Mar 2002 12:14:40 -0000
Received: from unknown (HELO imf26bis.bellsouth.net) (205.152.58.86)
  by sources.redhat.com with SMTP; 5 Mar 2002 12:14:40 -0000
Received: from OARcorp.com ([66.20.69.46]) by imf26bis.bellsouth.net
          (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with ESMTP
          id <20020305121601.GETM7463.imf26bis.bellsouth.net@OARcorp.com>;
          Tue, 5 Mar 2002 07:16:01 -0500
Message-ID: <3C84B6D7.2B2986D4@OARcorp.com>
Date: Tue, 05 Mar 2002 06:15:19 -0600
From: Joel Sherrill <joel.sherrill@OARcorp.com>
Reply-To: joel.sherrill@OARcorp.com
Organization: OAR Corporation
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: joel.sherrill@oarcorp.com, gcc-gnats@gcc.gnu.org,
 	gcc-prs@gcc.gnu.org, eric.norum@usask.ca, gcc-bugs@gcc.gnu.org,
 	Jan Hubicka <jh@suse.cz>, rth@redhat.com
Subject: Re: c/5707: i386 compiler can't build libgcc2.c with -msoft-float
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Eric sent me email privately confirming that PR5707 is present on 
i386-linux-gcc as well as on i386-rtems-gcc.  It's the -msoft-float that 
causes the problem.  When we tried adding -msoft-float as a multilib
to the i386-elf target in the past, it has broken as well.  This is 
on the main line CVS and a regression from 3.0.4.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5707

Richard/Jan could you try this out and take a stab at fixing it?  This
is a real pain for the embedded community using i386dx/ex and 486sx 
derived CPUs.  

Thanks.

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel@OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985

Re: [Fwd: failure notice]

[Andrew Cagney]

> I know it looks like GNATS days are numbered but just out of curiousity
> why does the "send email to interested parties" link include 
> two email addresses that don't work -- nobody@gcc.gnu.org and
> gcc-prs@gcc.gnu.org.  

I was wondering the same thing.

Andrew

> Hello,
> 
> I'm finding that (using mozilla?) clicking on the link leads to:
> 
>     To: nobody@sources.redhat.com
>     To: <submitter>
>     To: gdb-gnats@sources.redhat.com
>     To: gdb-prs@sources.redhat.com?Subject=Re:
>     To: gdb/359
> 
> Two questions.  Is that a typo or a mozilla bug?  Which of the above (gdb-gnats or gdb-prs) should it be CC'd to (I can never remember am so updating the GDB web page with the correct info)?

I've figured out it should go to gdb-gnats@.

> enjoy,
> Andrew
> 

[Fwd: failure notice]

[Jonathan Larmour]

I've been getting a fair number of bounces recently with this problem. Any
ideas why? As far as I know, there's nothing special about this mail as
opposed to any of the many others I send to the eCos list.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine


To : jlarmour at redhat dot com
Subject : failure notice
From : MAILER-DAEMON at sourceware dot cygnus dot com
Date : 23 Apr 2001 00:29:30 -0000

Hi. This is the qmail-send program at sourceware.cygnus.com.
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.

<ecos-discuss@sources.redhat.com>:
ezmlm-send: fatal: message already has a Mailing-List header (maybe I should be a sublist) (#5.7.2)

--- Below this line is a copy of the message.

Return-Path: <jlarmour@redhat.com>
Received: (qmail 14965 invoked from network); 23 Apr 2001 00:29:28 -0000
Received: from unknown (HELO china.com) (202.106.182.13)
  by sourceware.cygnus.com with SMTP; 23 Apr 2001 00:29:28 -0000
Received: from china.com([10.1.0.100]) by china.com(AIMC 2.9.5.1)
	with SMTP id jm93ae37d8d; Mon, 23 Apr 2001 08:26:10 +0800
Received: from sourceware.cygnus.com([205.180.83.71]) by china.com(AIMC 2.9.5.1)
	with SMTP id jm2213ae2e765; Sun, 22 Apr 2001 17:23:43 +0800
Received: (qmail 23587 invoked by alias); 20 Apr 2001 09:23:28 -0000
Mailing-List: contact ecos-discuss-help@sourceware.cygnus.com; run by ezmlm
Precedence: bulk
List-Unsubscribe: < mailto:ecos-discuss-unsubscribe-zhongtao=china.com@sources.redhat.com >
List-Subscribe: < mailto:ecos-discuss-subscribe@sources.redhat.com >
List-Archive: < http://sources.redhat.com/ml/ecos-discuss/ >
List-Post: < mailto:ecos-discuss@sources.redhat.com >
List-Help: < mailto:ecos-discuss-help@sources.redhat.com >, < http://sources.redhat.com/ml/#faqs >
Sender: ecos-discuss-owner@sources.redhat.com
Delivered-To: mailing list ecos-discuss@sources.redhat.com
Received: (qmail 23534 invoked from network); 20 Apr 2001 09:23:25 -0000
Received: from unknown (HELO executor.cambridge.redhat.com) (195.224.55.237)
  by sourceware.cygnus.com with SMTP; 20 Apr 2001 09:23:25 -0000
Received: from redhat.com (murgh.cambridge.redhat.com [172.16.18.70])
	by executor.cambridge.redhat.com (Postfix) with ESMTP
	id D65A9ABAF7; Fri, 20 Apr 2001 10:23:21 +0100 (BST)
Message-ID: <3AE00009.2BC3F600@redhat.com>
Date: Fri, 20 Apr 2001 10:23:21 +0100
From: Jonathan Larmour <jlarmour@redhat.com>
Organization: Red Hat UK Ltd.
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.17-14enterprise i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Andrea Acquaviva <aacquaviva@deis.unibo.it>
Cc: "ecos-discuss@sources.redhat.com" <ecos-discuss@sources.redhat.com>
References: <3ADFFA65.CC964CFF@deis.unibo.it>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [ECOS]thread switch frequency
X-Auto-Forward: zhongtao@china.com
 zhongtao@mail.sc.cninfo.net

Andrea Acquaviva wrote:
> 
> Hi,
> I have a question about eCos mlqueue scheduler.
> If there are two threads (making a matrix multiplication), running with
> the same priority, they switch with a frequency given by:
> 
> f_clock/CYGNUM_KERNEL_SCHED_TIMESLICE_TICKS,
> 
> where f_clock in the case of strongarm1110 (assabet) is 3.6864MHz.
> 
> Is this correct or is there something else that affects the switching
> frequency?

The timer that drives the kernel clock interrupt is at 3.6864MHz yes, but
it is has been programmed to only actually interrupt when its counter
reaches 36864, which corresponds to every 10ms. And only 1 in
CYGNUM_KERNEL_SCHED_TIMESLICE_TICKS of those causes a timeslice.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

Re: [Fwd: failure notice]

[Jonathan Larmour]

Jonathan Larmour wrote:
> 
> I've been getting a fair number of bounces recently with this problem. Any
> ideas why? As far as I know, there's nothing special about this mail as
> opposed to any of the many others I send to the eCos list.

And I've just seen what the problem is now on rereading. Sigh. I didn't see
the separate batch of Received: headers.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

[Fwd: failure notice]

[Jonathan Larmour]

Have a look at the attached mail bounce. As you can see it is a bit odd -
the CC line is listed twice and it is only the second one that gives the
list address. And even then the list address is sourceware.cygnus, not
sources.redhat.

Any ideas what was the problem here? I had a look on sources.redhat, but
couldn't find anything and I don't have read access to the most interesting
parts of qmail to find out.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault


To : Jonathan Larmour <jlarmour at redhat dot com>
Subject : RE: failure notice
From : Gary Thomas <gthomas at redhat dot com>
Date : Wed, 30 Aug 2000 11:29:49 -0600 (MDT)

This is pretty bogus.  Any idea how we can get it fixed?

On 30-Aug-2000 MAILER-DAEMON@sourceware.cygnus.com wrote:
> Hi. This is the qmail-send program at sourceware.cygnus.com.
> 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.
> 
> <ecos-discuss@sourceware.cygnus.com>:
>  
>   Mail note rejected:  List address must be in To: or Cc: headers.
>  
> 
> --- Below this line is a copy of the message.
> 
> Return-Path: <gthomas@redhat.com>
> Received: (qmail 17750 invoked from network); 30 Aug 2000 16:52:06 -0000
> Received: from dns.cygnus.co.uk (HELO pasanda.cygnus.co.uk) (194.130.39.3)
>   by sourceware.cygnus.com with SMTP; 30 Aug 2000 16:52:06 -0000
> Received: (qmail 8555 invoked by alias); 30 Aug 2000 16:52:03 -0000
> Received: (qmail 8546 invoked from network); 30 Aug 2000 16:52:01 -0000
> Received: from cse.cygnus.com (HELO ares.chez-thomas.org) (205.180.230.236)
>   by dns.cygnus.co.uk with SMTP; 30 Aug 2000 16:52:01 -0000
> Message-ID: <XFMail.20000830105157.gthomas@redhat.com>
> X-Mailer: XFMail 1.4.6 on Linux
> X-Priority: 3 (Normal)
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 8bit
> MIME-Version: 1.0
> In-Reply-To: <1943-144@arm.com>
> X-printer-x: mailto:g.thomas@opengroup.org
> Date: Wed, 30 Aug 2000 10:51:57 -0600 (MDT)
> Sender: gary@ares.chez-thomas.org
> From: Gary Thomas <gthomas@redhat.com>
> To: Andreas.Karlsson@combitechsystems.com
> Subject: RE: [aeb] downloading a program
> Cc: ARM Evaluation Board - List Server <aeb@arm.com>,
> Cc: ARM Evaluation Board - List Server <aeb@arm.com>,
>   eCos Discussion <ecos-discuss@sourceware.cygnus.com>
> 
> 
> On 30-Aug-2000 Andreas.Karlsson@combitechsystems.com wrote:
>> I'm trying to download my uuencoded program into AEB and the start it. This
>> happens. 
>> 
>> 
>> 
>> Boot: download
>> 
>> Ready to download. Use 'transmit' option on terminal emulator to download
>> file.
>> 
>> Loaded file TESTPROG.EXE at address 00008000, size = 1125378
>> 
>> Boot: go
>> 
>> $O526573657420485720626F6172642E2E2E2E2E0A#DF
>> 
>> 
>> 
>> 
>> 
>> Why don't it start?
> 
> It did.  You downloaded an eCos application (I know, I saw your other
> questions) which by default is expecting to talk with GDB.  If you want
> to see the output directly, without GDB, you need to configure your
> program to work that way.
> 

[Fwd: failure notice]

[Jonathan Larmour]

Have a look at the attached mail bounce. As you can see it is a bit odd -
the CC line is listed twice and it is only the second one that gives the
list address. And even then the list address is sourceware.cygnus, not
sources.redhat.

Any ideas what was the problem here? I had a look on sources.redhat, but
couldn't find anything and I don't have read access to the most interesting
parts of qmail to find out.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault


To : Jonathan Larmour <jlarmour at redhat dot com>
Subject : RE: failure notice
From : Gary Thomas <gthomas at redhat dot com>
Date : Wed, 30 Aug 2000 11:29:49 -0600 (MDT)

This is pretty bogus.  Any idea how we can get it fixed?

On 30-Aug-2000 MAILER-DAEMON@sourceware.cygnus.com wrote:
> Hi. This is the qmail-send program at sourceware.cygnus.com.
> 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.
> 
> <ecos-discuss@sourceware.cygnus.com>:
>  
>   Mail note rejected:  List address must be in To: or Cc: headers.
>  
> 
> --- Below this line is a copy of the message.
> 
> Return-Path: <gthomas@redhat.com>
> Received: (qmail 17750 invoked from network); 30 Aug 2000 16:52:06 -0000
> Received: from dns.cygnus.co.uk (HELO pasanda.cygnus.co.uk) (194.130.39.3)
>   by sourceware.cygnus.com with SMTP; 30 Aug 2000 16:52:06 -0000
> Received: (qmail 8555 invoked by alias); 30 Aug 2000 16:52:03 -0000
> Received: (qmail 8546 invoked from network); 30 Aug 2000 16:52:01 -0000
> Received: from cse.cygnus.com (HELO ares.chez-thomas.org) (205.180.230.236)
>   by dns.cygnus.co.uk with SMTP; 30 Aug 2000 16:52:01 -0000
> Message-ID: <XFMail.20000830105157.gthomas@redhat.com>
> X-Mailer: XFMail 1.4.6 on Linux
> X-Priority: 3 (Normal)
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 8bit
> MIME-Version: 1.0
> In-Reply-To: <1943-144@arm.com>
> X-printer-x: mailto:g.thomas@opengroup.org
> Date: Wed, 30 Aug 2000 10:51:57 -0600 (MDT)
> Sender: gary@ares.chez-thomas.org
> From: Gary Thomas <gthomas@redhat.com>
> To: Andreas.Karlsson@combitechsystems.com
> Subject: RE: [aeb] downloading a program
> Cc: ARM Evaluation Board - List Server <aeb@arm.com>,
> Cc: ARM Evaluation Board - List Server <aeb@arm.com>,
>   eCos Discussion <ecos-discuss@sourceware.cygnus.com>
> 
> 
> On 30-Aug-2000 Andreas.Karlsson@combitechsystems.com wrote:
>> I'm trying to download my uuencoded program into AEB and the start it. This
>> happens. 
>> 
>> 
>> 
>> Boot: download
>> 
>> Ready to download. Use 'transmit' option on terminal emulator to download
>> file.
>> 
>> Loaded file TESTPROG.EXE at address 00008000, size = 1125378
>> 
>> Boot: go
>> 
>> $O526573657420485720626F6172642E2E2E2E2E0A#DF
>> 
>> 
>> 
>> 
>> 
>> Why don't it start?
> 
> It did.  You downloaded an eCos application (I know, I saw your other
> questions) which by default is expecting to talk with GDB.  If you want
> to see the output directly, without GDB, you need to configure your
> program to work that way.
> 

Re: [Fwd: failure notice]

[Jason Molenda]

On Wed, Aug 30, 2000 at 07:12:19PM +0100, Jonathan Larmour wrote:

> Any ideas what was the problem here? I had a look on sources.redhat, but
> couldn't find anything and I don't have read access to the most interesting
> parts of qmail to find out.

I think they converted all of the list-name blocking to use that script
I wrote for gcc earlier this year (infra/bin/check-for-listname.sh I think).
I bet it doesn't handle a double-Cc or double-To correctly (I don't know
if this is even legal, although it's clear that the MTA did try to send
it to ecos-discuss).


> > To: Andreas.Karlsson@combitechsystems.com
> > Subject: RE: [aeb] downloading a program
> > Cc: ARM Evaluation Board - List Server <aeb@arm.com>,
> > Cc: ARM Evaluation Board - List Server <aeb@arm.com>,
> >   eCos Discussion <ecos-discuss@sourceware.cygnus.com>
> > 


J

Re: [Fwd: failure notice]

[Jason Molenda]

On Wed, Aug 30, 2000 at 07:12:19PM +0100, Jonathan Larmour wrote:

> Any ideas what was the problem here? I had a look on sources.redhat, but
> couldn't find anything and I don't have read access to the most interesting
> parts of qmail to find out.

I think they converted all of the list-name blocking to use that script
I wrote for gcc earlier this year (infra/bin/check-for-listname.sh I think).
I bet it doesn't handle a double-Cc or double-To correctly (I don't know
if this is even legal, although it's clear that the MTA did try to send
it to ecos-discuss).


> > To: Andreas.Karlsson@combitechsystems.com
> > Subject: RE: [aeb] downloading a program
> > Cc: ARM Evaluation Board - List Server <aeb@arm.com>,
> > Cc: ARM Evaluation Board - List Server <aeb@arm.com>,
> >   eCos Discussion <ecos-discuss@sourceware.cygnus.com>
> > 


J

Re: [Fwd: failure notice]

[Jason Molenda]

On Wed, Aug 30, 2000 at 11:30:53AM -0700, Jason Molenda wrote:

> I think they converted all of the list-name blocking to use that script
> I wrote for gcc earlier this year (infra/bin/check-for-listname.sh I think).
> I bet it doesn't handle a double-Cc or double-To correctly 


PS-  Jonathan, I bestow upon you the FREEDOM TO INNOVATE.  If you really
     want this fixed, the shell script is in the /cvs/sourceware repository.
     I don't imagine it'll be all that difficult to throw a loop around the
     listname check, but you have to be careful that the script is correct -
     a bug in this script will stop all e-mail to sourceware/gcc lists.

Re: [Fwd: failure notice]

[Jason Molenda]

On Wed, Aug 30, 2000 at 11:30:53AM -0700, Jason Molenda wrote:

> I think they converted all of the list-name blocking to use that script
> I wrote for gcc earlier this year (infra/bin/check-for-listname.sh I think).
> I bet it doesn't handle a double-Cc or double-To correctly 


PS-  Jonathan, I bestow upon you the FREEDOM TO INNOVATE.  If you really
     want this fixed, the shell script is in the /cvs/sourceware repository.
     I don't imagine it'll be all that difficult to throw a loop around the
     listname check, but you have to be careful that the script is correct -
     a bug in this script will stop all e-mail to sourceware/gcc lists.

Re: [Fwd: failure notice]

[Chris Faylor]

On Wed, Aug 30, 2000 at 12:03:23PM -0700, Jason Molenda wrote:
>On Wed, Aug 30, 2000 at 11:30:53AM -0700, Jason Molenda wrote:
>
>> I think they converted all of the list-name blocking to use that script
>> I wrote for gcc earlier this year (infra/bin/check-for-listname.sh I think).
>> I bet it doesn't handle a double-Cc or double-To correctly 
>
>
>PS-  Jonathan, I bestow upon you the FREEDOM TO INNOVATE.  If you really
>     want this fixed, the shell script is in the /cvs/sourceware repository.
>     I don't imagine it'll be all that difficult to throw a loop around the
>     listname check, but you have to be careful that the script is correct -
>     a bug in this script will stop all e-mail to sourceware/gcc lists.

I looked at the script and I can see why it does fail on two Cc: lines.
I don't see any obvious way to fix this.  Are two Cc: lines even legal in
a header?  Especially when the first line ends with a comma?

cgf

Re: [Fwd: failure notice]

[Chris Faylor]

On Wed, Aug 30, 2000 at 12:03:23PM -0700, Jason Molenda wrote:
>On Wed, Aug 30, 2000 at 11:30:53AM -0700, Jason Molenda wrote:
>
>> I think they converted all of the list-name blocking to use that script
>> I wrote for gcc earlier this year (infra/bin/check-for-listname.sh I think).
>> I bet it doesn't handle a double-Cc or double-To correctly 
>
>
>PS-  Jonathan, I bestow upon you the FREEDOM TO INNOVATE.  If you really
>     want this fixed, the shell script is in the /cvs/sourceware repository.
>     I don't imagine it'll be all that difficult to throw a loop around the
>     listname check, but you have to be careful that the script is correct -
>     a bug in this script will stop all e-mail to sourceware/gcc lists.

I looked at the script and I can see why it does fail on two Cc: lines.
I don't see any obvious way to fix this.  Are two Cc: lines even legal in
a header?  Especially when the first line ends with a comma?

cgf

Re: [Fwd: failure notice]

[Jason Molenda]

On Wed, Aug 30, 2000 at 03:36:22PM -0400, Chris Faylor wrote:

> I looked at the script and I can see why it does fail on two Cc: lines.
> I don't see any obvious way to fix this.  Are two Cc: lines even legal in
> a header?  Especially when the first line ends with a comma?

I don't know if it's legal, but it got delivered.  If it were me,
I'd probably say "Don't do that" - this is the first report I've
ever seen of someone sending out a msg like that.  But if Jonathan
thinks it's important enough, he can always dig in to it himself.

To fix it, I'd probably add some code to count the number of To: and Cc:
lines in the headers, and then loop over them somehow.

J

Re: [Fwd: failure notice]

[Jason Molenda]

On Wed, Aug 30, 2000 at 03:36:22PM -0400, Chris Faylor wrote:

> I looked at the script and I can see why it does fail on two Cc: lines.
> I don't see any obvious way to fix this.  Are two Cc: lines even legal in
> a header?  Especially when the first line ends with a comma?

I don't know if it's legal, but it got delivered.  If it were me,
I'd probably say "Don't do that" - this is the first report I've
ever seen of someone sending out a msg like that.  But if Jonathan
thinks it's important enough, he can always dig in to it himself.

To fix it, I'd probably add some code to count the number of To: and Cc:
lines in the headers, and then loop over them somehow.

J

Re: [Fwd: failure notice]

[Jonathan Larmour]

Jason Molenda wrote:
> 
> On Wed, Aug 30, 2000 at 03:36:22PM -0400, Chris Faylor wrote:
> 
> > I looked at the script and I can see why it does fail on two Cc: lines.
> > I don't see any obvious way to fix this.  Are two Cc: lines even legal in
> > a header? 

RFC822 sez about header fields:

    This specification permits multiple  occurrences  of  most
    fields.   Except  as  noted,  their  interpretation is not
    specified here, and their use is discouraged.

So it is frowned upon, but not illegal.

> Especially when the first line ends with a comma?

RFC822 #2.7 says that null elements are allowed, and therefore permits
trailing commas. But I've looked and this isn't the cause of the problem
anyway.
 
> I don't know if it's legal, but it got delivered.  If it were me,
> I'd probably say "Don't do that" - this is the first report I've
> ever seen of someone sending out a msg like that.  But if Jonathan
> thinks it's important enough, he can always dig in to it himself.
> 
> To fix it, I'd probably add some code to count the number of To: and Cc:
> lines in the headers, and then loop over them somehow.

Looking at check-for-listname.sh (thanks for the pointer Crash), the
relevant line is:
if cat $TMPFILE | sed -n '/^[Cc][Cc]: /,/^[a-zA-Z]/p' | sed '$d' |
   egrep -i "$VALID_LISTNAME" >/dev/null 2>&1                     

If the "sed '$d' |" is removed, it works correctly on this mail. I can't
see any reason for the "sed '$d'" to be there. Is there one? If not, I'll
just remove it.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

Re: [Fwd: failure notice]

[Jonathan Larmour]

Jason Molenda wrote:
> 
> On Wed, Aug 30, 2000 at 03:36:22PM -0400, Chris Faylor wrote:
> 
> > I looked at the script and I can see why it does fail on two Cc: lines.
> > I don't see any obvious way to fix this.  Are two Cc: lines even legal in
> > a header? 

RFC822 sez about header fields:

    This specification permits multiple  occurrences  of  most
    fields.   Except  as  noted,  their  interpretation is not
    specified here, and their use is discouraged.

So it is frowned upon, but not illegal.

> Especially when the first line ends with a comma?

RFC822 #2.7 says that null elements are allowed, and therefore permits
trailing commas. But I've looked and this isn't the cause of the problem
anyway.
 
> I don't know if it's legal, but it got delivered.  If it were me,
> I'd probably say "Don't do that" - this is the first report I've
> ever seen of someone sending out a msg like that.  But if Jonathan
> thinks it's important enough, he can always dig in to it himself.
> 
> To fix it, I'd probably add some code to count the number of To: and Cc:
> lines in the headers, and then loop over them somehow.

Looking at check-for-listname.sh (thanks for the pointer Crash), the
relevant line is:
if cat $TMPFILE | sed -n '/^[Cc][Cc]: /,/^[a-zA-Z]/p' | sed '$d' |
   egrep -i "$VALID_LISTNAME" >/dev/null 2>&1                     

If the "sed '$d' |" is removed, it works correctly on this mail. I can't
see any reason for the "sed '$d'" to be there. Is there one? If not, I'll
just remove it.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

Re: [Fwd: failure notice]

[Chris Faylor]

On Wed, Aug 30, 2000 at 09:51:50PM +0100, Jonathan Larmour wrote:
>Looking at check-for-listname.sh (thanks for the pointer Crash), the
>relevant line is:
>if cat $TMPFILE | sed -n '/^[Cc][Cc]: /,/^[a-zA-Z]/p' | sed '$d' |
>   egrep -i "$VALID_LISTNAME" >/dev/null 2>&1                     
>
>If the "sed '$d' |" is removed, it works correctly on this mail. I can't
>see any reason for the "sed '$d'" to be there. Is there one? If not, I'll
>just remove it.

I think that the $d guards against something like:

To: greatopportunities@foryou.com,
    dontmiss@this.com
Subject: ecos-discuss@sourceware.cygnus.com

Admittedly, it's not likely that something like this would happen, but this
should be moot anyway.  I've checked in a patch which should solve this problem.

I've checked it on the header in question and it seems to work fine.

Now, let's see if there are thousands of angry screams when we find that this
only works for ecos-discuss@sourceware.cygnus.com...

cgf

Re: [Fwd: failure notice]

[Chris Faylor]

On Wed, Aug 30, 2000 at 09:51:50PM +0100, Jonathan Larmour wrote:
>Looking at check-for-listname.sh (thanks for the pointer Crash), the
>relevant line is:
>if cat $TMPFILE | sed -n '/^[Cc][Cc]: /,/^[a-zA-Z]/p' | sed '$d' |
>   egrep -i "$VALID_LISTNAME" >/dev/null 2>&1                     
>
>If the "sed '$d' |" is removed, it works correctly on this mail. I can't
>see any reason for the "sed '$d'" to be there. Is there one? If not, I'll
>just remove it.

I think that the $d guards against something like:

To: greatopportunities@foryou.com,
    dontmiss@this.com
Subject: ecos-discuss@sourceware.cygnus.com

Admittedly, it's not likely that something like this would happen, but this
should be moot anyway.  I've checked in a patch which should solve this problem.

I've checked it on the header in question and it seems to work fine.

Now, let's see if there are thousands of angry screams when we find that this
only works for ecos-discuss@sourceware.cygnus.com...

cgf

Re: [Fwd: failure notice]

[Jonathan Larmour]

Chris Faylor wrote:
> 
> On Wed, Aug 30, 2000 at 09:51:50PM +0100, Jonathan Larmour wrote:
> >Looking at check-for-listname.sh (thanks for the pointer Crash), the
> >relevant line is:
> >if cat $TMPFILE | sed -n '/^[Cc][Cc]: /,/^[a-zA-Z]/p' | sed '$d' |
> >   egrep -i "$VALID_LISTNAME" >/dev/null 2>&1
> >
> >If the "sed '$d' |" is removed, it works correctly on this mail. I can't
> >see any reason for the "sed '$d'" to be there. Is there one? If not, I'll
> >just remove it.
> 
> I think that the $d guards against something like:
> 
> To: greatopportunities@foryou.com,
>     dontmiss@this.com
> Subject: ecos-discuss@sourceware.cygnus.com
> 
> Admittedly, it's not likely that something like this would happen, but this
> should be moot anyway. 

That's not what it's for either - sed only displays the line beginning with
the CC. I even just tried it to be sure.

Anyway, no matter - whatever works :-).

>  I've checked in a patch which should solve this problem. I've checked
> it on the header in question and it seems to work fine.

As long as formail isn't slow. Probably not.
 
> Now, let's see if there are thousands of angry screams when we find that this
> only works for ecos-discuss@sourceware.cygnus.com...

Heh.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

Re: [Fwd: failure notice]

[Jonathan Larmour]

Chris Faylor wrote:
> 
> On Wed, Aug 30, 2000 at 09:51:50PM +0100, Jonathan Larmour wrote:
> >Looking at check-for-listname.sh (thanks for the pointer Crash), the
> >relevant line is:
> >if cat $TMPFILE | sed -n '/^[Cc][Cc]: /,/^[a-zA-Z]/p' | sed '$d' |
> >   egrep -i "$VALID_LISTNAME" >/dev/null 2>&1
> >
> >If the "sed '$d' |" is removed, it works correctly on this mail. I can't
> >see any reason for the "sed '$d'" to be there. Is there one? If not, I'll
> >just remove it.
> 
> I think that the $d guards against something like:
> 
> To: greatopportunities@foryou.com,
>     dontmiss@this.com
> Subject: ecos-discuss@sourceware.cygnus.com
> 
> Admittedly, it's not likely that something like this would happen, but this
> should be moot anyway. 

That's not what it's for either - sed only displays the line beginning with
the CC. I even just tried it to be sure.

Anyway, no matter - whatever works :-).

>  I've checked in a patch which should solve this problem. I've checked
> it on the header in question and it seems to work fine.

As long as formail isn't slow. Probably not.
 
> Now, let's see if there are thousands of angry screams when we find that this
> only works for ecos-discuss@sourceware.cygnus.com...

Heh.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

Re: [Fwd: failure notice]

[Chris Faylor]

On Wed, Aug 30, 2000 at 01:14:25PM -0700, Jason Molenda wrote:
>On Wed, Aug 30, 2000 at 03:36:22PM -0400, Chris Faylor wrote:
>
>> I looked at the script and I can see why it does fail on two Cc: lines.
>> I don't see any obvious way to fix this.  Are two Cc: lines even legal in
>> a header?  Especially when the first line ends with a comma?
>
>I don't know if it's legal, but it got delivered.  If it were me,
>I'd probably say "Don't do that" - this is the first report I've
>ever seen of someone sending out a msg like that.  But if Jonathan
>thinks it's important enough, he can always dig in to it himself.
>
>To fix it, I'd probably add some code to count the number of To: and Cc:
>lines in the headers, and then loop over them somehow.

Ok.  I think I fixed it.  I just used 'formail' to parse the headers.  This
program was written to parse header info, so...

cgf

Re: [Fwd: failure notice]

[Chris Faylor]

On Wed, Aug 30, 2000 at 01:14:25PM -0700, Jason Molenda wrote:
>On Wed, Aug 30, 2000 at 03:36:22PM -0400, Chris Faylor wrote:
>
>> I looked at the script and I can see why it does fail on two Cc: lines.
>> I don't see any obvious way to fix this.  Are two Cc: lines even legal in
>> a header?  Especially when the first line ends with a comma?
>
>I don't know if it's legal, but it got delivered.  If it were me,
>I'd probably say "Don't do that" - this is the first report I've
>ever seen of someone sending out a msg like that.  But if Jonathan
>thinks it's important enough, he can always dig in to it himself.
>
>To fix it, I'd probably add some code to count the number of To: and Cc:
>lines in the headers, and then loop over them somehow.

Ok.  I think I fixed it.  I just used 'formail' to parse the headers.  This
program was written to parse header info, so...

cgf