Mailinglist Archive: opensuse-security (334 mails)

< Previous Next >
confirm subscribe to suse-security-announce@xxxxxxxx
  • From: "Fried Melgar, Gustavo" <GFried@xxxxxxxxxx>
  • Date: Fri, 5 Sep 2003 14:42:03 -0300
  • Message-id: <89DFDF0DBB95BF47AB7A83A5A72FC40241655F@xxxxxxxxxxxxxxxxxxxxxxx>



Hi! This is the ezmlm program. I'm managing the
suse-security-announce@xxxxxxxx mailing list.

I'm working for my owner, who can be reached
at suse-security-announce-owner@xxxxxxxxx

To confirm that you would like

gfried@xxxxxxxxxx

added to the suse-security-announce mailing list, please send
an empty reply to this address:

suse-security-announce-sc.1062783158.iojdggpfjelhjkmldalp-gfried=ute.com.uy@xxxxxxxx

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.


--- Administrative commands for the suse-security-announce 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:

For help and a description of available commands, send a message to:
<suse-security-announce-help@xxxxxxxx>

To subscribe to the list, send a message to:
<suse-security-announce-subscribe@xxxxxxxx>

To remove your address from the list, just send a message to
the address in the ``List-Unsubscribe'' header of any list
message. If you haven't changed addresses since subscribing,
you can also send a message to:
<suse-security-announce-unsubscribe@xxxxxxxx>

For addition or removal of addresses, I'll send a confirmation
message to that address. When you receive it, simply reply to it
to complete the transaction.

If you need to get in touch with the human owner of this list,
please send a message to:

<suse-security-announce-owner@xxxxxxxx>

Please include a FORWARDED list message with ALL HEADERS intact
to make it easier to help you.

--- Enclosed is a copy of the request I received.

Return-Path: <gfried@xxxxxxxxxx>
Received: (qmail 15627 invoked from network); 5 Sep 2003 17:32:37 -0000
Received: from ns.suse.de (HELO Cantor.suse.de) (195.135.220.2)
by 0 with SMTP; 5 Sep 2003 17:32:37 -0000
Received: from Hermes.suse.de (Hermes.suse.de [195.135.221.8])
(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
(No client certificate requested)
by Cantor.suse.de (Postfix) with ESMTP id 243C115B1B45
for <suse-security-announce-subscribe@xxxxxxxxxxxxxx>; Fri, 5 Sep 2003 19:32:37 +0200 (CEST)
Received: from Cantor.suse.de (ns.suse.de [195.135.220.2])
(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
(No client certificate requested)
by Hermes.suse.de (Postfix) with ESMTP id ADF0D8137
for <suse-security-announce-subscribe@xxxxxxxx>; Fri, 5 Sep 2003 19:32:36 +0200 (CEST)
Received: from turing.suse.de (Turing.suse.de [195.135.220.3])
by Cantor.suse.de (Postfix) with ESMTP id ED3D815B201F
for <suse-security-announce-subscribe@xxxxxxxx>; Fri, 5 Sep 2003 19:30:22 +0200 (CEST)
Date: Fri, 5 Sep 2003 19:30:22 +0200
From: gfried@xxxxxxxxxx
Message-Id: <200309051730.h85HUMu09816@xxxxxxxxxxxxxx>
To: undisclosed-recipients: ;



< Previous Next >
Follow Ups