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 5A5336DE178F for ; Fri, 15 Jan 2016 11:26:05 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.024 X-Spam-Level: X-Spam-Status: No, score=-0.024 tagged_above=-999 required=5 tests=[AWL=-0.024] 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 dD6FxVVquXKn for ; Fri, 15 Jan 2016 11:26:03 -0800 (PST) Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108]) by arlo.cworth.org (Postfix) with ESMTP id A48BF6DE0A87 for ; Fri, 15 Jan 2016 11:26:03 -0800 (PST) Received: from fifthhorseman.net (unknown [38.109.115.130]) by che.mayfirst.org (Postfix) with ESMTPSA id 47067F984 for ; Fri, 15 Jan 2016 14:26:01 -0500 (EST) Received: by fifthhorseman.net (Postfix, from userid 1000) id 1250320000; Fri, 15 Jan 2016 11:26:01 -0800 (PST) From: Daniel Kahn Gillmor To: notmuch@notmuchmail.org Subject: Re: Bug report: undeletable traces of ghosts in the notmuch database In-Reply-To: <87twmf7t8k.fsf@alice.fifthhorseman.net> References: <87twmf7t8k.fsf@alice.fifthhorseman.net> User-Agent: Notmuch/0.21+66~g8c19a9a (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Fri, 15 Jan 2016 14:26:01 -0500 Message-ID: <87y4bq63w6.fsf@alice.fifthhorseman.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" 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: Fri, 15 Jan 2016 19:26:05 -0000 --=-=-= Content-Type: text/plain On Thu 2016-01-14 16:20:59 -0500, Daniel Kahn Gillmor wrote: > This suggests that if i include a bogus message-id in my References: > list for any mail i send to a notmuch user, then access to their > database will let me tell whether they ever saw it or not, regardless of > whether they deleted the message. The script below demonstrates the problem. before the message is added and removed, delve -a shows: ---------------------- All terms in database: ---------------------- but afterward, it shows: ---------------------- All terms in database: G0000000000000001 Qno-such-message@example.org Tghost XDDIRENTRY2:new XDIRECTORY XDIRECTORYnew ---------------------- --dkg --=-=-= Content-Type: text/x-sh Content-Disposition: inline; filename=demonstrate-ghost-leak #!/bin/bash -x workdir="$(mktemp -d)" export NOTMUCH_CONFIG="${workdir}/.notmuch-config" mkdir -p "${workdir}"/messages/{cur,tmp,new} cat >$NOTMUCH_CONFIG <"${workdir}"/messages/new/test-message.eml < Message-ID: <12345@example.org> Content-Type: text/plain This is a test message EOF notmuch new delve -a $workdir/messages/.notmuch/xapian rm -f "${workdir}"/messages/new/test-message.eml notmuch new delve -a $workdir/messages/.notmuch/xapian --=-=-=--