unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Reto <reto@labrat.space>
To: Michael J Gruber <git@grubix.eu>
Cc: notmuch@notmuchmail.org
Subject: Re: Is there a reason why the trashed flag is not synced?
Date: Tue, 11 May 2021 08:23:21 +0200	[thread overview]
Message-ID: <20210511062321.7rp3g64qfopaxedj@feather> (raw)
In-Reply-To: <162065351282.5824.14225420932746058853.git@grubix.eu>

On Mon, May 10, 2021 at 03:31:52PM +0200, Michael J Gruber wrote:
> Deleting by chance is more harmful, yes. But is it more typical to clear
> out duplicate files using "T" or to delete a message (i.e. all it's file
> copies)?

You have to be a bit careful here... imap is a relatively strange protocol.
Consider a provider like gmail that uses a label system over normal imap folders.
If you assign a message "inbox" and "vacation" and maybe "archive" and then want
to remove the message from inbox and vacation folders you execute delete instructions.
That however, certainly shouldn't propagate to the "archive" copy.

So I'd argue that in fact no, what you mention is not the "typical" thing to do.
At least not with those providers.
Not all MUAs behave the same in regards to whether or not they set the trash flag
first.
Yes, you can tell neomutt to do almost anything, but if setting the Trash flag
on one message starts deleting all other copies I'd be very much surprised.

  parent reply	other threads:[~2021-05-11  6:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-08 23:24 Is there a reason why the trashed flag is not synced? Felipe Contreras
2021-05-09  9:38 ` David Bremner
2021-05-09 20:43   ` Felipe Contreras
2021-05-10 12:04     ` David Bremner
2021-05-10 13:31       ` Michael J Gruber
2021-05-10 14:45         ` omgitsaheadcrab
2021-05-11  6:23         ` Reto [this message]
2021-05-11  6:48           ` Michael J Gruber
2021-05-12  5:10             ` Reto
2021-05-12  8:37               ` Michael J Gruber
2021-05-12 19:52                 ` Felipe Contreras

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=20210511062321.7rp3g64qfopaxedj@feather \
    --to=reto@labrat.space \
    --cc=git@grubix.eu \
    --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).