From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 314136DE0314 for ; Sat, 14 Sep 2019 10:34:04 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.056 X-Spam-Level: X-Spam-Status: No, score=-0.056 tagged_above=-999 required=5 tests=[AWL=-0.055, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BwgXrqOyAwz4 for ; Sat, 14 Sep 2019 10:34:03 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 2B5766DE02CB for ; Sat, 14 Sep 2019 10:34:02 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1i9Bvp-0005vG-F8; Sat, 14 Sep 2019 13:33:57 -0400 Received: (nullmailer pid 26220 invoked by uid 1000); Sat, 14 Sep 2019 17:33:56 -0000 From: David Bremner To: Jameson Graef Rollins , Daniel Kahn Gillmor , Notmuch Mail Subject: Re: v4 of repairing Mixed-up mangled MIME messages In-Reply-To: <87v9tu508a.fsf@caltech.edu> References: <20190909032726.8931-1-dkg@fifthhorseman.net> <87zhj749p7.fsf@caltech.edu> <87o8znyv2f.fsf@tethera.net> <87v9tu508a.fsf@caltech.edu> Date: Sat, 14 Sep 2019 14:33:56 -0300 Message-ID: <87d0g2zssb.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Sep 2019 17:34:04 -0000 Jameson Graef Rollins writes: > On Sat, Sep 14 2019, David Bremner wrote: >> Jameson Graef Rollins writes: >> >>> Can we have notmuch auto-apply a tag, like the "encrypted" and "signed" >>> tags, that indicates mail has been mangled in this way? I'm feeling >>> somewhat morally opposed to just silently fixing mail that's been broken >>> by bad/irresponsible actors on the net. We need to keep pushing on MS >>> to fix this issue globally, so I for one would like to be reminded if >>> I'm still being affected by this. >> >> It's side point, but it should rather be a property than a tag if we do >> something like that. In hindsight I think "auto tags" were probably a >> design mistake, since they are (easily) mutable by users. > > Right, sorry, yes it should be a property. I agree. > > Any reason not to move "encrypted" and "signed" to be properties as > well? I guess it would require some client code to be adapted. I'm not sure what really relies on those tags other than ad hoc searches. d