From: <stephen.mcgowen@upcmail.ie>
To: gcc-sc.1338392813.djoibchpffcfojcjhieo-stephen.mcgowen=upcmail.ie@gcc.gnu.org
Cc: gcc-help@gcc.gnu.org
Subject: Re: confirm subscribe to gcc@gcc.gnu.org
Date: Wed, 30 May 2012 15:50:00 -0000 [thread overview]
Message-ID: <20120530175013.FJ3X3.101597.root@viefep30> (raw)
In-Reply-To: <1338392813.14106.ezmlm@gcc.gnu.org>
---- gcc-help@gcc.gnu.org wrote:
> Hi! This is the ezmlm program. I'm managing the
> gcc@gcc.gnu.org mailing list.
>
> To confirm that you would like
>
> stephen.mcgowen@upcmail.ie
>
> added to the gcc mailing list, please send
> an empty reply to this address:
>
> gcc-sc.1338392813.djoibchpffcfojcjhieo-stephen.mcgowen=upcmail.ie@gcc.gnu.org
>
> Usually, this happens when you just hit the "reply" button.
> If this does not work, simply copy the address and paste it into
> the "To:" field of a new message.
>
> This confirmation serves two purposes. First, it verifies that I am able
> to get mail through to you. Second, it protects you in case someone
> forges a subscription request in your name.
>
> Some mail programs are broken and cannot handle long addresses. If you
> cannot reply to this request, instead send a message to
> <gcc-request@gcc.gnu.org> and put the
> entire address listed above into the "Subject:" line.
>
>
> --- Administrative commands for the gcc list ---
>
> I can handle administrative requests automatically. Please
> do not send them to the list address! Instead, send
> your message to the correct command address:
>
> To subscribe to the list, send a message to:
> <gcc-subscribe@gcc.gnu.org>
>
> To remove your address from the list, send a message to:
> <gcc-unsubscribe@gcc.gnu.org>
>
> Send mail to the following for info and FAQ for this list:
> <gcc-info@gcc.gnu.org>
> <gcc-faq@gcc.gnu.org>
>
> Similar addresses exist for the digest list:
> <gcc-digest-subscribe@gcc.gnu.org>
> <gcc-digest-unsubscribe@gcc.gnu.org>
>
> To get messages 123 through 145 (a maximum of 100 per request), mail:
> <gcc-get.123_145@gcc.gnu.org>
>
> To get an index with subject and author for messages 123-456 , mail:
> <gcc-index.123_456@gcc.gnu.org>
>
> They are always returned as sets of 100, max 2000 per request,
> so you'll actually get 100-499.
>
> To receive all messages with the same subject as message 12345,
> send an empty message to:
> <gcc-thread.12345@gcc.gnu.org>
>
> The messages do not really need to be empty, but I will ignore
> their content. Only the ADDRESS you send to is important.
>
> You can start a subscription for an alternate address,
> for example "john@host.domain", just add a hyphen and your
> address (with '=' instead of '@') after the command word:
> <gcc-subscribe-john=host.domain@gcc.gnu.org>
>
> To stop subscription for this address, mail:
> <gcc-unsubscribe-john=host.domain@gcc.gnu.org>
>
> In both cases, I'll send a confirmation message to that address. When
> you receive it, simply reply to it to complete your subscription.
>
> If despite following these instructions, you do not get the
> desired results, please contact my owner at
> gcc-owner@gcc.gnu.org. Please be patient, my owner is a
> lot slower than I am ;-)
>
> --- Enclosed is a copy of the request I received.
>
> Return-Path: <anonymous@sourceware.org>
> Received: (qmail 14101 invoked by uid 48); 30 May 2012 15:46:52 -0000
> Date: 30 May 2012 15:46:52 -0000
> Message-ID: <20120530154652.14099.qmail@sourceware.org>
> From: anonymous@sourceware.org
> To: gcc-subscribe-stephen.mcgowen=upcmail.ie@sourceware.org
>
>
next parent reply other threads:[~2012-05-30 15:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1338392813.14106.ezmlm@gcc.gnu.org>
2012-05-30 15:50 ` stephen.mcgowen [this message]
[not found] <1576253971.61554.ezmlm@gcc.gnu.org>
2019-12-13 16:20 ` Mário Nunes
[not found] <1544990764.42581.ezmlm@gcc.gnu.org>
2018-12-16 22:14 ` Jan Nieuwenhuizen
[not found] <1423452188.27593.ezmlm@gcc.gnu.org>
2015-02-09 3:26 ` Mike Gerwitz
[not found] <1391682002.26568.ezmlm@gcc.gnu.org>
2014-02-06 10:20 ` Jose E. Marchesi
[not found] <1339709568.26023.ezmlm@gcc.gnu.org>
2012-06-14 21:46 ` Walter Landry
[not found] <1319440213.13024.ezmlm@gcc.gnu.org>
2011-10-24 7:11 ` Konrad Eisele
[not found] <1315596074.8711.ezmlm@gcc.gnu.org>
2011-09-09 19:22 ` Maxim Kuvyrkov
[not found] <1306025540.13065.ezmlm@gcc.gnu.org>
2011-05-22 7:37 ` Ruben Safir
2011-05-23 15:44 ` Ian Lance Taylor
[not found] <1301666245.9803.ezmlm@gcc.gnu.org>
2011-04-01 13:58 ` Sho Nakatani
2010-05-10 11:51 ahmet mutlu
[not found] <1104130803.3845.ezmlm@gcc.gnu.org>
2004-12-27 7:01 ` Shibata Yukishige
[not found] <1096179730.21325.ezmlm@gcc.gnu.org>
2004-09-26 6:33 ` Demo Account
[not found] <1070590073.30546.ezmlm@gcc.gnu.org>
2003-12-05 2:10 ` Jerry
[not found] <1029427898.13215.ezmlm@gcc.gnu.org>
2002-08-15 9:13 ` Mat Harris
[not found] <1021057403.21550.ezmlm@gcc.gnu.org>
2002-05-10 12:06 ` David Gerber
[not found] <(eti>
[not found] ` <pan)>
2001-07-27 21:23 ` eti pan
[not found] <989247623.4183.ezmlm@gcc.gnu.org>
2001-05-07 8:07 ` adam morley
[not found] <973234577.31557.ezmlm@gcc.gnu.org>
2000-11-02 22:59 ` Hiroaki Etoh
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=20120530175013.FJ3X3.101597.root@viefep30 \
--to=stephen.mcgowen@upcmail.ie \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc-sc.1338392813.djoibchpffcfojcjhieo-stephen.mcgowen=upcmail.ie@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).