--- /dev/null
+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 82F04431FAF\r
+ for <notmuch@notmuchmail.org>; Sun, 27 Jan 2013 14:05:57 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.001\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.001 tagged_above=-999 required=5\r
+ tests=[HTML_MESSAGE=0.001] 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 bY-rABGG9T2R for <notmuch@notmuchmail.org>;\r
+ Sun, 27 Jan 2013 14:05:53 -0800 (PST)\r
+X-Greylist: delayed 402 seconds by postgrey-1.32 at olra;\r
+ Sun, 27 Jan 2013 14:05:53 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 7490D431FAE\r
+ for <notmuch@notmuchmail.org>; Sun, 27 Jan 2013 14:05:53 -0800 (PST)\r
+Received: (qmail 23786 invoked from network); 27 Jan 2013 22:59: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; 27 Jan 2013 22:59:07 +0100\r
+From: "Robert Mast" <beheerder@tekenbeetziekten.nl>\r
+To: <notmuch@notmuchmail.org>\r
+Subject: Reply all - issue\r
+Date: Sun, 27 Jan 2013 22:58:58 +0100\r
+Message-ID: <000001cdfcd9$82500f00$86f02d00$@nl>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/alternative;\r
+ boundary="----=_NextPart_000_0001_01CDFCE1.E4147700"\r
+X-Mailer: Microsoft Office Outlook 12.0\r
+Thread-Index: Ac382YIPcFbBRELZQDerBAwMXRgaKA==\r
+Content-Language: nl\r
+X-Mailman-Approved-At: Sun, 27 Jan 2013 23:36:54 -0800\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: Sun, 27 Jan 2013 22:05:57 -0000\r
+\r
+This is a multi-part message in MIME format.\r
+\r
+------=_NextPart_000_0001_01CDFCE1.E4147700\r
+Content-Type: text/plain;\r
+ charset="us-ascii"\r
+Content-Transfer-Encoding: 7bit\r
+\r
+Last week I studied many Windows-Mail User Agents with the conversation\r
+threading feature.\r
+\r
+None of them (SUP, mutt-kz(notmuch), Outlook 2010, Thunderbird with\r
+conversation thread plug in, Postbox, Evolution) could cope with the\r
+following case:\r
+\r
+ \r
+\r
+In our e-mail-discussions people often choose 'reply-all' to construct a new\r
+message with the same reciepients.\r
+\r
+They clear the body and the subject, but the hidden References: and\r
+In-reply-To: stay and should be cleared as well.\r
+\r
+Result is that this new subject drowns in an old\r
+conversation-thread-drilldown and this unpredictable behavior makes\r
+conversation threading useless.\r
+\r
+This weekend I went analyzing the notmuch-source to find where I could put a\r
+fix best.\r
+\r
+ \r
+\r
+I think of a fix that indexes the first dates of (stripped) subject-changes\r
+within threads, and with each first (stripped) subject change check the body\r
+on quotes of previous messages. If there is no quote to referenced mails\r
+then drop the reference and assign a new thread_id_ to the (stripped)\r
+subject.\r
+\r
+ \r
+\r
+After two days of studying I think the best place with the least\r
+interference with existing code is between 'notmuch new' and starting the\r
+MUA. Then the threads are in place in XAPIAN, and new thread_id_'s can be\r
+inserted.\r
+\r
+ \r
+\r
+Am I right?\r
+\r
+ \r
+\r
+\r
+------=_NextPart_000_0001_01CDFCE1.E4147700\r
+Content-Type: text/html;\r
+ charset="us-ascii"\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =\r
+xmlns:o=3D"urn:schemas-microsoft-com:office:office" =\r
+xmlns:w=3D"urn:schemas-microsoft-com:office:word" =\r
+xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =\r
+xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =\r
+http-equiv=3DContent-Type content=3D"text/html; =\r
+charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =\r
+(filtered medium)"><style><!--\r
+/* Font Definitions */\r
+@font-face\r
+ {font-family:"Cambria Math";\r
+ panose-1:2 4 5 3 5 4 6 3 2 4;}\r
+@font-face\r
+ {font-family:Calibri;\r
+ panose-1:2 15 5 2 2 2 4 3 2 4;}\r
+/* Style Definitions */\r
+p.MsoNormal, li.MsoNormal, div.MsoNormal\r
+ {margin:0cm;\r
+ margin-bottom:.0001pt;\r
+ font-size:11.0pt;\r
+ font-family:"Calibri","sans-serif";}\r
+a:link, span.MsoHyperlink\r
+ {mso-style-priority:99;\r
+ color:blue;\r
+ text-decoration:underline;}\r
+a:visited, span.MsoHyperlinkFollowed\r
+ {mso-style-priority:99;\r
+ color:purple;\r
+ text-decoration:underline;}\r
+span.E-mailStijl17\r
+ {mso-style-type:personal-compose;\r
+ font-family:"Calibri","sans-serif";\r
+ color:windowtext;}\r
+.MsoChpDefault\r
+ {mso-style-type:export-only;}\r
+@page WordSection1\r
+ {size:612.0pt 792.0pt;\r
+ margin:70.85pt 70.85pt 70.85pt 70.85pt;}\r
+div.WordSection1\r
+ {page:WordSection1;}\r
+--></style><!--[if gte mso 9]><xml>\r
+<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />\r
+</xml><![endif]--><!--[if gte mso 9]><xml>\r
+<o:shapelayout v:ext=3D"edit">\r
+<o:idmap v:ext=3D"edit" data=3D"1" />\r
+</o:shapelayout></xml><![endif]--></head><body lang=3DNL link=3Dblue =\r
+vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =\r
+lang=3DEN-US>Last week I studied many Windows-Mail User Agents with the =\r
+conversation threading feature.<o:p></o:p></span></p><p =\r
+class=3DMsoNormal><span lang=3DEN-US>None of them (SUP, =\r
+mutt-kz(notmuch), Outlook 2010, Thunderbird with conversation thread =\r
+plug in, Postbox, Evolution) could cope with the following =\r
+case:<o:p></o:p></span></p><p class=3DMsoNormal><span =\r
+lang=3DEN-US><o:p> </o:p></span></p><p class=3DMsoNormal><span =\r
+lang=3DEN-US>In our e-mail-discussions people often choose =\r
+‘reply-all’ to construct a new message with the same =\r
+reciepients.<o:p></o:p></span></p><p class=3DMsoNormal><span =\r
+lang=3DEN-US>They clear the body and the subject, but the hidden =\r
+References: and In-reply-To: stay and should be cleared as =\r
+well.<o:p></o:p></span></p><p class=3DMsoNormal><span =\r
+lang=3DEN-US>Result is that this new subject drowns in an old =\r
+conversation-thread-drilldown and this unpredictable behavior makes =\r
+conversation threading useless.<o:p></o:p></span></p><p =\r
+class=3DMsoNormal><span lang=3DEN-US>This weekend I went analyzing the =\r
+notmuch-source to find where I could put a fix =\r
+best.<o:p></o:p></span></p><p class=3DMsoNormal><span =\r
+lang=3DEN-US><o:p> </o:p></span></p><p class=3DMsoNormal><span =\r
+lang=3DEN-US>I think of a fix that indexes the first dates of (stripped) =\r
+subject-changes within threads, and with each first (stripped) subject =\r
+change check the body on quotes of previous messages. If there is no =\r
+quote to referenced mails then drop the reference and assign a new =\r
+thread_id_ to the (stripped) subject.<o:p></o:p></span></p><p =\r
+class=3DMsoNormal><span lang=3DEN-US><o:p> </o:p></span></p><p =\r
+class=3DMsoNormal><span lang=3DEN-US>After two days of studying I think =\r
+the best place with the least interference with existing code is between =\r
+‘notmuch new’ and starting the MUA. Then the threads are in =\r
+place in XAPIAN, and new thread_id_’s can be =\r
+inserted.<o:p></o:p></span></p><p class=3DMsoNormal><span =\r
+lang=3DEN-US><o:p> </o:p></span></p><p class=3DMsoNormal><span =\r
+lang=3DEN-US>Am I right?<o:p></o:p></span></p><p class=3DMsoNormal><span =\r
+lang=3DEN-US><o:p> </o:p></span></p></div></body></html>\r
+------=_NextPart_000_0001_01CDFCE1.E4147700--\r
+\r
projects / notmuch-archives.git / commitdiff