--- /dev/null
+Return-Path: <MarkR.Andersom@amd.com>\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 DE23E431FBC\r
+ for <notmuch@notmuchmail.org>; Wed, 23 Dec 2009 14:08:05 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\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 enTJbBWWKaqo for <notmuch@notmuchmail.org>;\r
+ Wed, 23 Dec 2009 14:08:03 -0800 (PST)\r
+Received: from VA3EHSOBE002.bigfish.com (va3ehsobe002.messaging.microsoft.com\r
+ [216.32.180.12])\r
+ by olra.theworths.org (Postfix) with ESMTP id CAAB9431FAE\r
+ for <notmuch@notmuchmail.org>; Wed, 23 Dec 2009 14:08:03 -0800 (PST)\r
+Received: from mail132-va3-R.bigfish.com (10.7.14.245) by\r
+ VA3EHSOBE002.bigfish.com (10.7.40.22) with Microsoft SMTP Server id\r
+ 8.1.240.5; Wed, 23 Dec 2009 22:08:03 +0000\r
+Received: from mail132-va3 (localhost.localdomain [127.0.0.1]) by\r
+ mail132-va3-R.bigfish.com (Postfix) with ESMTP id DFE6613B81D3;\r
+ Wed, 23 Dec 2009 22:08:02 +0000 (UTC)\r
+X-SpamScore: -20\r
+X-BigFish: VPS-20(zz1432R1453M98dNzz1202hzzz32i6bh61h)\r
+X-Spam-TCS-SCL: 0:0\r
+Received: from mail132-va3 (localhost.localdomain [127.0.0.1]) by mail132-va3\r
+ (MessageSwitch) id 1261606079137914_2864;\r
+ Wed, 23 Dec 2009 22:07:59 +0000 (UTC)\r
+Received: from VA3EHSMHS036.bigfish.com (unknown [10.7.14.237]) by\r
+ mail132-va3.bigfish.com (Postfix) with ESMTP id 818591080057;\r
+ Wed, 23 Dec 2009 22:07:58 +0000 (UTC)\r
+Received: from ausb3extmailp02.amd.com (163.181.251.22) by\r
+ VA3EHSMHS036.bigfish.com (10.7.99.46) with Microsoft SMTP Server (TLS)\r
+ id 14.0.482.32; Wed, 23 Dec 2009 22:07:55 +0000\r
+Received: from ausb3twp02.amd.com ([163.181.250.38]) by\r
+ ausb3extmailp02.amd.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id\r
+ nBNM7p9m029510; Wed, 23 Dec 2009 16:07:54 -0600\r
+X-WSS-ID: 0KV4LH1-02-58D-02\r
+X-M-MSG: \r
+Received: from sausexbh2.amd.com (SAUSEXBH2.amd.com [163.181.22.102]) by\r
+ ausb3twp02.amd.com (Tumbleweed MailGate 3.7.2) with ESMTP id\r
+ 26AA6FCC3F5; Wed, 23 Dec 2009 16:07:48 -0600 (CST)\r
+Received: from sausexmb6.amd.com ([163.181.49.140]) by sausexbh2.amd.com with\r
+ Microsoft SMTPSVC(6.0.3790.3959); Wed, 23 Dec 2009 16:07:49 -0600\r
+Received: from optimon.amd.com ([163.181.34.104]) by sausexmb6.amd.com with\r
+ Microsoft SMTPSVC(6.0.3790.3959); Wed, 23 Dec 2009 16:07:49 -0600\r
+Received: from mhdc-ns01.amd.com (mhdc-ns01.amd.com [165.204.35.147]) by\r
+ optimon.amd.com (8.12.10/8.12.10) with ESMTP id nBNM7nCG013525;\r
+ Wed, 23 Dec 2009 16:07:49 -0600\r
+Received: from testarossa.amd.com (testarossa.amd.com [165.204.147.44]) by\r
+ mhdc-ns01.amd.com (8.13.8+Sun/8.13.8) with ESMTP id nBNM7m1n018616;\r
+ Wed, 23 Dec 2009 15:07:48 -0700 (MST)\r
+Received: (from manderso@localhost) by testarossa.amd.com\r
+ (8.13.1/8.13.1/Submit) id nBNM7lDc013462;\r
+ Wed, 23 Dec 2009 15:07:47 -0700\r
+X-Authentication-Warning: testarossa.amd.com: manderso set sender to\r
+ MarkR.Andersom@amd.com using -f\r
+From: Mark Anderson <markr.anderson@amd.com>\r
+To: Marten Veldthuis <marten@veldthuis.com>, Carl Worth <cworth@cworth.org>,\r
+ notmuch <notmuch@notmuchmail.org>\r
+In-Reply-To:\r
+ <87my1kkzbn.fsf@marten.i-did-not-set--mail-host-address--so-tickle-me>\r
+References: <1260400470-sup-5775@testarossa>\r
+ <87ws0ug23f.fsf@yoom.home.cworth.org>\r
+ <87ljha3avx.fsf@home.veldthuis.com>\r
+ <87ocm64ivu.fsf@yoom.home.cworth.org>\r
+ <87my1kkzbn.fsf@marten.i-did-not-set--mail-host-address--so-tickle-me>\r
+Date: Wed, 23 Dec 2009 15:07:47 -0700\r
+Message-ID: <3wdzl59mjik.fsf@testarossa.amd.com>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset="us-ascii"\r
+X-OriginalArrivalTime: 23 Dec 2009 22:07:49.0386 (UTC)\r
+ FILETIME=[5D5DCEA0:01CA841C]\r
+X-Reverse-DNS: ausb3extmailp02.amd.com\r
+Subject: Re: [notmuch] Threading\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.12\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: Wed, 23 Dec 2009 22:08:06 -0000\r
+\r
+On Tue, 15 Dec 2009 16:54:20 +0100, Marten Veldthuis <marten@veldthuis.com> wrote:\r
+> On Thu, 10 Dec 2009 13:30:13 -0800, Carl Worth <cworth@cworth.org> wrote:\r
+> > But I still have a hard time justifying user operations to manipulate\r
+> > threading. The whole point of threading is to make it faster to process\r
+> > and read messages. But manual operations like joining and splitting\r
+> > threads seem like the user just doing more work, and that *after* having\r
+> > read the messages. So that seems mostly backwards to me.\r
+> \r
+> By the way, Outlook & Exchange suck (or at least some versions do), and\r
+> don't seem to generate In-Reply-To and References: headers. Just got a\r
+> mail which prompted me to write this mail. I'd really like to be able to\r
+> join messages in a case like this.\r
+\r
+It's actually worse than that. I was looking into why some of my\r
+threads weren't coalescing. Some of it seems to be a very difficult bug\r
+DB that doesn't use identical Message-ID's to refer to the parent bug\r
+mail. I don't know how that works at all. Sometimes it uses the same\r
+Message-ID, but sometimes it changes a number in the ID.\r
+\r
+However, this isn't the worst news, because I work with a lot of\r
+Exchange users, and I noticed that their mail was also refusing to\r
+thread.\r
+\r
+I was looking at the message bodies, and they led me to these links\r
+about mail processing.\r
+\r
+The problem identified:\r
+http://blog.postmaster.gr/2007/12/11/trying-to-make-use-of-outlooks-thread-index-header/\r
+\r
+How to read it, or how Exchange goes its own way:\r
+http://blog.postmaster.gr/2007/12/23/more-fun-with-message-threading/\r
+\r
+With a fairly loose understanding of how notmuch detects threads, and\r
+how much information it places in the Xapian database (only the\r
+msg-id?), I can't suggest much of the how.\r
+\r
+But I would like to propose that we consider handling the Exchange\r
+non-standard threading method as well as the RFC822 threading in the\r
+headers.\r
+\r
+Reactions?\r
+\r
+-Mark\r
+\r
projects / notmuch-archives.git / blobdiff