1 Return-Path: <jani@nikula.org>
\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 80BE8431FB6
\r
6 for <notmuch@notmuchmail.org>; Wed, 4 Apr 2012 00:38:45 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5
\r
12 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\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 6i+HHI+bUZXz for <notmuch@notmuchmail.org>;
\r
16 Wed, 4 Apr 2012 00:38:45 -0700 (PDT)
\r
17 Received: from mail-qa0-f43.google.com (mail-qa0-f43.google.com
\r
18 [209.85.216.43]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
\r
19 (No client certificate requested)
\r
20 by olra.theworths.org (Postfix) with ESMTPS id D86F5431FAE
\r
21 for <notmuch@notmuchmail.org>; Wed, 4 Apr 2012 00:38:44 -0700 (PDT)
\r
22 Received: by qadb15 with SMTP id b15so235570qad.2
\r
23 for <notmuch@notmuchmail.org>; Wed, 04 Apr 2012 00:38:43 -0700 (PDT)
\r
24 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
\r
25 d=google.com; s=20120113;
\r
26 h=from:to:subject:in-reply-to:references:user-agent:date:message-id
\r
27 :mime-version:content-type:x-gm-message-state;
\r
28 bh=58Hyg8+IuiynGQY16ctH3doLQiLp7A6vl0A3fgAAm80=;
\r
29 b=bRbV1jIKeHJtnVTQNLKC3qpfHiRdYoaJtZp9lG83oWYB08cWLnTrsvhJcMi5uvN6hi
\r
30 QlXFN9sUK5VzL4xlZPEQBTfuTkd6d0JTHh+vMTf758k11EeXQsA5Q0A/gnZOloIg8oKh
\r
31 /ceHPvHq7CBJk2coVwQqopsc/5te96ELcrY9sI0YNJIbTA5v1LO/2GEau/c/MWyKOECl
\r
32 qUyqyzTW396aQ2q/ZW9UVxNxjCBHfGU/7kUkIPmQkvio/pQTQEIZu3/RHFp5EGiSxxc9
\r
33 iac++jAzP8BGcdRy/Lh7X/zlI+kFsUhW02AnhPR845zMdOzhPkF96cOdEM4OlfmH/c3z
\r
35 Received: by 10.224.209.74 with SMTP id gf10mr21444714qab.8.1333525121972;
\r
36 Wed, 04 Apr 2012 00:38:41 -0700 (PDT)
\r
37 Received: from localhost (nikula.org. [92.243.24.172])
\r
38 by mx.google.com with ESMTPS id df8sm152547qab.6.2012.04.04.00.38.39
\r
39 (version=SSLv3 cipher=OTHER); Wed, 04 Apr 2012 00:38:41 -0700 (PDT)
\r
40 From: Jani Nikula <jani@nikula.org>
\r
41 To: Jameson Graef Rollins <jrollins@finestructure.net>,
\r
42 Jacek Generowicz <jacek.generowicz@cern.ch>, notmuch@notmuchmail.org
\r
43 Subject: Re: Message deletion wisdom
\r
44 In-Reply-To: <87sjgk2xzf.fsf@servo.finestructure.net>
\r
45 References: <0cc49af3-5415-419d-97ef-2bec76117d63@CERNFE22.cern.ch>
\r
46 <87sjgk2xzf.fsf@servo.finestructure.net>
\r
47 User-Agent: Notmuch/0.11.1+222~ga47a98c (http://notmuchmail.org) Emacs/23.1.1
\r
49 Date: Wed, 04 Apr 2012 07:38:37 +0000
\r
50 Message-ID: <87mx6sx7ya.fsf@nikula.org>
\r
52 Content-Type: text/plain; charset=us-ascii
\r
54 ALoCoQl7X0awS/HlfAWQGXM5PFJaIlMX+ror4LOKmWGuu0yY9JCfLksykj0dx/DVLa8rIcH8DC4W
\r
55 X-BeenThere: notmuch@notmuchmail.org
\r
56 X-Mailman-Version: 2.1.13
\r
58 List-Id: "Use and development of the notmuch mail system."
\r
59 <notmuch.notmuchmail.org>
\r
60 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
61 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
62 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
63 List-Post: <mailto:notmuch@notmuchmail.org>
\r
64 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
65 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
66 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
67 X-List-Received-Date: Wed, 04 Apr 2012 07:38:45 -0000
\r
69 On Tue, 03 Apr 2012 16:32:04 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
\r
70 > On Tue, Apr 03 2012, Jacek Generowicz <jacek.generowicz@cern.ch> wrote:
\r
71 > > Looking through the archives of this list, I see that the topic of
\r
72 > > message deletion is, if not controversial, then at least non-trivial.
\r
74 > > + Requests for the provision of message deletion mechanisms have
\r
75 > > appeared many times, and that various patches addressing the issue
\r
76 > > have been submitted, and (IIUC) some of these are awaiting review
\r
77 > > and might possibly make it into an official release in the future.
\r
79 > > + Having the 'deleted' tag cause messages to be deleted is,
\r
80 > > apparently, fraught with peril of losing mail.
\r
82 > Hi, Jacek. You are right on both of these points. It has indeed been a
\r
83 > controversial topic. However, I would say that we have reached a stasis
\r
84 > in terms of our response to this issue. I'll try to summarize here.
\r
86 > I can say with a very high degree of certainly that notmuch will NEVER
\r
87 > gain the capability to actually delete mail files from disk itself. It
\r
88 > is too risky for notmuch to be involved in that, and it's too easy to do
\r
89 > it outside of notmuch (e.g. "notmuch search --output=files tag:deleted |
\r
90 > xargs rm"). This has never really been up for discussion.
\r
92 To amend that (with mostly historical and not so helpful info), notmuch
\r
93 used to have the ability to sync the "deleted" tag with the T
\r
94 ("trashed") maildir flag (with maildir.synchronize_flags option
\r
95 set). Other mail clients or offlineimap were then able to delete the
\r
96 mails locally and/or on a server. However, this too had some issues
\r
97 (concerning multiple files with the same message-id) making it
\r
98 potentially dangerous, and was removed [1]. Whether this feature ever
\r
99 makes a comeback depends on someone tackling the problems. And taking
\r
100 into account the fact that current users of the deleted tag probably do
\r
101 not expect the files to be actually deleted.
\r
103 [1] http://git.notmuchmail.org/git/notmuch/commit/2c262042ac174d7bc96d6035ab9c88bd0abe7f35
\r
projects / notmuch-archives.git / blob