From: erik colson <eco@ecocode.net>
To: notmuch@notmuchmail.org
Subject: Re: moving mail to another maildir based on tags and renaming files
Date: Tue, 24 May 2022 11:45:02 +0200 [thread overview]
Message-ID: <875ylvs1r5.fsf@toolbox.mail-host-address-is-not-set> (raw)
In-Reply-To: <CK7VMK1DGF5M.2N5PP0T1B7IFR@bisio>
"inwit" <inwit@sindominio.net> writes:
> Yeah, that is correct. But it proved trickier than it seemed to me (thus the
> safeMove2 attempt).
Yes, I have seen that
> I must confess that I've holding this tag/folder scheme for over a year now, and
> that I'm more and more inclined to reduce the amount of folders that I keep
> (I've recently fused 3 or 4 of my biggest folders into Archive, for example).
> I'm trying to reduce my use of portable devices, and the truth is that search
> engines offered by webmail are slowly getting better, so I feel less exposed by
> not having my mail ranged in folders. I guess the whole tag-based paradigm is
> also settling down on my mind, although I still feel that its nowadays a bit odd
> to rely on a single local copy instead of a cloud-based solution. For this last
> problem, there have been some interesting developments recently that I need to
> investigate (precisely, the nmbug evolution).
I have 1000+ mailboxes linked to projects. Every project gets a number
and every 'subject' in the project gets its own subfolder. Take that
down 20+ years and you get 1000+ folders ;)
With notmuch my idea is to bundle the subfolders in the mainfolder so
that would roughly divide the mailboxes by at least 5. With notmuch the
subfolders are definitely to be tags. I want to keep the folder for
every project to at least have some kind of fallback in case the notmuch
database gets corrupt.. That is my most important fear with notmuch ;)
I was thinking if notmuch offers some kind of 'dump' for the database,
so it can eventually be restored ?
> Anyway, notmuch rocks. :)
quite a lot, in fact !
--
erik colson
next prev parent reply other threads:[~2022-05-24 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 21:02 moving mail to another maildir based on tags and renaming files erik colson
2022-05-23 21:19 ` inwit
2022-05-23 22:01 ` erik colson
2022-05-24 9:15 ` inwit
2022-05-24 9:45 ` erik colson [this message]
2022-05-24 12:26 ` David Bremner
2022-05-24 14:08 ` erik colson
2022-05-24 0:48 ` João Pedro
2022-05-24 8:49 ` erik colson
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=875ylvs1r5.fsf@toolbox.mail-host-address-is-not-set \
--to=eco@ecocode.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).