confirm unsubscribe to myodbc@lists.mysql.com

confirm unsubscribe to myodbc@lists.mysql.com

am 15.04.2008 20:21:21 von myodbc-help

To confirm that you would like

gcdmo-myodbc@m.gmane.org

removed from the myodbc mailing list, please click on
the following link:

http://lists.mysql.com/u/myodbc/4804f2217a2ffcc8/gcdmo-myodb c=m.gmane.org

This confirmation serves two purposes. First, it verifies that we are
able to get mail through to you. Second, it protects you in case
someone forges a subscription request in your name.

We 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, john@example.com receives messages
with return path: myodbc-return--john=example.com@lists.mysql.com.


--- Administrative commands for the myodbc 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:


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:


or for the digest to:


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:



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.

Received: (qmail 29743 invoked by uid 48); 15 Apr 2008 18:21:20 -0000
Date: 15 Apr 2008 18:21:20 -0000
Message-ID: <20080415182120.29709.qmail@lists.mysql.com>
To: myodbc-unsubscribe-gcdmo-myodbc=m.gmane.org@lists.mysql.com
Subject: Unsubscribe request
From:

This message was generated because of a request from 84.179.121.199.