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 182FF431FBF for ; Sat, 22 Nov 2014 01:45:00 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] 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 No2jbkhh0eLB for ; Sat, 22 Nov 2014 01:44:55 -0800 (PST) Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id C2D07431FBC for ; Sat, 22 Nov 2014 01:44:55 -0800 (PST) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1Xs7FK-0007VH-WB; Sat, 22 Nov 2014 05:44:51 -0400 Received: (nullmailer pid 3881 invoked by uid 1000); Sat, 22 Nov 2014 09:44:45 -0000 From: David Bremner To: Edward Betts , notmuch@notmuchmail.org Subject: Re: exim pipe transport, notmuch insert and mbox-style messages In-Reply-To: <20141122092851.GA31815@x230> References: <20141122092851.GA31815@x230> User-Agent: Notmuch/0.19+2~g32855b9 (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Sat, 22 Nov 2014 10:44:45 +0100 Message-ID: <87tx1r7enm.fsf@maritornes.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain 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, 22 Nov 2014 09:45:00 -0000 Edward Betts writes: > I wonder if 'notmuch insert' could be modified to detect and drop the From_ > line before writing the message to disk and index it. It could do that > silently or with a warning. I don't know about the larger question(s), but I'd suggest just escaping it to something like X-Envelope-From: . There may even be some semi-standard header to use for this. d