From: David Bremner <david@tethera.net>
To: Jorge <jorge+list@disroot.org>, notmuch@notmuchmail.org
Subject: Re: Notmuch tags when OfflineIMAP creates a new folder with the same messages
Date: Tue, 27 Nov 2018 16:01:59 -0400 [thread overview]
Message-ID: <875zwinvbc.fsf@tethera.net> (raw)
In-Reply-To: <02f6dc712139021c08a8237b16bab3f6@disroot.org>
"Jorge" <jorge+list@disroot.org> writes:
> Hi. I work at Dataprev (a Brazilian state-owned federal IT company),
> and here we use an email implementation called Expresso 3.0. I access
> it via OfflineIMAP 7.2.1 on Debian buster. Recently I have gained
> access to a shared folder hierarchy called "demandas.dica" (with Drafts,
> Sent and Trash subfolders). OfflineIMAP could not handle it because its
> name contains a "." which is the default sep character.
>
> On the OfflineIMAP mailing list, Nicolas Sebrecht recommended I choose
> another sep character. I would choose '+', but I have not yet
> configured it. What is holding me back is the fear that, when I set
> sep = "+", OfflineIMAP will create a new 'INBOX+Sent' folder in place of
> the current 'INBOX.Sent' and ditto for lots of other folders. Nicolas
> confirmed this is how OfflineIMAP will behave.
>
> So my last doubt is, will Notmuch recognize that the emails are the
> same, and keep my tags? Then after Notmuch indexes the "new" (renamed
> copies) folders, can I delete the original folders?
I _think_ it should be OK. Notmuch
1) Tracks file renames
2) Attaches tags to message-ids, not to files.
As a precaution, it is always worthwhile to have a "notmuch dump" and or
full backup before attempting anything drastic.
d
next prev parent reply other threads:[~2018-11-27 20:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 13:16 Notmuch tags when OfflineIMAP creates a new folder with the same messages Jorge
2018-11-27 20:01 ` David Bremner [this message]
2018-12-08 17:17 ` Jorge P. de Morais Neto
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=875zwinvbc.fsf@tethera.net \
--to=david@tethera.net \
--cc=jorge+list@disroot.org \
--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).