RE: Reply all - issue

diff --git a/a2/86c29873d54237ff3984cf086f835e20f0cb3c b/a2/86c29873d54237ff3984cf086f835e20f0cb3c
new file mode 100644 (file)
index 0000000..1875588
--- /dev/null
+++ b/a2/86c29873d54237ff3984cf086f835e20f0cb3c
@@ -0,0 +1,105 @@
+Return-Path: <beheerder@tekenbeetziekten.nl>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 2E404431FBC\r
+       for <notmuch@notmuchmail.org>; Mon, 11 Feb 2013 12:09:54 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id y-LxznREmouH for <notmuch@notmuchmail.org>;\r
+       Mon, 11 Feb 2013 12:09:53 -0800 (PST)\r
+Received: from srv047132.webreus.nl (srv047132.webreus.nl [46.235.47.132])\r
+       (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id AA0AF431FAE\r
+       for <notmuch@notmuchmail.org>; Mon, 11 Feb 2013 12:09:52 -0800 (PST)\r
+Received: (qmail 7816 invoked from network); 10 Feb 2013 16:43:09 +0100\r
+Received: from ip73-109-210-87.adsl2.static.versatel.nl (HELO PCvangebruike)\r
+       (87.210.109.73)\r
+       by srv047132.webreus.nl with SMTP; 10 Feb 2013 16:42:59 +0100\r
+From: "Robert Mast" <beheerder@tekenbeetziekten.nl>\r
+To: <notmuch@notmuchmail.org>\r
+References: <000001cdfcd9$82500f00$86f02d00$@nl>\r
+       <CA+pa1O0mTxkj_FMQH_jXWajmUAKHWbMsB4Yhp_4UX7hnhwgBrg@mail.gmail.com>\r
+       <000001ce0161$5da40990$18ec1cb0$@nl>\r
+       <87a9rml9pm.fsf@zancas.localnet>\r
+In-Reply-To: <87a9rml9pm.fsf@zancas.localnet>\r
+Subject: RE: Reply all - issue\r
+Date: Sun, 10 Feb 2013 16:43:01 +0100\r
+Message-ID: <00a501ce07a5$4edcbb10$ec963130$@nl>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain;\r
+       charset="utf-8"\r
+Content-Transfer-Encoding: quoted-printable\r
+X-Mailer: Microsoft Office Outlook 12.0\r
+Thread-Index: Ac4Bh0PMAEUftH8lRH6w+fV5DvJa7QGDuB6A\r
+Content-Language: nl\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 11 Feb 2013 20:09:54 -0000\r
+\r
+>From many replies I understand manual thread-joining and -breaking =\r
+exists with mutt's manual commands and default subject breaking -as =\r
+Gmail does- would not be preferred, while not only version control =\r
+systems vary subjects within a thread, but also discussions with slight =\r
+off-topic forks and therefore slightly changed subjects should stay in =\r
+the same thread.\r
+\r
+The reason why I asked my question in the first place is because I have =\r
+lots of mail-discussions going on between about 10 board-members who are =\r
+not able to meet in real life often enough to decide everything by =\r
+conference, so our mailboxes pile up with suggestions, remarks with =\r
+longer growing thread-histories and evolving addressee-lists. Those =\r
+addressee-lists vary by individual choice, often without confirmation of =\r
+other participants to involve some new addressee's, sometimes resulting =\r
+in leakage.\r
+\r
+I thought to revive mail2forum, a plug-in for phpBB, to force people to =\r
+use existing addressee-lists per 'circle' and archive all =\r
+e-maildiscussions in a forum, so people wouldn't be e-mailed for every =\r
+subject and could lose/drop their own mail. Threads should be compressed =\r
+to keep mostly only original messages - if available -, and small =\r
+citations, or links to original texts if needed. This thread-compression =\r
+is functionality the existing mail2forum doesn't have, so that's where =\r
+for example notmuch comes in.\r
+\r
+Discussing around I understand that phpBB misses the very basic feature =\r
+of thread-forking: Every slightly off-topic remark in a phpBB-message =\r
+can only be splitted to a completely new thread.\r
+\r
+I wonder whether that is blocking for my own situation, as participants =\r
+in our discussions don't change the subject-line very often, but it =\r
+could probably affect the viability of mail2forum as an open =\r
+source-project.\r
+\r
+I don't see how I can easily manually manipulate threads with a mail =\r
+client when mail2forum automatically reads and processes new incoming =\r
+mail, so my efforts with notmuch will probably stick to the 'optional' =\r
+subject-splitting-solution.\r
+\r
+As, however, mail2forum should handle postponed e-mail as well (and =\r
+exchange former quotes with their original texts), probably patching =\r
+from a manually altered maildir wouldn't be such a big step. I however =\r
+haven't studied all that's needed there yet.\r
+\r
+By the way, before I spend too much time on mail2forum - does anyone =\r
+know an (open source?) group-mail project with user authentication to =\r
+centrally stored messages that already does have satisfying =\r
+thread-compression?\r
+\r