From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Victor Rodriguez <vm.rod25@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: ezmlm warning
Date: Tue, 25 Aug 2015 18:15:00 -0000 [thread overview]
Message-ID: <CAH6eHdTRCx=xg_Zx+EYYw6PtE_=fySxTErMtj9wxLuFea8QQtw@mail.gmail.com> (raw)
In-Reply-To: <CAK5mtewKM5aK_Rgug2NqsrOPnq-uduYYyy=-YGL-OX8WXgX7kQ@mail.gmail.com>
You can add or remove yourself using the form at https://gcc.gnu.org/lists.html
(It's unfortunate that the ezmlm software sends email from the
gcc-help@gcc.gnu.org address which also happens to be a valid list)
On 25 August 2015 at 19:03, Victor Rodriguez <vm.rod25@gmail.com> wrote:
> Hi
>
> I am developing things for gcc autofdo feature . Can you please add
> the to the gcc mailing list
>
> Please do not remove me from the mailing list :)
>
> Best regards
>
> Victor Rodriguez
>
>
> On Tue, Aug 25, 2015 at 12:02 PM, <gcc-help@gcc.gnu.org> wrote:
>> 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:
>>
>> 188139
>> 188169
>> 188185
>>
>> --- Enclosed is a copy of the bounce message I received.
>>
>> Return-Path: <>
>> Received: (qmail 129988 invoked for bounce); 14 Aug 2015 02:32:21 -0000
>> Date: 14 Aug 2015 02:32:21 -0000
>> From: MAILER-DAEMON@sourceware.org
>> To: gcc-return-188139-@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.
>>
>> <vm.rod25@gmail.com>:
>> User and password not set, continuing without authentication.
>> <vm.rod25@gmail.com> 173.194.203.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 https://support.google.com/mail/answer/2451690 to learn about DMARC
>> 550 5.7.1 initiative. gh3si945255pbd.129 - gsmtp
>>
next prev parent reply other threads:[~2015-08-25 18:15 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1440522165.122030.ezmlm-warn@gcc.gnu.org>
2015-08-25 18:03 ` Victor Rodriguez
2015-08-25 18:15 ` Jonathan Wakely [this message]
[not found] <1573542876.107262.ezmlm-warn@gcc.gnu.org>
2019-11-12 9:33 ` xaris.papadopoulos
2019-11-12 15:05 ` Jonathan Wakely
[not found] <1553292518.33035.ezmlm-warn@gcc.gnu.org>
2019-03-22 23:58 ` Fwd: " Perry Wagle
2019-03-23 0:25 ` Jonathan Wakely
2019-03-23 0:34 ` Perry Wagle
2019-03-23 0:35 ` Jonathan Wakely
2019-03-23 2:51 ` Jonathan Wakely
[not found] <1542666098.95636.ezmlm-warn@gcc.gnu.org>
2018-11-26 0:28 ` Fwd: " Timur Tabi
2018-11-26 10:40 ` Jonathan Wakely
2018-10-17 8:37 jfb
[not found] <1533450048.58449.ezmlm-warn@gcc.gnu.org>
2018-08-05 17:17 ` Caroline Willis
2018-08-05 17:52 ` Toby Douglass
2018-08-05 21:47 ` Segher Boessenkool
2018-08-05 22:58 ` arrl via gcc-help
2018-08-06 14:27 ` Jonathan Wakely
2018-08-06 14:38 ` Jonathan Wakely
2018-08-08 1:31 ` Yubin Ruan
2018-08-08 10:31 ` Jonathan Wakely
-- strict thread matches above, loose matches on Subject: below --
2018-08-05 6:19 jfb
[not found] <1525977321.30450.ezmlm-warn@gcc.gnu.org>
2018-05-10 18:52 ` Eric S. Raymond
2016-09-11 21:39 jfb
2013-08-30 6:38 gcc-help-help
[not found] <1138836346.15795.ezmlm-warn@gcc.gnu.org>
2006-02-01 23:58 ` Dave Murphy
2006-02-02 18:34 ` Ian Lance Taylor
[not found] <1089282316.20156.ezmlm-warn@gcc.gnu.org>
2004-07-09 23:08 ` Alan Matsuoka
[not found] <1040832276.14084.ezmlm-warn@gcc.gnu.org>
2003-01-02 17:35 ` Kevin Cheek
2002-07-12 21:40 Robert Dewar
[not found] <983221643.2421.ezmlm-warn@gcc.gnu.org>
2001-02-26 23:47 ` Bo Thorsen
2001-02-27 0:22 ` Andrei A. Dergatchev
[not found] <974442017.7990.ezmlm-warn@gcc.gnu.org>
2000-11-17 9:11 ` David O'Brien
[not found] <970221716.23478.ezmlm-warn@gcc.gnu.org>
2000-09-29 8:23 ` Bruce Korb
2000-04-19 4:26 fvd
[not found] <944155534.23083.ezmlm-warn@gcc.gnu.org>
1999-12-02 9:32 ` David Wollmann
1999-12-31 22:24 ` David Wollmann
[not found] <943889159.18284.ezmlm-warn@gcc.gnu.org>
1999-11-29 8:36 ` Al Longyear
1999-11-30 23:28 ` Al Longyear
[not found] <941754663.30667.ezmlm-warn@gcc.gnu.org>
1999-11-04 22:33 ` Patrick Audley
1999-11-30 23:28 ` Patrick Audley
[not found] <935484852.22791.ezmlm-warn@gcc.gnu.org>
1999-10-01 0:00 ` Senthil Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH6eHdTRCx=xg_Zx+EYYw6PtE_=fySxTErMtj9wxLuFea8QQtw@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=vm.rod25@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).