From: gcc-help-help@gcc.gnu.org
To: listarch-gcc-help@gcc.gnu.org
Subject: ezmlm warning
Date: Fri, 30 Aug 2013 06:38:00 -0000 [thread overview]
Message-ID: <1377826854.652.ezmlm-warn@gcc.gnu.org> (raw)
Hi! This is the ezmlm program. I'm managing the
gcc-help@gcc.gnu.org mailing list.
Messages to you from the gcc-help 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-help mailing list,
without further notice.
I've kept a list of which messages from the gcc-help 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-help-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-help-index@gcc.gnu.org>
Here are the message numbers:
53697
--- Enclosed is a copy of the bounce message I received.
Return-Path: <fnems.cqu@gmail.com>
Received: (qmail 23212 invoked by uid 89); 18 Aug 2013 08:53:56 -0000
X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.2
X-Spam-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.2
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on sourceware.org
X-Spam-Level:
Received: from mail-vb0-f68.google.com (HELO mail-vb0-f68.google.com) (209.85.212.68)
by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Sun, 18 Aug 2013 08:53:55 +0000
Received: by mail-vb0-f68.google.com with SMTP id e13so976864vbg.7
for <gcc-help-return-53697-listarch-gcc-help=gcc.gnu.org@gcc.gnu.org>; Sun, 18 Aug 2013 01:53:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:date:message-id:subject:from:to:content-type;
bh=tAiCJ1KIu5scewIQHdHST1PiIw/BGPoMG0koFfYOTZE=;
b=NSJp2NhX2ZLM5HUD9QcMVmPRfS1Zqg6khaEEVChNaAkYZ3IsiU2ObWKbHEEGDou2Wd
6wAnjN06zwdEQSPol9iFvhyqAfK7zV4zRg2PGuhcF3MqMoWSJHatrZRJo7i5bATHg4tQ
N+jHkP7KZ+/51nNr2knq+L9xjXITVzoQbQiIwDL5B3z+xUg57e1F2vJ9OnHmX1ouFUKw
wSvFTrXIFgFnyIOpbv5Y/6LCOcIkCXkW809cpaGgIsTb63MIiZat5cwR8mXJZc0PoPA1
p7bpOtbQiRnUqkWVJR6vbP0y4113divZSkGzapP4pBEb0H3ba8CWZR9+OpPsrIujijvY
GWYQ==
MIME-Version: 1.0
X-Received: by 10.52.180.229 with SMTP id dr5mr6025727vdc.20.1376816033905;
Sun, 18 Aug 2013 01:53:53 -0700 (PDT)
Received: by 10.221.41.196 with HTTP; Sun, 18 Aug 2013 01:53:53 -0700 (PDT)
Date: Sun, 18 Aug 2013 16:53:53 +0800
Message-ID: <CAM3-2K14-CUu7XVV--AQBRXbO=eFoRCcjfT5ta245BRHpFXAiw@mail.gmail.com>
Subject: Re: Stack Boundary
From: Felix <fnems.cqu@gmail.com>
To: gcc-help-return-53697-listarch-gcc-help=gcc.gnu.org@gcc.gnu.org
Content-Type: text/plain; charset=ISO-8859-1
I can see your attachment, though i don't know the solution.
next reply other threads:[~2013-08-30 1:40 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 6:38 gcc-help-help [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
-- strict thread matches above, loose matches on Subject: below --
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
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
[not found] <1440522165.122030.ezmlm-warn@gcc.gnu.org>
2015-08-25 18:03 ` Victor Rodriguez
2015-08-25 18:15 ` Jonathan Wakely
[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=1377826854.652.ezmlm-warn@gcc.gnu.org \
--to=gcc-help-help@gcc.gnu.org \
--cc=listarch-gcc-help@gcc.gnu.org \
/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).