On 2013-06-24 09:11, gcc-bugs-h...@gcc.gnu.org wrote:
Hi! This is the ezmlm program. I'm managing the
gcc-bugs@gcc.gnu.org mailing list.
To confirm that you would like
joop.boo...@boonen.org
removed from the gcc-bugs mailing list, please send an empty reply
to this address:
gcc-bugs-uc.1372057878.ilaghhpkihfgnfkidodi-joop.boonen=boonen@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.
I haven't checked whether your address is currently on the mailing
list.
To see what address you used to subscribe, look at the messages you
are
receiving from the mailing list. Each message has your address hidden
inside its return path; for example, m...@xdd.ff.com receives messages
with return path:
gcc-bugs-return-number-mary=xdd.ff@gcc.gnu.org.
Some mail programs are broken and cannot handle long addresses. If you
cannot reply to this request, instead send a message to
gcc-bugs-requ...@gcc.gnu.org and put the entire address listed above
into the Subject: line.
--- Administrative commands for the gcc-bugs 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-bugs-subscr...@gcc.gnu.org
To remove your address from the list, send a message to:
gcc-bugs-unsubscr...@gcc.gnu.org
Send mail to the following for info and FAQ for this list:
gcc-bugs-i...@gcc.gnu.org
gcc-bugs-...@gcc.gnu.org
Similar addresses exist for the digest list:
gcc-bugs-digest-subscr...@gcc.gnu.org
gcc-bugs-digest-unsubscr...@gcc.gnu.org
To get messages 123 through 145 (a maximum of 100 per request), mail:
gcc-bugs-get.123_...@gcc.gnu.org
To get an index with subject and author for messages 123-456 , mail:
gcc-bugs-index.123_...@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-bugs-thread.12...@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-bugs-subscribe-john=host.dom...@gcc.gnu.org
To stop subscription for this address, mail:
gcc-bugs-unsubscribe-john=host.dom...@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-bugs-ow...@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: anonym...@sourceware.org
Received: (qmail 28832 invoked by uid 48); 24 Jun 2013 07:11:18 -
Message-ID: 20130624071118.28829.qm...@sourceware.org
From: anonym...@sourceware.org
Date: Mon, 24 Jun 2013 07:11:18 +
To: gcc-bugs-unsubscribe-joop.boonen=boonen@sourceware.org
User-Agent: Heirloom mailx 12.4 7/29/08
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
