confirm unsubscribe to [email protected]
[email protected] 23 Jul 2009 10:39:54 -0000
| Newsgroups | gmane.comp.db.mysql.bugs |
|---|---|
| Message-ID | <[email protected]> |
To confirm that you would like [email protected] removed from the bugs mailing list, please click on the following link: http://lists.mysql.com/u/bugs/4a683dfabc25b628/gcdmb-bugs=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, [email protected] receives messages with return path: bugs-return-<number>[email protected]. --- Administrative commands for the bugs 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: <[email protected]> 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: <[email protected]> or for the digest to: <[email protected]> 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: <[email protected]> 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 6624 invoked by uid 48); 23 Jul 2009 10:39:52 -0000 Date: 23 Jul 2009 10:39:52 -0000 Message-ID: <[email protected]> To: [email protected] Subject: Unsubscribe request From: <[email protected]> This message was generated because of a request from 212.45.32.222.