Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 08F4F4196F5 for ; Thu, 3 Jun 2010 17:02:23 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -2.89 X-Spam-Level: X-Spam-Status: No, score=-2.89 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, T_MIME_NO_TEXT=0.01] autolearn=ham Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IQdf3yimv9A2; Thu, 3 Jun 2010 17:02:11 -0700 (PDT) Received: from yoom.home.cworth.org (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 2D2FB431FC1; Thu, 3 Jun 2010 17:02:11 -0700 (PDT) Received: by yoom.home.cworth.org (Postfix, from userid 1000) id D00E5568F2D; Thu, 3 Jun 2010 17:02:10 -0700 (PDT) From: Carl Worth To: Jameson Rollins , Notmuch Mail list Subject: Re: [PATCH] Remove bcc header from notmuch reply. In-Reply-To: <87d3xjxnxd.fsf@servo.finestructure.net> References: <87r5pcad5v.fsf@servo.finestructure.net> <87d3xjxnxd.fsf@servo.finestructure.net> User-Agent: Notmuch/0.3.1-22-g1d528f8 (http://notmuchmail.org) Emacs/23.1.1 (i486-pc-linux-gnu) Date: Thu, 03 Jun 2010 17:02:10 -0700 Message-ID: <87aarbfywt.fsf@yoom.home.cworth.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 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: Fri, 04 Jun 2010 00:02:23 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable On Wed, 28 Apr 2010 17:33:18 -0400, Jameson Rollins wrote: > Notmuch reply should not be Bcc'ing the sender by default. This is > not the appropriate way to save copies of sent mail (which should > probably be handled by an Fcc header) and it doesn't give the user the > option to not be bcc'd. This is really something that should be > handled by the reader UI. For instance, emacs message-mode can easily > be configured to add Bcc's if the user wishes. > --- > Now that we finally have good built-in fcc support, we can finally get > rid of the annoying bcc in notmuch-reply. >=20 > This is a resubmit of an old patch that has been rebased against the > current head of cworth/master. I do want to apply this patch. But before I do I want the emacs interface to be doing *something* to ensure the user gets a copy of all sent messages by default. That could be a non-nil FCC value by default. Or if people think that's stepping on the user's mailstore namespace too much, it could be a Bcc option by default. Either way, I know that some users *do* want to use Bcc (or even Cc!) rather than Fcc. So I'd also like an emacs variable to select that too. =2DCarl --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFMCEKC6JDdNq8qSWgRAtvmAJ92WwdA7i4adGkJbhO4RKTrHyypOQCeMZ7+ Oyww6+1YSDUUblwqIeSP0/M= =R6qR -----END PGP SIGNATURE----- --=-=-=--