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