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 80986431FB6 for ; Wed, 6 Apr 2011 12:23:28 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -2.3 X-Spam-Level: X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3] 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 w4s-vn6qeE58 for ; Wed, 6 Apr 2011 12:23:26 -0700 (PDT) Received: from mail4.ucc.ie (mail4.ucc.ie [143.239.1.34]) by olra.theworths.org (Postfix) with ESMTP id 4AEE9431FB5 for ; Wed, 6 Apr 2011 12:23:26 -0700 (PDT) Received: from msstf091.ucc.ie (msstf091.ucc.ie [143.239.76.91]) by mail4.ucc.ie (8.13.8/8.13.8) with ESMTP id p36JNIkM005943 for ; Wed, 6 Apr 2011 20:23:23 +0100 Received: by msstf091.ucc.ie (Postfix, from userid 1000) id E6A8E62B22; Wed, 6 Apr 2011 20:23:17 +0100 (IST) From: Andreas Amann To: Notmuch Mail Subject: Problem with "Unexpected output" messages User-Agent: Notmuch/0.5-80-g8a534dc (http://notmuchmail.org) Emacs/24.0.50.1 (x86_64-unknown-linux-gnu) Date: Wed, 06 Apr 2011 20:23:17 +0100 Message-ID: <87pqozi3q2.fsf@msstf091.ucc.ie> MIME-Version: 1.0 Content-Type: text/plain X-MD-NoSA: yes X-Scanned-By: MIMEDefang 2.68 on 143.239.1.34 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: Wed, 06 Apr 2011 19:23:28 -0000 since commit 44d3c57e (emacs: Display any unexpected output from notmuch search) I see a number of messages of the form Error: Unexpected output from notmuch search: thread:000000000000XXXX after notmuch-search in emacs. The problem seems to be that some messages contain a "CR LF" sequence in the "Subject:" line which is either QP or base64 encoded. Apparently the emacs part of notmuch does not expect such a newline in the subject and cannot parse the output of "notmuch search". I am happy to forward one of the offending messages at request. This problem occurs with the git master branch as well as with the crypto branch. Is there any way around this? Andreas