1 Return-Path: <sojkam1@fel.cvut.cz>
\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 A3838431FB6
\r
6 for <notmuch@notmuchmail.org>; Thu, 10 Feb 2011 22:55:34 -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 q1YfmpmgZuvD for <notmuch@notmuchmail.org>;
\r
16 Thu, 10 Feb 2011 22:55:33 -0800 (PST)
\r
17 Received: from max.feld.cvut.cz (max.feld.cvut.cz [147.32.192.36])
\r
18 by olra.theworths.org (Postfix) with ESMTP id 8E26A431FB5
\r
19 for <notmuch@notmuchmail.org>; Thu, 10 Feb 2011 22:55:33 -0800 (PST)
\r
20 Received: from localhost (unknown [192.168.200.4])
\r
21 by max.feld.cvut.cz (Postfix) with ESMTP id 90A7A19F338E;
\r
22 Fri, 11 Feb 2011 07:55:31 +0100 (CET)
\r
23 X-Virus-Scanned: IMAP AMAVIS
\r
24 Received: from max.feld.cvut.cz ([192.168.200.1])
\r
25 by localhost (styx.feld.cvut.cz [192.168.200.4]) (amavisd-new,
\r
27 with ESMTP id jrJo1U5ol0zq; Fri, 11 Feb 2011 07:55:30 +0100 (CET)
\r
28 Received: from imap.feld.cvut.cz (imap.feld.cvut.cz [147.32.192.34])
\r
29 by max.feld.cvut.cz (Postfix) with ESMTP id 58FAC19F3396;
\r
30 Fri, 11 Feb 2011 07:55:30 +0100 (CET)
\r
31 Received: from steelpick.2x.cz (note-sojka.felk.cvut.cz [147.32.86.30])
\r
32 (Authenticated sender: sojkam1)
\r
33 by imap.feld.cvut.cz (Postfix) with ESMTPSA id 4F3A5FA005;
\r
34 Fri, 11 Feb 2011 07:55:29 +0100 (CET)
\r
35 Received: from wsh by steelpick.2x.cz with local (Exim 4.72)
\r
36 (envelope-from <sojkam1@fel.cvut.cz>)
\r
37 id 1Pnmuf-0007LO-P7; Fri, 11 Feb 2011 07:55:29 +0100
\r
38 From: Michal Sojka <sojkam1@fel.cvut.cz>
\r
39 To: Jesse Rosenthal <jrosenthal@jhu.edu>, notmuch@notmuchmail.org
\r
40 Subject: Re: Remote usage script updated
\r
41 In-Reply-To: <m1k4h8syhi.fsf@watt.hwcampus.jhu.edu>
\r
42 References: <87oc72xs35.fsf@lucky.home> <87aaibylqe.fsf@steelpick.2x.cz>
\r
43 <87tygiowyi.fsf@wsheee.2x.cz>
\r
44 <m1k4h8syhi.fsf@watt.hwcampus.jhu.edu>
\r
45 User-Agent: Notmuch/0.5-103-g1253785 (http://notmuchmail.org) Emacs/23.2.1
\r
46 (x86_64-pc-linux-gnu)
\r
47 Date: Fri, 11 Feb 2011 07:55:29 +0100
\r
48 Message-ID: <877hd712n2.fsf@steelpick.2x.cz>
\r
50 Content-Type: text/plain; charset=us-ascii
\r
51 X-BeenThere: notmuch@notmuchmail.org
\r
52 X-Mailman-Version: 2.1.13
\r
54 List-Id: "Use and development of the notmuch mail system."
\r
55 <notmuch.notmuchmail.org>
\r
56 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
57 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
58 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
59 List-Post: <mailto:notmuch@notmuchmail.org>
\r
60 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
61 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
62 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
63 X-List-Received-Date: Fri, 11 Feb 2011 06:55:35 -0000
\r
65 On Wed, 09 Feb 2011, Jesse Rosenthal wrote:
\r
66 > By the way, I've also realized that most attachment downloading is done
\r
67 > not by "--format=raw" but by "notmuch part". It's possible to do caching
\r
68 > there as well. There are a few options there:
\r
70 > * One option would be to just cache by the attachment number -- but
\r
71 > this is very fragile if you delete an attachment through mutt or
\r
72 > some other client that allows it.
\r
74 This is obviously the simplest possibility. I do not know how often do
\r
75 you (and others) delete attachments, but I do it rarely and usually I
\r
76 delete all the attachments of the messages older than something. So this
\r
79 Additionally, I have added the following command to the attachment
\r
82 find ${CACHE} -ctime +$CACHE_MAX_DAYS -and -mtime +$CACHE_MAX_DAYS -print0 | xargs -r -0 rm -f
\r
84 It deletes attachments older than one week (in my case) so it there is
\r
85 some inconsistency, it would not last more than one week.
\r
87 > * cache by the hash of the attachment. The idea is that asking the
\r
88 > server to fetch it, hash it, and send the hash would still save
\r
89 > time over sending the whole attachment. Probably -- though most
\r
90 > attachments are small enough and most connections are fast enough
\r
91 > that this might not actually matter.
\r
93 If people do more weird things with their attachments, this is probably
\r
96 > * Actually stick the attachment hash in the json output in the first
\r
97 > place. But this would be a lot of trouble for a small gain for
\r