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