From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id 2Ff6BxpHmWCO9wAAgWs5BA (envelope-from ) for ; Mon, 10 May 2021 16:45:46 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id QyK9AxpHmWA1UQAA1q6Kng (envelope-from ) for ; Mon, 10 May 2021 14:45:46 +0000 Received: from mail.notmuchmail.org (nmbug.tethera.net [IPv6:2607:5300:201:3100::1657]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 847F01E21E for ; Mon, 10 May 2021 16:45:45 +0200 (CEST) Received: from nmbug.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id 6298627185; Mon, 10 May 2021 10:45:40 -0400 (EDT) Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) by mail.notmuchmail.org (Postfix) with ESMTPS id 8EDD926874 for ; Mon, 10 May 2021 10:45:37 -0400 (EDT) Received: by mail-io1-xd31.google.com with SMTP id d24so5130401ios.2 for ; Mon, 10 May 2021 07:45:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+qpHIxpAzka3oufDPoGgMrpYH/biqvf8JuD5oQLGlL8=; b=o/AKb9GS7g2OLWCZ9Or7inW3mgSiKUSVhwqqyuEVhVElsNzlnUKLkC1qRJVkH2Sl+d dEcP2bYhzTSJDcYNGWGQSRppHiZkospIiGRcXsLEN1hh/mwPLYkDMJMrCRYKV4OkXdod MhSx5bW3uNyBzxGZzTHl2x2fZU9bqUAJ9R4WYIqjhkvaRKvDnOKu71yhd2jFZYeTHSfC shR6SP5Leymp36ZOiMz76q7YOqabG75/SXchPpQXCachribu5FgKGU16V2v7Va7H+ulB AnkrGw13Da0zHuI5bPbX9asoBKfW2i8QS3iab7EQVePXDaNxIC1Um7oZxxxl3KFHmRPg jfEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+qpHIxpAzka3oufDPoGgMrpYH/biqvf8JuD5oQLGlL8=; b=dZFd3wZKAcXReSi8lzldIJCIllxJD+gM3W0sJc52WJFw32v5oHu3i7Af0wD+R58BMr rJUtr3A2/PbwuY53IA66s5O1dc8mjm//cQ4YNE989vDWA6mdB1LDEjoY3wL54AhySFPw 21JhZ/5miwDHIlCy+ZefJk+7c+PlOcNa0Wez8tu5+HARrAZAESR1lBncqOvpB9N0VGT3 Dc+Y6zKS3afOoS/dIbHAhdo0ym7zBMQszAWCWwovipn6owa5qRuqhC5l8jMAYAp8g+MW 6UeLsJugAV83Pnei5uvhevGkJouCcdI2OpHJ/p2pBHmSMxcCsttQ9nPzu5a4RK1eLhKV SycA== X-Gm-Message-State: AOAM533s8gaE/WsQWhliWZT8IoILrK25ifeV0ZpR4hPBqymD1yIWmyZB eBNzeFEsI2/H9UUcwXYMnCcyKy4Xx6f21E8xzdE= X-Google-Smtp-Source: ABdhPJyKe6srtOLsLwD7d1XigC7MIyshPu6D/fPwtFG43Svp1g7azeLngVJDctkWcrfWVzQx7lwxI93sWszLFQa/s4s= X-Received: by 2002:a05:6638:3013:: with SMTP id r19mr22354203jak.36.1620657933454; Mon, 10 May 2021 07:45:33 -0700 (PDT) MIME-Version: 1.0 References: <60971dc77decb_22cb620817@natae.notmuch> <87bl9kjlgo.fsf@tethera.net> <8735uukd6c.fsf@tethera.net> <162065351282.5824.14225420932746058853.git@grubix.eu> In-Reply-To: <162065351282.5824.14225420932746058853.git@grubix.eu> From: omgitsaheadcrab Date: Mon, 10 May 2021 15:45:23 +0100 Message-ID: Subject: Re: Is there a reason why the trashed flag is not synced? To: Michael J Gruber Message-ID-Hash: 243XZQSFOEMCPGYE5NVWQSFABHQRH2RL X-Message-ID-Hash: 243XZQSFOEMCPGYE5NVWQSFABHQRH2RL X-MailFrom: omgitsaheadcrab@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-notmuch.notmuchmail.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header CC: notmuch@notmuchmail.org X-Mailman-Version: 3.2.1 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Help: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: multipart/mixed; boundary="===============8016762750213867578==" X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1620657945; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=R6lUDJQUicXqWZsg8H+3On5AG/P7KKCRaWzfMoHSJ44=; b=SlPAv8vbPtqArlvxwLykuI/OxEbPq3vflnVhMdoetRutISHBAaWcvsDQijHJGO7VHwAckd gR2dLxOrgdppfJHLOuGRJKoZI53OwfOdKw61WduRnNrmS+YYztVGbLRfoySNApIMooH4nU sHNNQQzvJ7Ll358ZX7jD7Bj18NvEFBqG3P5Vzj03Bi25riNrS9UuQ4E4YAw1/j2KM9Yq0J /nhSZmGnMsA9Y48tQexouYJdXvN+/42UXI5VWVMuRvgq+ldHdjJ9R9jR59m5BBgaxOqkFG tcnPFajLYgjEH0I/IHgwfDUhAl7k+9z+zudNXCymZjaJvsvOJ2EUQ7tjMrcBBg== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1620657945; a=rsa-sha256; cv=none; b=o4C9xlEJlf5dWHDKmZiaodvPafItcsgoRKJt0l9QRG54A+6D0JNO4m35TM9qAh3j6L9tsw vg4WcL/w5WV5bZ7QFGAzVoMkGjc3E/SyGjlA+eXAirnLUDTxtSKRVI7igGWIDZPMkLGdzE 0DppHZBJL7hWsjN2vd+1EHKLOlO6M7446CliNPa+Dp1bGSsXcyWDsckQE5mj+xhpewKgMe Dc0Emeh6ZyubeyICsQZpNTv/C4IHoyJO2cXD+rghAf3oxEDefxW+8W0IIxYWp+3mpqOP9r zCCTMWgWl6vmwPdn0yam29vwaUpj81jg1ZYl64Wy9TPyIpRN0a3wGWANAitdRg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=gmail.com header.s=20161025 header.b="o/AKb9GS"; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 2607:5300:201:3100::1657 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Migadu-Spam-Score: 1.05 Authentication-Results: aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=gmail.com header.s=20161025 header.b="o/AKb9GS"; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 2607:5300:201:3100::1657 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Migadu-Queue-Id: 847F01E21E X-Spam-Score: 1.05 X-Migadu-Scanner: scn0.migadu.com X-TUID: 9+pEvettCDDk --===============8016762750213867578== Content-Type: multipart/alternative; boundary="0000000000006d137605c1fad4ec" --0000000000006d137605c1fad4ec Content-Type: text/plain; charset="UTF-8" My use is similar to Michael's. That being said, I think giving users the option, assuming they are aware of the risks, is a good idea. I do however think that this should be a separate flag as I dislike extra options being bolted on to booleans. On Mon, May 10, 2021 at 2:32 PM Michael J Gruber wrote: > David Bremner venit, vidit, dixit 2021-05-10 14:04:27: > > Felipe Contreras writes: > > > > > > > > It makes sense that by default synchronize_flags=true doesn't sync the > > > trash flag, but what's wrong with a new configuration > > > synchronize_flags=all that does? > > > > > > > That seems plausible to me, but I'd like more input in case I missed > > something. > > What happens if you have multiple copies of the same message, some "unseen" > or "replied" etc.? notmuch synchronizes them with the flag on the > message and in turn with all message copies, and this works "as > expected" because, for example, there is no "unseen" flag but a "seen" > flag. > > Well, partially. What happens if you mark a message unread (clear the > "seen" flag) in one account? Notmuch will see a changed message file for > one copy - will it reread all files for this mid and reconstruct the > flags (thereby overwriting the unseen with the seen from the other one)? > (Honest question, I don't know.) > > 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)? I'd even argue for the latter, at least for supporting > "maildir.synchronize_deleted" in both directions. To be super-safe, one > could special case this to take an AND of all message delete flags: > "unread" already acts as if it was an AND of the unread flags of all > copies (because it's the negation of an OR of seen flags). > > A one-sync, however, can be confusing, I'm afraid. > > Personally, I use trash folders synced with flags (through mbsync+afew, > gmailieer) togther with the typical 30day clean-up. Has worked well so > far. > > Cheers > Michael > _______________________________________________ > notmuch mailing list -- notmuch@notmuchmail.org > To unsubscribe send an email to notmuch-leave@notmuchmail.org > --0000000000006d137605c1fad4ec Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
My use is similar to Michael's.

Tha= t being said, I think giving users the option, assuming they are aware of t= he risks,
is a good idea.

I do however think that this should be = a separate flag as I dislike
extra options being bolted on to booleans.<= /div>

On Mon, May 10, 2021 at 2:32 PM Michael J Gruber <git@grubix.eu> wrote:
David Bremner venit, vidit, dixit 2021-05-10 1= 4:04:27:
> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
> >
> > It makes sense that by default synchronize_flags=3Dtrue doesn'= ;t sync the
> > trash flag, but what's wrong with a new configuration
> > synchronize_flags=3Dall that does?
> >
>
> That seems plausible to me, but I'd like more input in case I miss= ed
> something.

What happens if you have multiple copies of the same message, some "un= seen"
or "replied" etc.? notmuch synchronizes them with the flag on the=
message and in turn with all message copies, and this works "as
expected" because, for example, there is no "unseen" flag bu= t a "seen"
flag.

Well, partially. What happens if you mark a message unread (clear the
"seen" flag) in one account? Notmuch will see a changed message f= ile for
one copy - will it reread all files for this mid and reconstruct the
flags (thereby overwriting the unseen with the seen from the other one)? (Honest question, I don't know.)

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)? I'd even argue for the latter, at least for supporting
"maildir.synchronize_deleted" in both directions. To be super-saf= e, one
could special case this to take an AND of all message delete flags:
"unread" already acts as if it was an AND of the unread flags of = all
copies (because it's the negation of an OR of seen flags).

A one-sync, however, can be confusing, I'm afraid.

Personally, I use trash folders synced with flags (through mbsync+afew,
gmailieer) togther with the typical 30day clean-up. Has worked well so
far.

Cheers
Michael
_______________________________________________
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-leave@notmuchmail.org
--0000000000006d137605c1fad4ec-- --===============8016762750213867578== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============8016762750213867578==--