Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0B58A186AF for ; Thu, 14 Jan 2016 17:20:17 +0000 (UTC) Received: (qmail 91880 invoked by uid 500); 14 Jan 2016 17:20:13 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 91832 invoked by uid 500); 14 Jan 2016 17:20:13 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 91822 invoked by uid 99); 14 Jan 2016 17:20:12 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jan 2016 17:20:12 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 7B2EF18028B for ; Thu, 14 Jan 2016 17:20:12 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3 X-Spam-Level: *** X-Spam-Status: No, score=3 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=rowe-clan-net.20150623.gappssmtp.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id x8ofVyxt5kwQ for ; Thu, 14 Jan 2016 17:19:59 +0000 (UTC) Received: from mail-ig0-f181.google.com (mail-ig0-f181.google.com [209.85.213.181]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 5CF0A2050D for ; Thu, 14 Jan 2016 17:19:59 +0000 (UTC) Received: by mail-ig0-f181.google.com with SMTP id z14so180829963igp.1 for ; Thu, 14 Jan 2016 09:19:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rowe-clan-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=5Y+NLDhdycasAJP2/edshbifbvVbEWOAkdgvvcWdE/k=; b=YB82uAogu4wPwA655dQ9TN4Ey32AcF4vJjYwur4o8VNNAtjv93TtyEA7zB5Od0RZXH s3zoknuGUyPGye8X9lMTcWSjD05KePnT+Ll/bshQ6mVJFpB4aIRoHOhYkyMWy9LaS8Ma nOj9AlL4uNcwzET3O+MRETowuGz8ZI+FFB17S9WFCWqFq2aAXWQ7MiKaktyRV1VcXfvX Joixkq/qRUhc2K2bHUA/0aJESMUN7W3MtkvFKvhMpgiUk82nnIKGrWVEo2W+uUOhmOQQ uTB+7sZLI22VgdXiWVRQDqh0BnOgBd7l1/ObnlWvUP+mblVQRcMLwvLQznTqomozSCxp HwPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=5Y+NLDhdycasAJP2/edshbifbvVbEWOAkdgvvcWdE/k=; b=iMJKNf6D8qgx8RJlKVid3/aGhlNbsIbmkfONxPTj0bCWj9Xidj3yB5vInH/ogf6a2H as2+vCsOHmlsb7D1nc3At28lU+4gsMuDAXbXmXPyFxytqebGGJDLUkqXc8KTfRam3aXB IwmHb7wWIIJ7LSas+laIdmJNIuLxF9ZbEKuu2QFESOauVkdW4x3hGtKANMgXi9zYazI5 UeI2tsoUwlogAIr+HTx71O4cWbp1UwbsNCOJu6rJpuYL2E1gwX9k9GYGT2FWa+wEk3dP lYCc2le9Mz3G83tZla7MwQTBZI6JnA8DRMRz69ap37AfWChHll8NyOqhUmPt5pNNN7nZ Z/Ew== X-Gm-Message-State: ALoCoQn6lQWOsI4NskFxNp5mfYIDiimtdlW9cL2GHFk/Hhb705Os6iC1IT6tzmbR77xhmNA+KuOON7OalexI1pYMZhTtvFZdqcWmOv+dLLJfmXsNwMizkY4= MIME-Version: 1.0 X-Received: by 10.50.4.38 with SMTP id h6mr6030823igh.32.1452791998766; Thu, 14 Jan 2016 09:19:58 -0800 (PST) Received: by 10.107.62.69 with HTTP; Thu, 14 Jan 2016 09:19:58 -0800 (PST) Received: by 10.107.62.69 with HTTP; Thu, 14 Jan 2016 09:19:58 -0800 (PST) In-Reply-To: <5693B558.3050201@lrz.de> References: <012701d14c6e$384032e0$a8c098a0$@idealgourmet.es> <5693A6CB.9040103@lrz.de> <5693B558.3050201@lrz.de> Date: Thu, 14 Jan 2016 11:19:58 -0600 Message-ID: From: William A Rowe Jr To: users@httpd.apache.org Content-Type: multipart/alternative; boundary=001a11c31322051df305294e7fde Subject: Re: [users@httpd] Blocking of users [was: Apache Server Access] --001a11c31322051df305294e7fde Content-Type: text/plain; charset=UTF-8 Precisely. We are likely to be switching mailing list mgmt platforms very soon, with luck we can preserve the subscribed address in such a way that unsubscribing users is less of a hassle. Right now the embedded list-unsubscribe fails to suggest the specific email address that needs to be unlinked. Third party subscriptions, unintentional or harassing the individual or the list, will happen. Let's assume the best intentions of users stuck in a list, please. On Jan 11, 2016 08:00, "Tobias Adolph" wrote: > Hi, > > Am 11.01.2016 um 14:07 schrieb Yehuda Katz: > > It's unfortunate that people can't figure out how to unsubscribe from a > mailing list that they subscribed to in the first place. > > > Maybe the person yelling isn't the same who subscribed to the list... > info@idealgourmet.es sounds not like an address that is dedicated to one > person only. Maybe an employee subscribed a long time ago and now the > person currently responsible for the inbox is just unable to cope with all > this - in his or her eyes - weird tech stuff. > > Therefore my proposal to manually remove/block the address. But it seems > that this has happened. > > Kind regards, > Tobias > --001a11c31322051df305294e7fde Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Precisely.=C2=A0 We are likely to be switching mailing list = mgmt platforms very soon, with luck we can preserve the subscribed address = in such a way that unsubscribing users is less of a hassle.=C2=A0 Right now= the embedded list-unsubscribe fails to suggest the specific email address = that needs to be unlinked.

Third party subscriptions, unintentional or harassing the in= dividual or the list, will happen.=C2=A0 Let's assume the best intentio= ns of users stuck in a list, please.

On Jan 11, 2016 08:00, "Tobias Adolph"= <Tobias.Adolph@lrz.de> w= rote:
=20 =20 =20
Hi,

Am 11.01.2016 um 14:07 schrieb Yehuda Katz:
=20

It's unfortunate that people can't figure out = how to unsubscribe from a mailing list that they subscribed to in the first place.


Maybe the person yelling isn't the same who subscribed to the list... info@= idealgourmet.es sounds not like an address that is dedicated to one person only. Maybe an employee subscribed a long time ago and now the person currently responsible for the inbox is just unable to cope with all this - in his or her eyes - weird tech stuff.

Therefore my proposal to manually remove/block the address. But it seems that this has happened.

Kind regards,
Tobias
--001a11c31322051df305294e7fde--