From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id QjVoK+0immDCSgEAgWs5BA (envelope-from ) for ; Tue, 11 May 2021 08:23:41 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id yM55Ju0immBfWwAAbx9fmQ (envelope-from ) for ; Tue, 11 May 2021 06:23:41 +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 658C32053D for ; Tue, 11 May 2021 08:23:41 +0200 (CEST) Received: from nmbug.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id D6C8C27180; Tue, 11 May 2021 02:23:31 -0400 (EDT) Received: from mariecurie.labrat.space (mariecurie.labrat.space [116.203.185.229]) by mail.notmuchmail.org (Postfix) with ESMTPS id B882827176 for ; Tue, 11 May 2021 02:23:28 -0400 (EDT) Received: from labrat.space (adsl-178-38-36-59.adslplus.ch [178.38.36.59]) by mariecurie.labrat.space (Postfix) with ESMTPSA id 91D921F22B71; Tue, 11 May 2021 08:22:19 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=labrat.space; s=201904; t=1620714139; bh=XlRQOVw3hDBHMzo8Vm1VAAWgQz/7AWoWBx/W4/X54d0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To:From:To:CC:Date: Subject:Content-Type:Content-Disposition:Reply-To:In-Reply-To: MIME-Version:Message-ID:References; b=ZR77z8CLTVCjEMrlIaEC9buuXKIQd+PpaG9H3VCD0xMg3bUOgd+eIF9vLhosAj+5o gHMH4gdSLW6mASRdFIEIZtPlPddw1DAORWAJwUpAahBS7mx+f6h10up9zpv3boQ57B 9QFM3BPPk3wxrR7NXRh2PqsPfOi0z37mXBtUacngI72GzqQkwIznOn9WhLJS/16ow5 GIpsfGN1QikuFEZ6DPYNvzLbu+0E90toinIBb2y38FDvxAYw/QIntBuVRg6nr2NWK2 RHmtiOKc6dBPKrATx89l4C3qoUb+c3uZC99x9HtVHGEVS/f5dkXsMx39aB3d8MJby9 Df88bpAHljaZw== Date: Tue, 11 May 2021 08:23:21 +0200 From: Reto To: Michael J Gruber Subject: Re: Is there a reason why the trashed flag is not synced? Message-ID: <20210511062321.7rp3g64qfopaxedj@feather> Mail-Followup-To: Michael J Gruber , David Bremner , Felipe Contreras , notmuch@notmuchmail.org References: <60971dc77decb_22cb620817@natae.notmuch> <87bl9kjlgo.fsf@tethera.net> <8735uukd6c.fsf@tethera.net> <162065351282.5824.14225420932746058853.git@grubix.eu> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <162065351282.5824.14225420932746058853.git@grubix.eu> Message-ID-Hash: F2VL3L23CVGNGMURYV3IR52T3EQUTXTG X-Message-ID-Hash: F2VL3L23CVGNGMURYV3IR52T3EQUTXTG X-MailFrom: reto@labrat.space 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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1620714221; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=yJGq/VpQ6+bD5ccLn0VhH7sa8Q24eYoDK/UNdqMRiEM=; b=tt0zceGMw7GS23q9Gz8xzcwb7qMuHghGDSMWkbUyQAeAAwrY66nK6DqnfBW0r7QMbv77kk iuPFJuMe6OkEmpl/MWzMmj7QtZVH5nzs0mD4uCg+S7f3MKQodCEIZHKKE/WgOHJ0tY/gOY Oyudyjjup0QE714xbXp2NJUcZmpA0J43ibI1CpJ8ajrGZXAJiUqrmzzJWDcvq9sWH6X4Jt bNJszFXaM6FXKM/ImqbBFjZ2ZFMd5r0pJW6ZSvQGMIcf+YeWu6WKbkPVHIKNlUAHzaQ760 DRhAiZDTUcBhlaJ5g02oEPXD6cGLPl3+1huxBSI7ZeehkfxYiAbB8Mngg9mSHQ== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1620714221; a=rsa-sha256; cv=none; b=BY6Z8dEdROYmEU7PRouq+9BTeDOuDrtMUtJpLkPcb+9VHK5ENJ2btYeSRobPuW7TG1o3WO ykpPuJKtuHSlmqcU7wQ3aLbIcVAlqVpGAnDXMlERuMyFvbAjRlQkHq8+uGOFZAV+qL5VTJ ydAqruQ2SN4yptuuIQaqMpBtP/MccORgJ43TbeqcMMCJgU76DNRHvP+b4glpFa+8xtQkEd oHjV8/VZWQ6qFiaRDsy4I7WfP41oC+9rImCdZsPmt6QniRVK5A8sB1Vt9/XDn0b0pkeYwh q5YhOGC6JzxKME6WlTt0s0wNwew7w9TL5yYr8xkKM+i1/84VLSnEFk1KtG9pnA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=labrat.space header.s=201904 header.b=ZR77z8CL; dmarc=fail reason="SPF not aligned (strict)" header.from=labrat.space (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: 2.06 Authentication-Results: aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=labrat.space header.s=201904 header.b=ZR77z8CL; dmarc=fail reason="SPF not aligned (strict)" header.from=labrat.space (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: 658C32053D X-Spam-Score: 2.06 X-Migadu-Scanner: scn0.migadu.com X-TUID: 55Dx+fwVpYy7 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.