From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <corbet@lwn.net>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN: AS63949 45.79.64.0/19
X-Spam-Status: No, score=-3.0 required=3.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,
	SPF_PASS,T_RP_MATCHES_RCVD shortcircuit=no autolearn=ham autolearn_force=no
	version=3.4.0
Received: from ms.lwn.net (ms.lwn.net [45.79.88.28])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by dcvr.yhbt.net (Postfix) with ESMTPS id 14DF01F42D
	for <meta@public-inbox.org>; Mon,  2 Apr 2018 14:36:17 +0000 (UTC)
Received: from lwn.net (localhost [127.0.0.1])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by ms.lwn.net (Postfix) with ESMTPSA id 91CA2305;
	Mon,  2 Apr 2018 14:36:16 +0000 (UTC)
Date: Mon, 2 Apr 2018 08:36:15 -0600
From: Jonathan Corbet <corbet@lwn.net>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: public-index-{watch,mda}
Message-ID: <20180402083615.3edf34ed@lwn.net>
Organization: LWN.net
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
List-Id: <meta.public-inbox.org>

I have a question on public-index-watch v. public-index-mda; sending to
the list since I might not be the only one.  I've seen a couple of times
that you recommend public-index-watch for maintaining a mirror of a
mailing list whose home is elsewhere.  But I would rather use
public-inbox-mda since that doesn't require keeping a duplicate maildir
around that's just wasted space.

So I'm wondering: is there a reason *not* to use public-inbox-mda for this
use case beyond the rather aggressive filtering that it does?  If not,
would you entertain a patch to make that filtering optional?

Thanks,

jon