Fwd: ezmlm warning

Fwd: ezmlm warning

[cyg Simple]

The below is a result of some attachment that was considered to be
vulnerable by my mail service.  Is there anything possible to do with
the filter sending these warnings?

> Remote host said: 552-5.7.0 This message was blocked because its
> content presents a potential security issue.

-------- Forwarded Message --------
Subject: ezmlm warning
Date: 30 May 2018 01:04:39 -0000
From: cygwin-help@cygwin.com
To: cygsimple@gmail.com

Hi! This is the ezmlm program. I'm managing the
cygwin@cygwin.com mailing list.


Messages to you from the cygwin 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 cygwin mailing list,
without further notice.


I've kept a list of which messages from the cygwin 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:
   <cygwin-get.123_145@cygwin.com>

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

Here are the message numbers:

   212575

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

Return-Path: <>
Received: (qmail 80790 invoked for bounce); 18 May 2018 09:25:34 -0000
Date: 18 May 2018 09:25:34 -0000
From: MAILER-DAEMON@sourceware.org
To: cygwin-return-212575-@cygwin.com
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.

<cygsimple@gmail.com>:
User and password not set, continuing without authentication.
<cygsimple@gmail.com> 173.194.202.26 failed after I sent the message.
Remote host said: 552-5.7.0 This message was blocked because its content
presents a potential
552-5.7.0 security issue. Please visit
552-5.7.0  https://support.google.com/mail/?p=BlockedMessage to review our
552 5.7.0 message content and attachment content guidelines.
f8-v6si3840726pgr.139 - gsmtp

Re: Fwd: ezmlm warning

[Christopher Faylor]

On Wed, May 30, 2018 at 11:43:27AM -0400, cyg Simple wrote:
>
>The below is a result of some attachment that was considered to be
>vulnerable by my mail service.  Is there anything possible to do with
>the filter sending these warnings?

Someone sent uncaught spam to the mailing list.  We can't block .gz
attachments for hopefully obvious reasons.

You just get those from time to time.

<losing-battle>Btw, email complaints don't go to overseers.  They go to
postmaster.</losing-battle>

Fwd: ezmlm warning

[Jan Beulich]

All,

for quite some time I've been getting one of these every once in a while.
Perhaps after some email system change over here, but see below.

>>> <binutils-help@sourceware.org> 05/21/18 10:40 AM >>>
>Hi! This is the ezmlm program. I'm managing the
>binutils@sourceware.org mailing list.
>
>
>Messages to you from the binutils 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 binutils mailing list,
>without further notice.
>
>
>I've kept a list of which messages from the binutils 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:
><binutils-get.123_145@sourceware.org>
>
>To receive a subject and author list for the last 100 or so messages,
>send an empty message to:
><binutils-index@sourceware.org>
>
>Here are the message numbers:
>
>101621
>101642
>101657
>101658
>101659
>101660
>101661
>101664
>101666
>101667
>101668
>101669
>101676
>101674
>101675
>101690
>101692
>101693
>101694
>101695
>101696
>101698
>101701
>101702
>101703
>101705
>101708
>101709
>101712
>101718
>101720
>101723
>101733

It would really be helpful if one could identify these messages in the list
archive. So far I've not been able to correlate the numbers to anything the
list archive web pages would show.

>--- Enclosed is a copy of the bounce message I received.
>
>Return-Path: <>
>Received: (qmail 108666 invoked for bounce); 9 May 2018 11:24:50 -0000
>Date: 9 May 2018 11:24:50 -0000
>From: MAILER-DAEMON@sourceware.org 
>To: binutils-return-101621-@sourceware.org 
>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.
>
><jbeulich@novell.com>:
>User and password not set, continuing without authentication.
><jbeulich@novell.com> 130.57.1.11 failed after I sent the message.
>Remote host said: 554 Line length exceeded per RFC2821 section 4.5.3.1

The question here is: Is the "Remote host" right? If yes, wouldn't it be better
to tell the sender of the original mail, so that they would (re)send well formed
mails? If not, once again it would be nice if identifying the messages in the
list archives was easily possible.

Jan

Re: Fwd: ezmlm warning

[Christopher Faylor]

On Fri, Jun 01, 2018 at 02:12:24AM -0600, Jan Beulich wrote:
>All,
>
>for quite some time I've been getting one of these every once in a while.
>Perhaps after some email system change over here, but see below.

Please send email problems to postmaster.

This is not a problem however.  sourceware is telling you tha your email
system bounced something back to us.  It might have been spam that wasn't
caught at sourceware but was caught on your end.

Everybody gets these.

>>>> <binutils-help@sourceware.org> 05/21/18 10:40 AM >>>
>>Hi! This is the ezmlm program. I'm managing the
>>binutils@sourceware.org mailing list.
>>
>>
>>Messages to you from the binutils 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 binutils mailing list,
>>without further notice.
>>
>>
>>I've kept a list of which messages from the binutils 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:
>><binutils-get.123_145@sourceware.org>
>>
>>To receive a subject and author list for the last 100 or so messages,
>>send an empty message to:
>><binutils-index@sourceware.org>
>>
>>Here are the message numbers:
>>
>>101621
>>101642
>>101657
>>101658
>>101659
>>101660
>>101661
>>101664
>>101666
>>101667
>>101668
>>101669
>>101676
>>101674
>>101675
>>101690
>>101692
>>101693
>>101694
>>101695
>>101696
>>101698
>>101701
>>101702
>>101703
>>101705
>>101708
>>101709
>>101712
>>101718
>>101720
>>101723
>>101733
>
>It would really be helpful if one could identify these messages in the list
>archive. So far I've not been able to correlate the numbers to anything the
>list archive web pages would show.
>
>>--- Enclosed is a copy of the bounce message I received.
>>
>>Return-Path: <>
>>Received: (qmail 108666 invoked for bounce); 9 May 2018 11:24:50 -0000
>>Date: 9 May 2018 11:24:50 -0000
>>From: MAILER-DAEMON@sourceware.org 
>>To: binutils-return-101621-@sourceware.org 
>>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.
>>
>><jbeulich@novell.com>:
>>User and password not set, continuing without authentication.
>><jbeulich@novell.com> 130.57.1.11 failed after I sent the message.
>>Remote host said: 554 Line length exceeded per RFC2821 section 4.5.3.1
>
>The question here is: Is the "Remote host" right? If yes, wouldn't it be better
>to tell the sender of the original mail, so that they would (re)send well formed
>mails? If not, once again it would be nice if identifying the messages in the
>list archives was easily possible.
>
>Jan
>
>
>

Fwd: ezmlm warning

[Toon Moene]

I got the following interesting failure message from ezmlm.
Apparently it was trying to send me an e-mail (via the gcc-patches 
mailing list) that contained more than 1,000 characters ...

Kind regards,
Toon Moene.


-------- Forwarded Message --------
Subject: ezmlm warning
Date: 19 Jun 2016 06:24:47 -0000
From: gcc-patches-help@gcc.gnu.org
To: toon@moene.org

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


Messages to you from the gcc-patches 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-patches mailing list,
without further notice.


I've kept a list of which messages from the gcc-patches 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-patches-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-patches-index@gcc.gnu.org>

Here are the message numbers:

    429184
    429199
    429200
    429276
    429286
    429287
    429288
    429283
    429284
    429285
    429356
    429501
    429518
    429532
    429641
    429654
    429659
    429661
    429744
    429747
    429748
    429745
    429749
    429704
    429768
    429766
    429782
    429844
    429933
    429983
    429996
    430045

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

Return-Path: <>
Received: (qmail 18240 invoked for bounce); 7 Jun 2016 09:28:49 -0000
Date: 7 Jun 2016 09:28:49 -0000
From: MAILER-DAEMON@sourceware.org
To: gcc-patches-return-429184-@gcc.gnu.org
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.

<toon@moene.org>:
User and password not set, continuing without authentication.
<toon@moene.org> 80.101.130.238 failed after I sent the message.
Remote host said: 550 maximum allowed line length is 998 octets, got 1525

Re: Fwd: ezmlm warning

[Frank Ch. Eigler]

Hi, Toon -

> I got the following interesting failure message from ezmlm.
> [...]
> <toon@moene.org>:
> User and password not set, continuing without authentication.
> <toon@moene.org> 80.101.130.238 failed after I sent the message.
> Remote host said: 550 maximum allowed line length is 998 octets, got 1525

This line length limit is being enforced by your own exim mail server.
Can you identify one of the messages on the archive perhaps, so we can
find out which line(s) were too long?  This may be an
overly-conservative exim configuration or some other problem.

- FChE

Re: Fwd: ezmlm warning

[Toon Moene]

On 06/21/2016 08:19 PM, Frank Ch. Eigler wrote:
> Hi, Toon -
>
>> I got the following interesting failure message from ezmlm.
>> [...]
>> <toon@moene.org>:
>> User and password not set, continuing without authentication.
>> <toon@moene.org> 80.101.130.238 failed after I sent the message.
>> Remote host said: 550 maximum allowed line length is 998 octets, got 1525
>
> This line length limit is being enforced by your own exim mail server.
> Can you identify one of the messages on the archive perhaps, so we can
> find out which line(s) were too long?  This may be an
> overly-conservative exim configuration or some other problem.

That's a bit hard to do, as ezmlm only gives me internal numbers (they 
are in my original message) and I see no way to correlate them with the 
archived messages ...

I thought the 550 message was related to a restriction imposed by an RFC 
newer than 822, but it could indeed be exim being too conservative.

If I am the only one with this complaint, just ignore it (although 
everyone running Debian testing would encounter this problem).

Kind regards,

-- 
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
At home: http://moene.org/~toon/; weather: http://moene.org/~hirlam/
Progress of GNU Fortran: http://gcc.gnu.org/wiki/GFortran#news

Fwd: ezmlm warning

[Rafael Espíndola]

This looks like the same issues we had some time ago in the LLVM lists:

http://lists.cs.uiuc.edu/pipermail/llvmdev/2014-May/072967.html

---------- Forwarded message ----------
From:  <gcc-help@gcc.gnu.org>
Date: 7 October 2014 17:09
Subject: ezmlm warning
To: rafael.espindola@gmail.com


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


Messages to you from the gcc 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 mailing list,
without further notice.


I've kept a list of which messages from the gcc 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-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-index@gcc.gnu.org>

Here are the message numbers:

   184984
   185030
   185061

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

Return-Path: <>
Received: (qmail 19475 invoked for bounce); 26 Sep 2014 01:36:24 -0000
Date: 26 Sep 2014 01:36:24 -0000
From: MAILER-DAEMON@sourceware.org
To: gcc-return-184984-@gcc.gnu.org
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.

<rafael.espindola@gmail.com>:
User and password not set, continuing without authentication.
<rafael.espindola@gmail.com> 173.194.79.26 failed after I sent the message.
Remote host said: 550-5.7.1 Unauthenticated email from yahoo.com is
not accepted due to domain's
550-5.7.1 DMARC policy. Please contact administrator of yahoo.com domain if
550-5.7.1 this was a legitimate mail. Please visit
550-5.7.1 http://support.google.com/mail/answer/2451690 to learn about DMARC
550 5.7.1 initiative. ew4si810254pdb.247 - gsmtp

Re: Fwd: ezmlm warning

[Ian Lance Taylor]

Rafael Espíndola <rafael.espindola@gmail.com> writes:

> This looks like the same issues we had some time ago in the LLVM lists:
>
> http://lists.cs.uiuc.edu/pipermail/llvmdev/2014-May/072967.html

There are no reasonable actions that we can take.  Yahoo! has chosen to
break mailing lists.

Perhaps we should simply ban @yahoo.com addresses.

Ian


> ---------- Forwarded message ----------
> From:  <gcc-help@gcc.gnu.org>
> Date: 7 October 2014 17:09
> Subject: ezmlm warning
> To: rafael.espindola@gmail.com
>
>
> Hi! This is the ezmlm program. I'm managing the
> gcc@gcc.gnu.org mailing list.
>
>
> Messages to you from the gcc 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 mailing list,
> without further notice.
>
>
> I've kept a list of which messages from the gcc 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-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-index@gcc.gnu.org>
>
> Here are the message numbers:
>
>    184984
>    185030
>    185061
>
> --- Enclosed is a copy of the bounce message I received.
>
> Return-Path: <>
> Received: (qmail 19475 invoked for bounce); 26 Sep 2014 01:36:24 -0000
> Date: 26 Sep 2014 01:36:24 -0000
> From: MAILER-DAEMON@sourceware.org
> To: gcc-return-184984-@gcc.gnu.org
> 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.
>
> <rafael.espindola@gmail.com>:
> User and password not set, continuing without authentication.
> <rafael.espindola@gmail.com> 173.194.79.26 failed after I sent the message.
> Remote host said: 550-5.7.1 Unauthenticated email from yahoo.com is
> not accepted due to domain's
> 550-5.7.1 DMARC policy. Please contact administrator of yahoo.com domain if
> 550-5.7.1 this was a legitimate mail. Please visit
> 550-5.7.1 http://support.google.com/mail/answer/2451690 to learn about DMARC
> 550 5.7.1 initiative. ew4si810254pdb.247 - gsmtp

Fwd: ezmlm warning

[Rafael Espíndola]

There was something similar going on the llvm and clang lists. The
explanation of what was going on in here

http://lists.cs.uiuc.edu/pipermail/cfe-dev/2014-May/037022.html

I am not sure if that is the same thing, but it sure looks similar.

---------- Forwarded message ----------
From:  <gcc-help@gcc.gnu.org>
Date: 29 May 2014 07:44
Subject: ezmlm warning
To: rafael.espindola@gmail.com


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


Messages to you from the gcc 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 mailing list,
without further notice.


I've kept a list of which messages from the gcc 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-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-index@gcc.gnu.org>

Here are the message numbers:

   183359
   183358
   183431
   183446

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

Return-Path: <>
Received: (qmail 1917 invoked for bounce); 17 May 2014 15:12:54 -0000
Date: 17 May 2014 15:12:54 -0000
From: MAILER-DAEMON@sourceware.org
To: gcc-return-183359-@gcc.gnu.org
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.

<rafael.espindola@gmail.com>:
User and password not set, continuing without authentication.
<rafael.espindola@gmail.com> 173.194.79.26 failed after I sent the message.
Remote host said: 550-5.7.1 [209.132.180.131       1] Our system has
detected an unusual rate of
550-5.7.1 unsolicited mail originating from your IP address. To protect our
550-5.7.1 users from spam, mail sent from your IP address has been blocked.
550-5.7.1 Please visit
550-5.7.1 http://www.google.com/mail/help/bulk_mail.html to review our Bulk
550 5.7.1 Email Senders Guidelines. wh4si4653110pbc.47 - gsmtp

Fwd: ezmlm warning

[Andrew Pinski]

This is the second email about the whole bulk email bounces.  Can
someone look into what it would take to make sure gmail does not
bounce the emails?

Thanks,
Andrew


---------- Forwarded message ----------
From:  <binutils-help@sourceware.org>
Date: Wed, May 21, 2014 at 1:42 PM
Subject: ezmlm warning
To: pinskia@gmail.com


Hi! This is the ezmlm program. I'm managing the
binutils@sourceware.org mailing list.


Messages to you from the binutils 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 binutils mailing list,
without further notice.


I've kept a list of which messages from the binutils 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:
   <binutils-get.123_145@sourceware.org>

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

Here are the message numbers:

   83669
   83671
   83672
   83674

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

Return-Path: <>
Received: (qmail 10946 invoked for bounce); 9 May 2014 19:38:30 -0000
Date: 9 May 2014 19:38:30 -0000
From: MAILER-DAEMON@sourceware.org
To: binutils-return-83669-@sourceware.org
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.

<pinskia@gmail.com>:
User and password not set, continuing without authentication.
<pinskia@gmail.com> 74.125.129.27 failed after I sent the message.
Remote host said: 550-5.7.1 [209.132.180.131       1] Our system has
detected an unusual rate of
550-5.7.1 unsolicited mail originating from your IP address. To protect our
550-5.7.1 users from spam, mail sent from your IP address has been blocked.
550-5.7.1 Please visit
550-5.7.1 http://www.google.com/mail/help/bulk_mail.html to review our Bulk
550 5.7.1 Email Senders Guidelines. ko6si968474pbc.313 - gsmtp

Re: Fwd: ezmlm warning

[Ian Lance Taylor]

Andrew Pinski <pinskia@gmail.com> writes:

> This is the second email about the whole bulk email bounces.  Can
> someone look into what it would take to make sure gmail does not
> bounce the emails?

I've asked Google internally what is going on.  No answer as yet.

I think the most likely cause of this would be people marking e-mail
sent from gcc.gnu.org/sourceware.org as spam, but I don't know why they
would be doing that.

Ian



> ---------- Forwarded message ----------
> From:  <binutils-help@sourceware.org>
> Date: Wed, May 21, 2014 at 1:42 PM
> Subject: ezmlm warning
> To: pinskia@gmail.com
>
>
> Hi! This is the ezmlm program. I'm managing the
> binutils@sourceware.org mailing list.
>
>
> Messages to you from the binutils 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 binutils mailing list,
> without further notice.
>
>
> I've kept a list of which messages from the binutils 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:
>    <binutils-get.123_145@sourceware.org>
>
> To receive a subject and author list for the last 100 or so messages,
> send an empty message to:
>    <binutils-index@sourceware.org>
>
> Here are the message numbers:
>
>    83669
>    83671
>    83672
>    83674
>
> --- Enclosed is a copy of the bounce message I received.
>
> Return-Path: <>
> Received: (qmail 10946 invoked for bounce); 9 May 2014 19:38:30 -0000
> Date: 9 May 2014 19:38:30 -0000
> From: MAILER-DAEMON@sourceware.org
> To: binutils-return-83669-@sourceware.org
> 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.
>
> <pinskia@gmail.com>:
> User and password not set, continuing without authentication.
> <pinskia@gmail.com> 74.125.129.27 failed after I sent the message.
> Remote host said: 550-5.7.1 [209.132.180.131       1] Our system has
> detected an unusual rate of
> 550-5.7.1 unsolicited mail originating from your IP address. To protect our
> 550-5.7.1 users from spam, mail sent from your IP address has been blocked.
> 550-5.7.1 Please visit
> 550-5.7.1 http://www.google.com/mail/help/bulk_mail.html to review our Bulk
> 550 5.7.1 Email Senders Guidelines. ko6si968474pbc.313 - gsmtp

Re: Fwd: ezmlm warning

[Andrew Pinski]

On Wed, May 21, 2014 at 9:22 PM, Ian Lance Taylor <ian@airs.com> wrote:
> Andrew Pinski <pinskia@gmail.com> writes:
>
>> This is the second email about the whole bulk email bounces.  Can
>> someone look into what it would take to make sure gmail does not
>> bounce the emails?
>
> I've asked Google internally what is going on.  No answer as yet.
>
> I think the most likely cause of this would be people marking e-mail
> sent from gcc.gnu.org/sourceware.org as spam, but I don't know why they
> would be doing that.

Could it also be there was some spam that went through but then some
folks decided to mark that one piece as spam?

Thanks,
Andrew


>
> Ian
>
>
>
>> ---------- Forwarded message ----------
>> From:  <binutils-help@sourceware.org>
>> Date: Wed, May 21, 2014 at 1:42 PM
>> Subject: ezmlm warning
>> To: pinskia@gmail.com
>>
>>
>> Hi! This is the ezmlm program. I'm managing the
>> binutils@sourceware.org mailing list.
>>
>>
>> Messages to you from the binutils 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 binutils mailing list,
>> without further notice.
>>
>>
>> I've kept a list of which messages from the binutils 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:
>>    <binutils-get.123_145@sourceware.org>
>>
>> To receive a subject and author list for the last 100 or so messages,
>> send an empty message to:
>>    <binutils-index@sourceware.org>
>>
>> Here are the message numbers:
>>
>>    83669
>>    83671
>>    83672
>>    83674
>>
>> --- Enclosed is a copy of the bounce message I received.
>>
>> Return-Path: <>
>> Received: (qmail 10946 invoked for bounce); 9 May 2014 19:38:30 -0000
>> Date: 9 May 2014 19:38:30 -0000
>> From: MAILER-DAEMON@sourceware.org
>> To: binutils-return-83669-@sourceware.org
>> 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.
>>
>> <pinskia@gmail.com>:
>> User and password not set, continuing without authentication.
>> <pinskia@gmail.com> 74.125.129.27 failed after I sent the message.
>> Remote host said: 550-5.7.1 [209.132.180.131       1] Our system has
>> detected an unusual rate of
>> 550-5.7.1 unsolicited mail originating from your IP address. To protect our
>> 550-5.7.1 users from spam, mail sent from your IP address has been blocked.
>> 550-5.7.1 Please visit
>> 550-5.7.1 http://www.google.com/mail/help/bulk_mail.html to review our Bulk
>> 550 5.7.1 Email Senders Guidelines. ko6si968474pbc.313 - gsmtp

Re: Fwd: ezmlm warning

[Ian Lance Taylor]

Andrew Pinski <pinskia@gmail.com> writes:

> On Wed, May 21, 2014 at 9:22 PM, Ian Lance Taylor <ian@airs.com> wrote:
>> Andrew Pinski <pinskia@gmail.com> writes:
>>
>>> This is the second email about the whole bulk email bounces.  Can
>>> someone look into what it would take to make sure gmail does not
>>> bounce the emails?
>>
>> I've asked Google internally what is going on.  No answer as yet.
>>
>> I think the most likely cause of this would be people marking e-mail
>> sent from gcc.gnu.org/sourceware.org as spam, but I don't know why they
>> would be doing that.
>
> Could it also be there was some spam that went through but then some
> folks decided to mark that one piece as spam?

My understanding is that it would take more than one piece of spam to
change the reputation of the machine.  Lots more.

Ian

Fwd: ezmlm warning

[Mike Stump]

So, likely you guys already know about dmarc and some folks are turning it on…  So, it looks like comcast thought you guys turned it on, and enabled rejects.

So, out of curiosity, did you?  I looked now, and I see it isn’t on.

I’ve checked lots of my old email for dkim=fail, and I see all bugzilla email fails dkim.  The latest failure was on March 31, 2014.

Begin forwarded message:
> From: gcc-patches-help@gcc.gnu.org
> Subject: ezmlm warning
> Date: April 20, 2014 at 9:41:41 PM PDT
> To: mikestump@comcast.net
> 
> Hi! This is the ezmlm program. I'm managing the
> gcc-patches@gcc.gnu.org mailing list.
> 
> 
> Messages to you from the gcc-patches 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-patches mailing list,
> without further notice.
> 
> 
> I've kept a list of which messages from the gcc-patches 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-patches-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-patches-index@gcc.gnu.org>
> 
> Here are the message numbers:
> 
>   364702
>   364826
>   364914
>   364933
>   365121
>   365339
>   365404
> 
> --- Enclosed is a copy of the bounce message I received.
> 
> Return-Path: <>
> Received: (qmail 9386 invoked for bounce); 9 Apr 2014 07:16:37 -0000
> Date: 9 Apr 2014 07:16:37 -0000
> From: MAILER-DAEMON@sourceware.org
> To: gcc-patches-return-364702-@gcc.gnu.org
> 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.
> 
> <mikestump@comcast.net>:
> User and password not set, continuing without authentication.
> <mikestump@comcast.net> 68.87.26.147 failed after I sent the message.
> Remote host said: 550 5.2.0 nhW41n0182qVqVd0DhW4cN Message rejected due to DMARC. Please see http://postmaster.comcast.net/smtp-error-codes.php#DM000001

Re: Fwd: ezmlm warning

[Frank Ch. Eigler]

Hi, Mike -

> So, likely you guys already know about dmarc [...]
> So, out of curiosity, did you?  I looked now, and I see it isn’t on.

Nope, but we do have an SPF & DKIM record in DNS and sign outgoing
mail with DKIM.

> I’ve checked lots of my old email for dkim=fail, and I see all
> bugzilla email fails dkim.  The latest failure was on March 31,
> 2014.

It'd be handy if you could find a couple of raw message URLs in the
archives for analysis.

> > Remote host said: 550 5.2.0 nhW41n0182qVqVd0DhW4cN Message rejected due to DMARC. Please see http://postmaster.comcast.net/smtp-error-codes.php#DM000001

Yeah, not enough information there.

- FChE

Fwd: ezmlm warning

[Carlos O'Donell]

Overseers,

I've been getting a lot of these transient failures lately.

I consider it pretty odd that my provider (Dotster.com) would not have
a mail exchanger or IP address in place for the MX for
@systemhalted.org.

Has anything been going on with sourceware.org that might cause this problem?

Is there any way I can track down the root cause?

Cheers,
Carlos.

---------- Forwarded message ----------
From:  <libc-ports-help@sourceware.org>
Date: Wed, Jun 6, 2012 at 5:52 PM
Subject: ezmlm warning
To: carlos@systemhalted.org


Hi! This is the ezmlm program. I'm managing the
libc-ports@sourceware.org mailing list.


Messages to you from the libc-ports 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 libc-ports mailing list,
without further notice.


I've kept a list of which messages from the libc-ports 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:
  <libc-ports-get.123_145@sourceware.org>

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

Here are the message numbers:

  2725
  2789

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

Return-Path: <>
Received: (qmail 4086 invoked for bounce); 25 May 2012 22:42:21 -0000
Date: 25 May 2012 22:42:21 -0000
From: MAILER-DAEMON@sourceware.org
To: libc-ports-return-2725-@sourceware.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="1337985273sourceware.org22923270"
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.

<carlos@systemhalted.org>:
Sorry, I couldn't find a mail exchanger or IP address. (#5.4.4)

Re: Fwd: ezmlm warning

[Ian Lance Taylor]

"Carlos O'Donell" <carlos@systemhalted.org> writes:

> I've been getting a lot of these transient failures lately.
>
> I consider it pretty odd that my provider (Dotster.com) would not have
> a mail exchanger or IP address in place for the MX for
> @systemhalted.org.
>
> Has anything been going on with sourceware.org that might cause this problem?

No.

> Is there any way I can track down the root cause?

I don't know.  This error means that some DNS server in the chain
responded to the request but failed to supply any information.  This
could be the nameservers for systemhalted.org (at dotster.com), or the
ones for your MX record, mx.mailix.net (at idirections.com).
Unfortunately our DNS logs cover less than 24 hours these days, and you
aren't going to get the failure notice in time for us to see anything.

Ian

> ---------- Forwarded message ----------
> From:  <libc-ports-help@sourceware.org>
> Date: Wed, Jun 6, 2012 at 5:52 PM
> Subject: ezmlm warning
> To: carlos@systemhalted.org
>
>
> Hi! This is the ezmlm program. I'm managing the
> libc-ports@sourceware.org mailing list.
>
>
> Messages to you from the libc-ports 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 libc-ports mailing list,
> without further notice.
>
>
> I've kept a list of which messages from the libc-ports 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:
>   <libc-ports-get.123_145@sourceware.org>
>
> To receive a subject and author list for the last 100 or so messages,
> send an empty message to:
>   <libc-ports-index@sourceware.org>
>
> Here are the message numbers:
>
>   2725
>   2789
>
> --- Enclosed is a copy of the bounce message I received.
>
> Return-Path: <>
> Received: (qmail 4086 invoked for bounce); 25 May 2012 22:42:21 -0000
> Date: 25 May 2012 22:42:21 -0000
> From: MAILER-DAEMON@sourceware.org
> To: libc-ports-return-2725-@sourceware.org
> MIME-Version: 1.0
> Content-Type: multipart/mixed; boundary="1337985273sourceware.org22923270"
> 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.
>
> <carlos@systemhalted.org>:
> Sorry, I couldn't find a mail exchanger or IP address. (#5.4.4)

Re: Fwd: ezmlm warning

[Carlos O'Donell]

On Thu, Jun 7, 2012 at 1:24 PM, Ian Lance Taylor <ian@airs.com> wrote:
>> Is there any way I can track down the root cause?
>
> I don't know.  This error means that some DNS server in the chain
> responded to the request but failed to supply any information.  This
> could be the nameservers for systemhalted.org (at dotster.com), or the
> ones for your MX record, mx.mailix.net (at idirections.com).
> Unfortunately our DNS logs cover less than 24 hours these days, and you
> aren't going to get the failure notice in time for us to see anything.

Thanks Ian.

I'd been putting off switching to a more reputable service provide and
I guess now's the time.

Cheers,
Carlos.

Fwd: ezmlm warning

[Mike Stump]

I'm sure you've seen these before, it's baack...

Begin forwarded message:

> From: gcc-patches-help@gcc.gnu.org
> Date: December 22, 2005 3:58:33 PM PST
> To: mrs@apple.com
> Subject: ezmlm warning
>
> Hi! This is the ezmlm program. I'm managing the
> gcc-patches@gcc.gnu.org mailing list.

> <mrs@apple.com>:
> SMTP cannot transfer messages with partial final lines. (#5.6.2)

Fwd: ezmlm warning

[Mike Stump]

It appears that sourceware uses qmail to forward on email and that  
something before qmail on sourceware stripped out the ending newline  
on the email before having fed it to qmail.  This appears to be an  
internal to sourceware problem.

Unfortunately there aren't enough details in the below to be sure.

Do this look familiar to anyone?  Do others agree?  I'm I wrong, is  
it post sourceware?

?

Begin forwarded message:

> From: gcc-help@gcc.gnu.org
> Date: December 11, 2005 8:49:52 PM PST
> To: mrs@apple.com
> Subject: ezmlm warning
>
>
> Hi! This is the ezmlm program. I'm managing the
> gcc@gcc.gnu.org mailing list.
>
>
> Messages to you from the gcc 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 mailing list,
> without further notice.
>
>
> I've kept a list of which messages from the gcc 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-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-index@gcc.gnu.org>
>
> Here are the message numbers:
>
>    122444
>    122403
>
> --- Enclosed is a copy of the bounce message I received.
>
> Return-Path: <>
> Received: (qmail 15378 invoked for bounce); 30 Nov 2005 14:13:10 -0000
> Date: 30 Nov 2005 14:13:10 -0000
> From: MAILER-DAEMON@sourceware.org
> To: gcc-return-122444-@gcc.gnu.org
> MIME-Version: 1.0
> Content-Type: multipart/mixed;  
> boundary="1133301907sourceware.org24884169"
> 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.
>
> <mrs@apple.com>:
> SMTP cannot transfer messages with partial final lines. (#5.6.2)
>
>

Re: Fwd: ezmlm warning

[Ian Lance Taylor]

Mike Stump <mrs@apple.com> writes:

> It appears that sourceware uses qmail to forward on email and that
> something before qmail on sourceware stripped out the ending newline
> on the email before having fed it to qmail.  This appears to be an
> internal to sourceware problem.
> 
> Unfortunately there aren't enough details in the below to be sure.
> 
> Do this look familiar to anyone?  Do others agree?  I'm I wrong, is
> it post sourceware?

You are correct that the problem must be internal to sourceware.  We
suspect that it has been fixed, but we are keeping an eye on it.

Thanks for reporting it.

Ian

Fwd: ezmlm warning

[Aaron W. LaFramboise]

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

Hello.  I got this weird message from gcc-help ezmlm today.  Does this 
indicate a problem with my mail, or can I ignore it?

[-- Attachment #2: ezmlm warning --]
[-- Type: message/rfc822, Size: 2254 bytes --]

From: gcc-help@gcc.gnu.org
To: aaronavay62@aaronwl.com
Subject: ezmlm warning
Date: 12 Dec 2005 04:50:04 -0000
Message-ID: <1134363004.10249.ezmlm-warn@gcc.gnu.org>

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


Messages to you from the gcc 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 mailing list,
without further notice.


I've kept a list of which messages from the gcc 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-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-index@gcc.gnu.org>

Here are the message numbers:

   122444
   122403

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

Return-Path: <>
Received: (qmail 15378 invoked for bounce); 30 Nov 2005 14:13:10 -0000
Date: 30 Nov 2005 14:13:10 -0000
From: MAILER-DAEMON@sourceware.org
To: gcc-return-122444-@gcc.gnu.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="1133301907sourceware.org24884169"
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.

<aaronavay62@aaronwl.com>:
SMTP cannot transfer messages with partial final lines. (#5.6.2)

Re: Fwd: ezmlm warning

[Ian Lance Taylor]

"Aaron W. LaFramboise" <aaronavay62@aaronwl.com> writes:

> Hello.  I got this weird message from gcc-help ezmlm today.  Does this
> indicate a problem with my mail, or can I ignore it?

You can ignore it.

Ian