From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <agk@redhat.com>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id LkRsyFnSA0op for <dm-crypt@saout.de>;
 Thu, 20 Dec 2012 17:55:49 +0100 (CET)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Thu, 20 Dec 2012 17:55:49 +0100 (CET)
Date: Thu, 20 Dec 2012 16:05:35 +0000
From: Alasdair G Kergon <agk@redhat.com>
Message-ID: <20121220160534.GD11558@agk-dp.fab.redhat.com>
References: <mailman.140.1351742424.23588.mailman@saout.de>
 <50D334DD.1060407@gmx.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <50D334DD.1060407@gmx.at>
Subject: [dm-crypt] [Off topic] Re: Fwd: saout.de mailing list
	memberships	reminder
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: Markus Krainz <ldm@gmx.at>
Cc: dm-crypt@saout.de

On Thu, Dec 20, 2012 at 04:55:09PM +0100, Markus Krainz wrote:
> I think the forwarded message speeks for itself :)

And your point is?

It's a compromise that seems to work pretty well for all sorts of reasons amply
debated elsewhere.

Similarly, the mailing list manager doesn't require every message to be GPG
signed yet the lists don't fill with forged email.

Alasdair