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 94516431FAF for ; Sat, 24 Mar 2012 05:17:17 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled 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 8m8vinr9cRh6 for ; Sat, 24 Mar 2012 05:17:17 -0700 (PDT) Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com [209.85.217.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id C6C25431FAE for ; Sat, 24 Mar 2012 05:17:16 -0700 (PDT) Received: by lbok6 with SMTP id k6so3274693lbo.26 for ; Sat, 24 Mar 2012 05:17:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:to:cc:subject:in-reply-to:references:user-agent:date :message-id:mime-version:content-type:x-gm-message-state; bh=6wf6v08DlsJ48vNdGX/fDWMztYUNAkQPfJiOb9ebwOE=; b=lYzv5PyUTwQqtSUWSouiQlw42UGqJGRQjwPyADDHx6yN8dlEGJehnPdrrWxDX6aHkH 2H9E5Owe2cfrJ3OSpaxN7GTVe3mv6irIHjDUTXTA96Z21qOWzWqPohKtAUzkKyEGdPUK rfjMYJk95D+X7BrREyC4W3qRtSZJJkTd4s7x5Ol8SjbPeVnIDDW7NYhKOshzY+CQL1nf pAAfVmvgTtqbIs1qj/4he/zDXuYfzR6P+kM1ULqc+vRJ6R8cwm+9BHKGSsnVnRBZovkT ueiMsHSAolvqia6/oYHgrcVOBoIxZMelBdeKvAdUsoh5vGFGY68IK3X8aUYacF0jEqeE e1Xg== Received: by 10.152.103.12 with SMTP id fs12mr11050256lab.47.1332591435219; Sat, 24 Mar 2012 05:17:15 -0700 (PDT) Received: from localhost (dsl-hkibrasgw4-fe50f800-253.dhcp.inet.fi. [84.248.80.253]) by mx.google.com with ESMTPS id a8sm13883224lba.15.2012.03.24.05.17.12 (version=SSLv3 cipher=OTHER); Sat, 24 Mar 2012 05:17:13 -0700 (PDT) From: Jani Nikula To: Patrick Totzke , Austin Clements , Kyle Sexton Subject: Re: Questions from a user new to notmuch In-Reply-To: <20120324100448.2696.11042@brick.lan> References: <20120322223907.GO2670@mit.edu> <20120324100448.2696.11042@brick.lan> User-Agent: Notmuch/0.11.1+295~g780f284 (http://notmuchmail.org) Emacs/23.3.1 (i686-pc-linux-gnu) Date: Sat, 24 Mar 2012 14:17:10 +0200 Message-ID: <878viqqjll.fsf@nikula.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Gm-Message-State: ALoCoQnxmHBZrqLZzjqLP4MW67XopFEHMrwLbm2P25clXqCf3crtkAzh3/LYtTTKkMfnwN57KBJE Cc: notmuch@notmuchmail.org 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: Sat, 24 Mar 2012 12:17:17 -0000 On Sat, 24 Mar 2012 10:04:48 +0000, Patrick Totzke wrote: > Quoting Austin Clements (2012-03-22 22:39:07) > >> 2. I received a message that was addressed to a distribution group and > >> tried to reply. Because the TO: address is not my address, notmuch > >> fails to guess the proper FROM: address to set. Is there a way to > >> handle this use case? This is with the emacs notmuch client. > > > >Not in general, since notmuch doesn't know where the mail was > >addressed to. I believe some people have solved problems like this > >using Emacs hooks, but I don't know the details. > > Does the notmuch CLI not use the 'Delivered-To' header for this? To decide which from address to use for replying, the CLI (and therefore emacs ui) looks for primary and other email addresses in the reply-to/from, to, cc, bcc, envelope-to, x-original-to, and finally received headers, in this order, before falling back to just using primary email. If someone is interested (read: I'm too busy right now), and it's desirable, it would be a one-liner to add delivered-to in the to_headers array in guess_from_received_header() in notmuch-reply.c. Plus a few dozen lines of test code. ;) BR, Jani.