1 Return-Path: <jason@jasonjgw.net>
\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 44B2F4196F4
\r
6 for <notmuch@notmuchmail.org>; Tue, 6 Apr 2010 17:26:25 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=1.682 tagged_above=-999 required=5
\r
12 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
\r
13 DKIM_VALID_AU=-0.1, RDNS_DYNAMIC=0.982] autolearn=no
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id bmWRc+wZ3Com for <notmuch@notmuchmail.org>;
\r
17 Tue, 6 Apr 2010 17:26:24 -0700 (PDT)
\r
18 Received: from jdc.jasonjgw.net (ppp121-45-190-215.lns6.syd7.internode.on.net
\r
20 by olra.theworths.org (Postfix) with ESMTP id 49D144196F0
\r
21 for <notmuch@notmuchmail.org>; Tue, 6 Apr 2010 17:26:24 -0700 (PDT)
\r
22 Received: by jdc.jasonjgw.net (Postfix, from userid 1000)
\r
23 id C4EE41812029F; Wed, 7 Apr 2010 10:26:22 +1000 (EST)
\r
24 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=jasonjgw.net; s=mail;
\r
25 t=1270599982; bh=g0wMIHkRangIEo9gc5PNtTxl2HEYuuUwZGG+4iI7KYg=;
\r
26 h=Date:From:To:Subject:Message-ID:References:MIME-Version:
\r
27 Content-Type:In-Reply-To;
\r
28 b=FeLLN0HXrhMVE8YtB8RLFh2Ucu56U5z3lJDwMwa7/ilRhvNHw2ppHED3JvkshVIvQ
\r
29 pb3sDgf+BYdnpuBEf74XToR8te2OB+gNyij1sAj+SrKttr/wNd7YFvQeG6CERcKcpZ
\r
30 M97Nc2AK5E1rsqsIlEuKv0WYX+gb+MydBHeGUsjs=
\r
31 Date: Wed, 7 Apr 2010 10:26:22 +1000
\r
32 From: Jason White <jason@jasonjgw.net>
\r
33 To: notmuch <notmuch@notmuchmail.org>
\r
34 Subject: Re: [notmuch] Message parsing issue?
\r
35 Message-ID: <20100407002622.GA10289@jdc.jasonjgw.net>
\r
36 References: <20100403072540.GA15606@jdc.jasonjgw.net>
\r
37 <87fx384wp9.fsf@rocinante.cs.unb.ca>
\r
39 Content-Type: text/plain; charset=us-ascii
\r
40 Content-Disposition: inline
\r
41 In-Reply-To: <87fx384wp9.fsf@rocinante.cs.unb.ca>
\r
42 User-Agent: Mutt/1.5.20 (2009-06-14)
\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: Wed, 07 Apr 2010 00:26:25 -0000
\r
57 David Bremner <bremner@unb.ca> wrote:
\r
59 > One thing I noticed was that the message you sent (at least, if I got
\r
60 > the correct attachment), had X-Spam headers _before_ the "From "
\r
61 > line. If I remove those headers then the message displays Ok. It is
\r
62 > probably not worth putting too much effort into that display code since
\r
63 > it is in the process of being completely rewritten. Perhaps an extra
\r
64 > pass through "formail" can format you message headers a bit more nicely?
\r
66 I noticed this as well. I hope the new display code in Notmuch will be able to
\r
67 handle such cases, unless there are good reasons not to do so.
\r