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 6ED426DE0355 for ; Wed, 21 Sep 2016 17:22:38 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.007 X-Spam-Level: X-Spam-Status: No, score=-0.007 tagged_above=-999 required=5 tests=[AWL=0.004, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 9NlXEfdakm2e for ; Wed, 21 Sep 2016 17:22:37 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 004636DE0319 for ; Wed, 21 Sep 2016 17:22:36 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1bmrmQ-0001b6-E5; Wed, 21 Sep 2016 20:22:22 -0400 Received: (nullmailer pid 3716 invoked by uid 1000); Thu, 22 Sep 2016 00:22:28 -0000 From: David Bremner To: Daniel Kahn Gillmor , Mark Walters , notmuch@notmuchmail.org Subject: Re: [PATCH 2/2] emacs: postpone/resume support In-Reply-To: <87oa3iuzi2.fsf@alice.fifthhorseman.net> References: <1473004582-19396-1-git-send-email-markwalters1009@gmail.com> <1473004582-19396-3-git-send-email-markwalters1009@gmail.com> <87d1kazlof.fsf@zancas.localnet> <87oa3iuzi2.fsf@alice.fifthhorseman.net> Date: Wed, 21 Sep 2016 21:22:28 -0300 Message-ID: <87fuoseqbf.fsf@zancas.localnet> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.22 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: Thu, 22 Sep 2016 00:22:38 -0000 Daniel Kahn Gillmor writes: > > So this failure that bremner's reporting appears to happen only when > combining the #secure mode with a message with attachments. It doesn't > happen when the draft itself is just plaintext and one of the #secure > flags is set. And there's no problem if there are attachments without > the #secure flag. > > Bremner, can you confirm this? Yes, that sounds about right. Although the emacs bug I reported does not have to do with attachments per se, just the requirement that the #secure tag is at the top of the message > > I also noticed that if you rearrange the text before sending so that the > #secure flag is at the top of the message, the structure of the message > looks weird -- in particular, there's a double layer of multipart/mixed > just within the crypto transformation, instead of a single layer. > > that said, these patches are really useful to me even in their current > form, since most of my draft messages don't deal with both crypto and > attachments. Is there some way to get the benefits here without the bug > at the intersection? We could (and I think emacs should) abort if it detects #secure anywhere but on the first line. d