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 67D966DE01D0 for ; Thu, 2 Jun 2016 13:36:56 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.02 X-Spam-Level: X-Spam-Status: No, score=-0.02 tagged_above=-999 required=5 tests=[AWL=-0.020] 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 f7JhOxjx-uFk for ; Thu, 2 Jun 2016 13:36:48 -0700 (PDT) Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) by arlo.cworth.org (Postfix) with ESMTP id C30216DE00DB for ; Thu, 2 Jun 2016 13:36:47 -0700 (PDT) Received: from fifthhorseman.net (unknown [38.109.115.130]) by che.mayfirst.org (Postfix) with ESMTPSA id 6BFC1F98B; Thu, 2 Jun 2016 16:36:43 -0400 (EDT) Received: by fifthhorseman.net (Postfix, from userid 1000) id 34943201E6; Thu, 2 Jun 2016 16:36:43 -0400 (EDT) From: Daniel Kahn Gillmor To: Mark Walters , notmuch@notmuchmail.org Subject: Re: Emacs: postponing messages In-Reply-To: <87mvn330zr.fsf@qmul.ac.uk> References: <87mvn330zr.fsf@qmul.ac.uk> User-Agent: Notmuch/0.22+16~g87b7bd4 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Thu, 02 Jun 2016 16:36:39 -0400 Message-ID: <8760trqqeg.fsf@alice.fifthhorseman.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.20 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, 02 Jun 2016 20:36:56 -0000 --=-=-= Content-Type: text/plain On Thu 2016-06-02 14:21:44 -0400, Mark Walters wrote: > My broad idea for postpone is to take the partial message, use notmuch > insert to put it in the database with a "postponed" tag, and then on > resume fetch the raw message and go into notmuch-message-mode, and also > either add a deleted tag to the resumed message, or better actually > delete the resumed message. Finally, we would add postponed to the > excluded tags list, so that postponed messages only show up when > searched for. I'd love to see this happen. The terminology many other mail user agents use for this workflow is often "draft" or "drafts" so we might do well to adopt that term, instead of using "postpone", which i don't think is as widely-used. > An alternative would be to attach the attachments with the postponed > message. This is probably doable by writing the message (as if being > fcc'd) to notmuch insert, and then using the mime-to-mml function to > reverse the process. The downside here is that now the attached file is > not the current file in the filesystem when you send -- ie its different > from the normal case. I like this approach, and i don't think that the caveat you're describing is a particuarly bad one, though it depends on how mime-to-mml works. I just tested it, and mime-to-mml actually produced something that was not directly sendable in notmuch-message-mode, because it didn't include the "--text follows this line--" break between headers and body :/ But this is probably fixable ;) However, mime-to-mml actually embedded the content of the included sub-part upon reconstruction and the filename was only the leaf filename (i'd included /home/dkg/tmp/test.txt, and in the reconstructed #part it said filename="test.txt" nofile=yes) Since this doesn't include the original path of the file (and it said "nofile=yes"), then i don't think it's a problem. One thing i should note is that if there's a message-id assigned during saving of the draft, then we need to think carefully about how a draft that gets saved multiple times gets indexed. it'll have the same message-id, which is good, but there will likely be multiple files referencing it, each with different content. ideally, there would only be one copy indexed, and it would be the latest one. Also, the actually-sent mail should be indexed in preference over a previous draft. The above pieces would all be really great to have! In addition, if they were in place, it'd be good to have an variant notmuch-search view that lists the recipients instead of the senders, so that i can do a search for tag:draft and actually see who the messages were sent to, instead of my own name (as the sender) on each item :) --dkg --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJXUJjYXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFREIyRTc0RjU2RkNGMkI2NzI5N0I3MzUy NEVDRkY1QUZGNjgzNzBBAAoJECTs/1r/aDcKPjoQAJnoQA3FDsZ+GMDu7hbfh0gD QepjocxPX1ER1SEOUVgy7fFUE4chHbG/mKyKyVYF40DHMEJvri3GMyavw0fFvEA+ NHL2mrDZqDC2MbhlqZps13tvD3RVUPkhiaZjVavVXIEgoqQzQOA00pCbRrj7iRQ/ Aadkx5ra4RmeGKWqvNDsPEy4oZPR5Gig9nQEUrwdVD/YXkMjU849/tq4ZfqP9Qec RuL6YKDz9PgOIDGZb86ePrwcFq6ekHoeI6u/EPIG1ov7fIGchVWRlbatEOeF09Xq REyGDtsnGfW0axFUPsBbJVSPz+B2hQpRfqn53Di3+8j2+R/l/kCGrRsN8eKJQbKe sANY3KRpY1sq/GkhTRERgXQPD9MTeCZBeerIUrwIECbOfe6QFutN7yxlX54QO/kj k1zvMurLWW+b7E/MJ1jL96CUc0AVjFdMdz9Pjs2510+5PEgXJxRAHDTg++tw2U3S yzTj1rsREmkdf/78H38lDK1zhZcxtAYlCl4cNduGsAaB6tJG+rsPuJgtqUynDDtA fNClsCcXLUgGjBFIlNBA95G/PK40u/qKfrSCVyrFy87STtJvwxNX1FaYqMQ7YNiV gQHi0f9wE+kNjI5GoudsCmAmLc17iyMZG5d++XhskvSFk4xNqsPNYEKTpOs+FaTm SRcDSU4waEF3ayWV8geb =5ZYr -----END PGP SIGNATURE----- --=-=-=--