Hi! This is the ezmlm program. I'm managing the gcc@xxxxxxxxxxx mailing list.
Acknowledgment: I have added the address
pupuru@xxxxxxxxxx
to the gcc mailing list.
Welcome to gcc@xxxxxxxxxxx!
Please save this message so that you know the address you are subscribed under, in case you later want to unsubscribe or change your subscription address.
--- 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@xxxxxxxxxxx>
To remove your address from the list, send a message to: <gcc-unsubscribe@xxxxxxxxxxx>
Send mail to the following for info and FAQ for this list: <gcc-info@xxxxxxxxxxx> <gcc-faq@xxxxxxxxxxx>
Similar addresses exist for the digest list: <gcc-digest-subscribe@xxxxxxxxxxx> <gcc-digest-unsubscribe@xxxxxxxxxxx>
To get messages 123 through 145 (a maximum of 100 per request), mail: <gcc-get.123_145@xxxxxxxxxxx>
To get an index with subject and author for messages 123-456 , mail: <gcc-index.123_456@xxxxxxxxxxx>
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@xxxxxxxxxxx>
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@xxxxxxxxxxx", just add a hyphen and your address (with '=' instead of '@') after the command word: <gcc-subscribe-john=host.domain@xxxxxxxxxxx>
To stop subscription for this address, mail: <gcc-unsubscribe-john=host.domain@xxxxxxxxxxx>
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@xxxxxxxxxxxx Please be patient, my owner is a lot slower than I am ;-)
--- Enclosed is a copy of the request I received.
Return-Path: <pupuru@xxxxxxxxxx> Received: (qmail 24276 invoked from network); 8 Apr 2004 01:11:07 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 8 Apr 2004 01:11:07 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i381B6WB023921; Wed, 7 Apr 2004 21:11:06 -0400 Received: from ns.tokyo.redhat.com (ns.tokyo.redhat.com [172.16.33.1]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i381B5j30035; Wed, 7 Apr 2004 21:11:05 -0400 Received: from kornet.net (host11.seoul.redhat.com [172.16.23.111]) by ns.tokyo.redhat.com (8.11.6/8.11.6) with ESMTP id i381ArD18149; Thu, 8 Apr 2004 10:10:53 +0900 Message-ID: <4074A6E9.9040300@xxxxxxxxxx> Date: Thu, 08 Apr 2004 10:12:09 +0900 From: Hoe-Seong Ha <pupuru@xxxxxxxxxx> User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gcc-sc.1081386299.gebcljbdjaomdaflnmaj-pupuru=kornet.net@xxxxxxxxxxx Subject: Re: confirm subscribe to gcc@xxxxxxxxxxx References: <108138630571858726.0.ppp9@ppp9> In-Reply-To: <108138630571858726.0.ppp9@ppp9> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit
gcc-help@xxxxxxxxxxx wrote:
Hi! This is the ezmlm program. I'm managing the gcc@xxxxxxxxxxx mailing list.
To confirm that you would like
pupuru@xxxxxxxxxx
added to the gcc mailing list, please send an empty reply to this address:
gcc-sc.1081386299.gebcljbdjaomdaflnmaj-pupuru=kornet.net@xxxxxxxxxxx
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@xxxxxxxxxxx> 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@xxxxxxxxxxx>
To remove your address from the list, send a message to: <gcc-unsubscribe@xxxxxxxxxxx>
Send mail to the following for info and FAQ for this list: <gcc-info@xxxxxxxxxxx> <gcc-faq@xxxxxxxxxxx>
Similar addresses exist for the digest list: <gcc-digest-subscribe@xxxxxxxxxxx> <gcc-digest-unsubscribe@xxxxxxxxxxx>
To get messages 123 through 145 (a maximum of 100 per request), mail: <gcc-get.123_145@xxxxxxxxxxx>
To get an index with subject and author for messages 123-456 , mail: <gcc-index.123_456@xxxxxxxxxxx>
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@xxxxxxxxxxx>
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@xxxxxxxxxxx", just add a hyphen and your address (with '=' instead of '@') after the command word: <gcc-subscribe-john=host.domain@xxxxxxxxxxx>
To stop subscription for this address, mail: <gcc-unsubscribe-john=host.domain@xxxxxxxxxxx>
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@xxxxxxxxxxxx Please be patient, my owner is a lot slower than I am ;-)
--- Enclosed is a copy of the request I received.
Return-Path: <anonymous@xxxxxxxxxxx> Received: (qmail 14984 invoked by uid 48); 8 Apr 2004 01:04:58 -0000 Date: 8 Apr 2004 01:04:58 -0000 Message-ID: <20040408010458.14978.qmail@xxxxxxxxxxxxxxxxxx> From: anonymous@xxxxxxxxxxx To: gcc-subscribe-pupuru=kornet.net@xxxxxxxxxxx
