public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: slouken@twomix.devolution.com
To: gcc-help@gcc.gnu.org
Subject: Confirmation request (SpugSpam=conf:PSWbJYcbUDkZ6sS52LnULA==)
Date: Fri, 22 Sep 2006 14:40:00 -0000	[thread overview]
Message-ID: <E1GQmCX-0003SE-56@twomix.devolution.com> (raw)

Hi, this is a one-time confirmation message to verify that you are the
sender of the message below.  If you are, please reply with the following
text in the subject or body of the message:
   
(SpugSpam=conf:PSWbJYcbUDkZ6sS52LnULA==)
   
In most cases, just hitting "reply" should work.
   
Thanks!
	-Sam Lantinga, Senior Software Engineer, Blizzard Entertainment

--
Date: 22 Sep 2006 14:40:23 -0000
From: gcc-help@gcc.gnu.org
To: slouken@twomix.devolution.com
Subject: ezmlm response
Hi! This is the ezmlm program. I'm managing the
gcc@gcc.gnu.org mailing list.

Acknowledgment: The address

   slouken@twomix.devolution.com

was not on the gcc mailing list when I received
your request and is not a subscriber of this list.

If you unsubscribe, but continue to receive mail, you're subscribed
under a different address than you currently use. Please look at the
header for:

'Return-Path: <gcc-return-1234-user=host.dom@gcc.gnu.org>'

The unsubscribe address for this user would be:
'gcc-unsubscribe-user=host.dom@gcc.gnu.org'.
Just mail to that address, substituting user=host.dom for the real
values, reply to the confirmation request, and you should receive a message
that you're off the list.

For some mail programs, you need to make the headers visible to
see the return path:

             reply	other threads:[~2006-09-22 14:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-22 14:40 slouken [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-22 14:41 slouken
2006-09-22 14:38 slouken
2006-09-22 14:37 slouken

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=E1GQmCX-0003SE-56@twomix.devolution.com \
    --to=slouken@twomix.devolution.com \
    --cc=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).