From: Carl Worth <cworth@cworth.org>
To: Alex Ghitza <aghitza@gmail.com>, Jed Brown <jed@59A2.org>,
	notmuch@notmuchmail.org
In-Reply-To: <54hbrmze3v.fsf@gmail.com>
References: <54hbrnpod1.fsf@gmail.com> <8763836xnv.fsf@59A2.org>
	<54hbrmze3v.fsf@gmail.com>
Date: Sat, 19 Dec 2009 18:37:12 -0800
Message-ID: <87aaxextev.fsf@yoom.home.cworth.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Subject: Re: [notmuch] keeping a copy of sent mail locally
Precedence: list

--=-=-=

On Sun, 20 Dec 2009 11:24:52 +1100, Alex Ghitza <aghitza@gmail.com> wrote:
> However, if I'm using notmuch in emacs and press 'm' to compose a new
> message, then the Bcc header is not added automatically and I guess it's
> not surprising that the rest doesn't work as expected.

Yeah, sorry about that. That's a known bug.

> So where is the difference between 'm' and 'r' coming from?

The difference is that 'r' actually runs the "notmuch reply" command and
that command explicitly puts your own address into the Bcc. So this is
happening outside of any emacs code.

When you hit 'm', though, there's not any notmuch code involved,
(neither C code, nor emacs lisp), as it's currently just running
`message-mail'. So we need to figure out how to configure (or hook) that
to insert the Bcc, and then we can fix notmuch.el to do this without any
user configuration.

> I have (setq mail-self-blind t)  in my .emacs, and I thought that should take
> care of things, but it obviously doesn't.

Ah, interesting.

I'm guessing that that variable would apply to the "mail" mode stuff in
emacs, but perhaps not the "message" mode stuff we're using.

Yes, emacs mail support is a huge pile of very similar, but incompatible
systems.

Hopefully someone can fix this soon, since I really don't like the fact
that I'm currently not getting copies of several messages that I'm
composing and sending.

-Carl

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFLLY3Y6JDdNq8qSWgRAhsSAJ0U8/teGOBgWDpcFQ0+xhFSly5s6wCeNYH1
lY5dXSFQZmEt0i2gtwAYl8Y=
=ung+
-----END PGP SIGNATURE-----
--=-=-=--