[ams@gnu.org: [sysadmin@gnu.org: [gnu.org #572859] [gcc-bugs-help@gcc.gnu.org: ezmlm warning]]]

[ams@gnu.org: [sysadmin@gnu.org: [gnu.org #572859] [gcc-bugs-help@gcc.gnu.org: ezmlm warning]]]

[Alfred M. Szmidt]

Could someone please look into this? These warnings tend to pop up
once in a while.

------- Start of forwarded message -------
From: "Alfred M. Szmidt" <ams@gnu.org>
To: gcc@gcc.gnu.org
Subject: [sysadmin@gnu.org: [gnu.org #572859] [gcc-bugs-help@gcc.gnu.org: ezmlm warning]]
Date: Tue, 11 May 2010 16:12:45 -0400

Not sure where to send this, who is responsible for the mail server
for gcc.gnu.org?

- ------- Start of forwarded message -------
Subject: [gnu.org #572859] [gcc-bugs-help@gcc.gnu.org: ezmlm warning] 
From: "Ward Vandewege via RT" <sysadmin@gnu.org>
To: ams@gnu.org
Date: Mon, 10 May 2010 10:28:41 -0400

> [ams@gnu.org - Sun May 09 07:42:17 2010]:
> 
> Not sure if it is useful to report these warnings from gcc.gnu.org,
> but here is another warning I got.
> 
> Hi. This is the qmail-send program at sourceware.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.
> 
> <ams@gnu.org>:
> 140.186.70.92 failed after I sent the message.
> Remote host said: 550-8-bit characters not allowed in subject
> 550 (see RFC 2822, sections 3.6.5, 2.2.1)
> ------- End of forwarded message -------

This was a message with illegal encoding. This is our rule:

  deny    senders       = \N[\x80-\xFF]\N
          message       = 8-bit characters not allowed in envelope sender\n\
                          (see RFC 2821, section 4.1.2)


The gcc.gnu.org mailserver should really not be accepting that mail either.

Thanks,
Ward.

- - -- 
Ward Vandewege <ward@fsf.org>
Free Software Foundation - Senior System Administrator
- ------- End of forwarded message -------
------- End of forwarded message -------

Re: [ams@gnu.org: [sysadmin@gnu.org: [gnu.org #572859] [gcc-bugs-help@gcc.gnu.org: ezmlm warning]]]

[Ian Lance Taylor]

"Alfred M. Szmidt" <ams@gnu.org> writes:

> Could someone please look into this? These warnings tend to pop up
> once in a while.

I can't tell where the original e-mail message came from.  If it came
from someone on the net, then I would recommend just ignoring these
warnings.  If some program on gcc.gnu.org is generating e-mail with
8-bit characters in the subject line, which program is it?

Ian

> From: "Alfred M. Szmidt" <ams@gnu.org>
> Subject: [sysadmin@gnu.org: [gnu.org #572859] [gcc-bugs-help@gcc.gnu.org: ezmlm warning]]
> To: gcc@gcc.gnu.org
> Date: Tue, 11 May 2010 16:12:45 -0400
>
> Not sure where to send this, who is responsible for the mail server
> for gcc.gnu.org?
>
> - ------- Start of forwarded message -------
> Subject: [gnu.org #572859] [gcc-bugs-help@gcc.gnu.org: ezmlm warning] 
> From: "Ward Vandewege via RT" <sysadmin@gnu.org>
> To: ams@gnu.org
> Date: Mon, 10 May 2010 10:28:41 -0400
>
>> [ams@gnu.org - Sun May 09 07:42:17 2010]:
>> 
>> Not sure if it is useful to report these warnings from gcc.gnu.org,
>> but here is another warning I got.
>> 
>> Hi. This is the qmail-send program at sourceware.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.
>> 
>> <ams@gnu.org>:
>> 140.186.70.92 failed after I sent the message.
>> Remote host said: 550-8-bit characters not allowed in subject
>> 550 (see RFC 2822, sections 3.6.5, 2.2.1)
>> ------- End of forwarded message -------
>
> This was a message with illegal encoding. This is our rule:
>
>   deny    senders       = \N[\x80-\xFF]\N
>           message       = 8-bit characters not allowed in envelope sender\n\
>                           (see RFC 2821, section 4.1.2)
>
>
> The gcc.gnu.org mailserver should really not be accepting that mail either.
>
> Thanks,
> Ward.
>
> - - -- 
> Ward Vandewege <ward@fsf.org>
> Free Software Foundation - Senior System Administrator
> - ------- End of forwarded message -------
> ----------

Re: [ams@gnu.org: [sysadmin@gnu.org: [gnu.org #572859] [gcc-bugs-help@gcc.gnu.org: ezmlm warning]]]

[Alfred M. Szmidt]

   > Could someone please look into this? These warnings tend to pop
   > up once in a while.

   I can't tell where the original e-mail message came from.  If it
   came from someone on the net, then I would recommend just ignoring
   these warnings.  If some program on gcc.gnu.org is generating
   e-mail with 8-bit characters in the subject line, which program is
   it?

Here is the original, with full headers.  What happens from what I can
guess is that gcc.gnu.org acepts messages that contain 8-bit
characters.  The mail server on gnu.org bounces all those messages,
and and thus the recipient (in this case, me) gets a warning from the
MTA about it.  

From gcc-bugs-return-warn-1273401010.modciloldjmepfeljbcj-ams_gnu.org@gcc.gnu.org Sun May  9 11:24:19 2010
Received: from fencepost.gnu.org (fencepost.gnu.org [140.186.70.10])
	by localhost (mpop-1.0.20) with POP3
	for <ams>; Sun, 09 May 2010 13:24:19 +0200
Return-path: <gcc-bugs-return-warn-1273401010.modciloldjmepfeljbcj-ams=gnu.org@gcc.gnu.org>
Envelope-to: ams@gnu.org
Delivery-date: Sun, 09 May 2010 06:30:27 -0400
Received: from mx10.gnu.org ([199.232.76.166]:56576)
	by fencepost.gnu.org with esmtp (Exim 4.69)
	(envelope-from <gcc-bugs-return-warn-1273401010.modciloldjmepfeljbcj-ams=gnu.org@gcc.gnu.org>)
	id 1OB3mF-0000Xu-57
	for ams@gnu.org; Sun, 09 May 2010 06:30:27 -0400
Received: from eggs.gnu.org ([140.186.70.92]:38600)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60)
	(envelope-from <gcc-bugs-return-warn-1273401010.modciloldjmepfeljbcj-ams=gnu.org@gcc.gnu.org>)
	id 1OB3mE-0002Wn-RP
	for ams@gnu.org; Sun, 09 May 2010 06:30:26 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <gcc-bugs-return-warn-1273401010.modciloldjmepfeljbcj-ams=gnu.org@gcc.gnu.org>)
	id 1OB3m3-0000ao-Kd
	for ams@gnu.org; Sun, 09 May 2010 06:30:17 -0400
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on eggs.gnu.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED
	autolearn=ham version=3.3.1
Received: from server1.sourceware.org ([209.132.180.131]:36035 helo=sourceware.org)
	by eggs.gnu.org with smtp (Exim 4.69)
	(envelope-from <gcc-bugs-return-warn-1273401010.modciloldjmepfeljbcj-ams=gnu.org@gcc.gnu.org>)
	id 1OB3m3-0000aD-DE
	for ams@gnu.org; Sun, 09 May 2010 06:30:15 -0400
Received: (qmail 14482 invoked by alias); 9 May 2010 10:30:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Date: 9 May 2010 10:30:10 -0000
Message-ID: <1273401010.14466.ezmlm-warn@gcc.gnu.org>
From: gcc-bugs-help@gcc.gnu.org
To: ams@gnu.org
Content-type: text/plain; charset=us-ascii
Subject: ezmlm warning
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized.
X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3)
X-UIDL: 5aD!!&-_!!Q3d"!o:n!!
X-RMAIL-ATTRIBUTES: -D-F----

Hi! This is the ezmlm program. I'm managing the
gcc-bugs@gcc.gnu.org mailing list.


Messages to you from the gcc-bugs mailing list seem to
have been bouncing. I've attached a copy of the first bounce
message I received.

If this message bounces too, I will send you a probe. If the probe bounces,
I will remove your address from the gcc-bugs mailing list,
without further notice.


I've kept a list of which messages from the gcc-bugs mailing list have 
bounced from your address.

Copies of these messages may be in the archive.
To retrieve a set of messages 123-145 (a maximum of 100 per request),
send an empty message to:
   <gcc-bugs-get.123_145@gcc.gnu.org>

To receive a subject and author list for the last 100 or so messages,
send an empty message to:
   <gcc-bugs-index@gcc.gnu.org>

Here are the message numbers:

   315945
   315947
   315948
   315949
   315950
   315961
   315963

--- Enclosed is a copy of the bounce message I received.

Return-Path: <>
Received: (qmail 8730 invoked for bounce); 27 Apr 2010 20:03:50 -0000
Date: 27 Apr 2010 20:03:50 -0000
From: MAILER-DAEMON@sourceware.org
To: gcc-bugs-return-315945-@gcc.gnu.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="1272128228sourceware.org22922222"
Subject: failure notice

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

<ams@gnu.org>:
140.186.70.92 failed after I sent the message.
Remote host said: 550-8-bit characters not allowed in subject
550 (see RFC 2822, sections 3.6.5, 2.2.1)

Re: [ams@gnu.org: [sysadmin@gnu.org: [gnu.org #572859] [gcc-bugs-help@gcc.gnu.org: ezmlm warning]]]

[Ian Lance Taylor]

"Alfred M. Szmidt" <ams@gnu.org> writes:

>    > Could someone please look into this? These warnings tend to pop
>    > up once in a while.
>
>    I can't tell where the original e-mail message came from.  If it
>    came from someone on the net, then I would recommend just ignoring
>    these warnings.  If some program on gcc.gnu.org is generating
>    e-mail with 8-bit characters in the subject line, which program is
>    it?
>
> Here is the original, with full headers.  What happens from what I can
> guess is that gcc.gnu.org acepts messages that contain 8-bit
> characters.  The mail server on gnu.org bounces all those messages,
> and and thus the recipient (in this case, me) gets a warning from the
> MTA about it.  

>    315945

This is a message to gcc-bugs.  I took at look at this one.  The Subject
line is:

Subject: [Bug fortran/43793] [4.5/4.6 Regression] tree check: expected tree that
 contains �decl minimal� structure, have �indirect_ref� in gfc_trans_array_bound
_check

which does indeed contain 8-bit characters.  The message is generated
from a bugzilla comment; the bug can be seen on the web at
http://gcc/PR43793.  It strikes me as a bad idea to have the gcc.gnu.org
mail server reject a message from Bugzilla running on the same machine
because a few mail servers are strict.  Therefore, we would need to
patch Bugzilla to avoid sending messages with these Subject lines.  We
are looking into upgrading our rather old copy of Bugzilla; perhaps that
will avoid or fix this problem.  If not, then I think the right approach
here is going to be for you to talk to the Bugzilla maintainers.

Ian