On 11/05/2018 11:32 PM, gcc-patches-h...@gcc.gnu.org wrote:
> Hi! This is the ezmlm program. I'm managing the
> gcc-patches@gcc.gnu.org mailing list.
>
> To confirm that you would like
>
>    t...@kompiler.org
>
> added to the gcc-patches mailing list, please send
> an empty reply to this address:
>
>    gcc-patches-sc.1541457171.macebnkebakhpagdepob-tim=kompiler....@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-patches-requ...@gcc.gnu.org> and put the
> entire address listed above into the "Subject:" line.
>
>
> --- Administrative commands for the gcc-patches 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-patches-subscr...@gcc.gnu.org>
>
> To remove your address from the list, send a message to:
>    <gcc-patches-unsubscr...@gcc.gnu.org>
>
> Send mail to the following for info and FAQ for this list:
>    <gcc-patches-i...@gcc.gnu.org>
>    <gcc-patches-...@gcc.gnu.org>
>
> Similar addresses exist for the digest list:
>    <gcc-patches-digest-subscr...@gcc.gnu.org>
>    <gcc-patches-digest-unsubscr...@gcc.gnu.org>
>
> To get messages 123 through 145 (a maximum of 100 per request), mail:
>    <gcc-patches-get.123_...@gcc.gnu.org>
>
> To get an index with subject and author for messages 123-456 , mail:
>    <gcc-patches-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-patches-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-patches-subscribe-john=host.dom...@gcc.gnu.org>
>
> To stop subscription for this address, mail:
> <gcc-patches-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-patches-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 96649 invoked by uid 48); 5 Nov 2018 22:32:50 -0000
> Message-ID: <20181105223250.96646.qm...@sourceware.org>
> From: anonym...@sourceware.org
> Date: Mon, 05 Nov 2018 22:32:50 +0000
> To: gcc-patches-subscribe-tim=kompiler....@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
>
>

Reply via email to