From: Jani Nikula <jani@nikula.org>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
Jacek Generowicz <jacek.generowicz@cern.ch>,
notmuch@notmuchmail.org
Subject: Re: Message deletion wisdom
Date: Wed, 04 Apr 2012 07:38:37 +0000 [thread overview]
Message-ID: <87mx6sx7ya.fsf@nikula.org> (raw)
In-Reply-To: <87sjgk2xzf.fsf@servo.finestructure.net>
On Tue, 03 Apr 2012 16:32:04 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
> On Tue, Apr 03 2012, Jacek Generowicz <jacek.generowicz@cern.ch> wrote:
> > Looking through the archives of this list, I see that the topic of
> > message deletion is, if not controversial, then at least non-trivial.
> >
> > + Requests for the provision of message deletion mechanisms have
> > appeared many times, and that various patches addressing the issue
> > have been submitted, and (IIUC) some of these are awaiting review
> > and might possibly make it into an official release in the future.
> >
> > + Having the 'deleted' tag cause messages to be deleted is,
> > apparently, fraught with peril of losing mail.
>
> Hi, Jacek. You are right on both of these points. It has indeed been a
> controversial topic. However, I would say that we have reached a stasis
> in terms of our response to this issue. I'll try to summarize here.
>
> I can say with a very high degree of certainly that notmuch will NEVER
> gain the capability to actually delete mail files from disk itself. It
> is too risky for notmuch to be involved in that, and it's too easy to do
> it outside of notmuch (e.g. "notmuch search --output=files tag:deleted |
> xargs rm"). This has never really been up for discussion.
To amend that (with mostly historical and not so helpful info), notmuch
used to have the ability to sync the "deleted" tag with the T
("trashed") maildir flag (with maildir.synchronize_flags option
set). Other mail clients or offlineimap were then able to delete the
mails locally and/or on a server. However, this too had some issues
(concerning multiple files with the same message-id) making it
potentially dangerous, and was removed [1]. Whether this feature ever
makes a comeback depends on someone tackling the problems. And taking
into account the fact that current users of the deleted tag probably do
not expect the files to be actually deleted.
[1] http://git.notmuchmail.org/git/notmuch/commit/2c262042ac174d7bc96d6035ab9c88bd0abe7f35
BR,
Jani.
next prev parent reply other threads:[~2012-04-04 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 10:37 Message deletion wisdom Jacek Generowicz
2012-04-03 23:32 ` Jameson Graef Rollins
2012-04-04 7:38 ` Jani Nikula [this message]
2012-04-05 16:24 ` Antoine Beaupré
2012-04-05 16:20 ` Antoine Beaupré
2012-04-06 20:17 ` Mark Anderson
2012-04-09 21:36 ` green
2012-04-08 22:24 ` Sebastian Spaeth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mx6sx7ya.fsf@nikula.org \
--to=jani@nikula.org \
--cc=jacek.generowicz@cern.ch \
--cc=jrollins@finestructure.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).