Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 012FC6DE0BF6 for ; Sun, 20 Dec 2015 13:26:23 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.562 X-Spam-Level: X-Spam-Status: No, score=-0.562 tagged_above=-999 required=5 tests=[AWL=-0.011, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, 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 JwxWWUz4Colc for ; Sun, 20 Dec 2015 13:26:21 -0800 (PST) Received: from mail-pa0-f66.google.com (mail-pa0-f66.google.com [209.85.220.66]) by arlo.cworth.org (Postfix) with ESMTPS id E9FD06DE0244 for ; Sun, 20 Dec 2015 13:26:20 -0800 (PST) Received: by mail-pa0-f66.google.com with SMTP id fl14so9968384pac.1 for ; Sun, 20 Dec 2015 13:26:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:in-reply-to:references:user-agent:date:message-id :mime-version:content-type; bh=uglWMRNvWqfrCK/QV/h3JOK4WU8A45wA3wYeVOQNozU=; b=z4VYIcnwTt+KlusHZY7IpG239FAeC42aIOaunIu74Sa283ucorYI3SKhDpMCkxgKiv hqoTePiFN7d5SXpOitbhXPXnT8mQJFPifUmEWWiBc+D/MkjqPl41rRagSakBG42ddGNc Ad7Xc/Nrd9PUeT0uNqXMPjVY1Ei88MzIkv6b35aQls1IqPgh5abXFehh6VheFfXnAssP B2N7sdAfy352G4sI6cBLEjbO/5cEs/9ZZxtIswpu/5+HFnvrQzyoNA7oCIUGihvuHAR2 TQFf9ushXJK3EllJnWh5Vm1Ztx8i+joUT/NTTmI3RHFZUShWiSKZxCBo4l82kBHOnTUl erFg== X-Received: by 10.66.102.97 with SMTP id fn1mr22322726pab.131.1450646779636; Sun, 20 Dec 2015 13:26:19 -0800 (PST) Received: from jinwoo-macbookair.roam.corp.google.com.gmail.com ([2601:647:4b02:71ea:4538:cef7:31d8:a56f]) by smtp.gmail.com with ESMTPSA id by2sm34654608pab.20.2015.12.20.13.26.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 20 Dec 2015 13:26:19 -0800 (PST) From: Jinwoo Lee To: Mark Walters , notmuch@notmuchmail.org Subject: Re: emacs: Wrong "From" address when forwarding a mail In-Reply-To: <8760zsyh5z.fsf@qmul.ac.uk> References: <8760zsyh5z.fsf@qmul.ac.uk> User-Agent: Notmuch/0.21+26~g8881a61 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-apple-darwin15.0.0) Date: Sun, 20 Dec 2015 13:26:17 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain 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: Sun, 20 Dec 2015 21:26:23 -0000 On Sun, Dec 20, 2015 at 12:54 PM, Mark Walters wrote: > You can get around some of this by setting > notmuch-always-prompt-for-sender to t (it is a customizable > variable). This means that whenever you create a new message or forward > a message you will be prompted to choose a sender address. I think forwarding should be more symmetric with replying than with sending a new message. Forwarding is an act of sending a mail you received at your account A to another person, and so the default account that it's sent from must be account A, not one of your other accounts. Isn't it really weird if a mail was "forwarded" from an account that never had received that mail? > Indeed, I am surprised you don't find it annoying that, when you start a > new personal email (e.g., with "m"), notmuch uses your corp address. I'm not surprised because it's a new mail and not associated with any of my accounts yet before I send it. Forwarding is different because it's already associated with one of the accounts and that one should be the default From address when forwarding. That's my expectation and I think it's intuitive. >> Can we make notmuch-show-forward-message behave like >> notmuch-show-reply-sender, which chooses the From address correctly? > > We could do this, but it's not clear to me that it is better than what > we have. Indeed, under your suggestion, suppose someone with their > personal address as their primary address received an idiotic email from > their boss, which they forward to their wife saying "what an > idiot". Suddenly, it is now being read by work... Agreed that this issue can happen in this case. Let's forget about the privacy issue. > Overall, I don't think is is possible for notmuch to get this right > enough of the time to make anything other than > notmuch-always-prompt-for-sender sensible in this sort of situation. > > Best wishes > > Mark