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 68142431FAE for ; Sat, 21 Jan 2012 10:13:53 -0800 (PST) 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 6o68zHfv9b3D for ; Sat, 21 Jan 2012 10:13:52 -0800 (PST) Received: from dmz-mailsec-scanner-5.mit.edu (DMZ-MAILSEC-SCANNER-5.MIT.EDU [18.7.68.34]) by olra.theworths.org (Postfix) with ESMTP id 26EBD429E49 for ; Sat, 21 Jan 2012 10:13:40 -0800 (PST) X-AuditID: 12074422-b7fd66d0000008f9-69-4f1b004d63f8 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id FA.8E.02297.D400B1F4; Sat, 21 Jan 2012 13:13:33 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id q0LIDWX0020225; Sat, 21 Jan 2012 13:13:33 -0500 Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91]) (authenticated bits=0) (User authenticated as amdragon@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id q0LIDV5j013972 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Sat, 21 Jan 2012 13:13:32 -0500 (EST) Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77) (envelope-from ) id 1RofR6-0008DE-0B; Sat, 21 Jan 2012 13:13:08 -0500 Date: Sat, 21 Jan 2012 13:13:07 -0500 From: Austin Clements To: Tomi Ollila Subject: Re: [PATCH] lib: Save filenames for files detected as "not an email file" in the database. Message-ID: <20120121181307.GI16740@mit.edu> References: <1327096827-5760-1-git-send-email-amdragon@mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpileLIzCtJLcpLzFFi42IR4hTV1vVlkPY32Hxa3eL6zZnMFm9WzmN1 YPI4/HUhi8ezVbeYA5iiuGxSUnMyy1KL9O0SuDI2X9vCVtDKX3H06Be2Bsb/3F2MnBwSAiYS l153sEPYYhIX7q1nA7GFBPYxSlxY7NPFyAVkb2CUeLH9LBOEc5JJYtnOi2wQzhJGiVfnmxlB WlgEVCWeH70INopNQENi2/7lYHERARWJB23rWUFsZgFpiW+/m5lAbGGBVImF2xrBbF4BHYmr e25CrU6VuPn0ECNEXFDi5MwnLBC9WhI3/r0EqucAm7P8HweIySlgIDHptQBIhSjQpiknt7FN YBSahaR5FpLmWQjNCxiZVzHKpuRW6eYmZuYUpybrFicn5uWlFuma6uVmluilppRuYgQFNbuL 0g7GnweVDjEKcDAq8fAm7JP0F2JNLCuuzD3EKMnBpCTKm/1Pyl+ILyk/pTIjsTgjvqg0J7X4 EKMEB7OSCG9ZF1A5b0piZVVqUT5MSpqDRUmcV13rnZ+QQHpiSWp2ampBahFMVoaDQ0mCd91/ oKGCRanpqRVpmTklCGkmDk6Q4TxAw2eD1PAWFyTmFmemQ+RPMSpKifNeAUkIgCQySvPgemFJ 5xWjONArwrwHQap4gAkLrvsV0GAmoMEceWCDSxIRUlINjEu6Q+Ruhl5bdvRmy1bjnLo1N8TP ih2ymiDuJBbDMY1JatO7/3s+NNX/e6aRHfzo1SWN3XMY3evPb5RfKvXhdUfX5j3/HyRkBRae Vks9kH5q9VIuvv413zrkAjNZbeI+X32nJDW3T3vLunqG6IcTShdcWCFynPnkId+k02m3Zdxl BIUsHtw7b6fEUpyRaKjFXFScCAAMVLEeFQMAAA== 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, 21 Jan 2012 18:13:53 -0000 Quoth Tomi Ollila on Jan 21 at 11:48 am: > On Fri, 20 Jan 2012 17:00:27 -0500, Austin Clements wrote: > > Later runs of "notmuch new" won't scan these files again and won't > > print warnings. > > > > Various programs (Dovecot, in my case) store indexes and caches and > > such in the maildir. Without this, notmuch persistently complains > > about such files. > > --- > > LGTM... > > > Every time I run notmuch new I get a slew of these warnings. It was > > starting to get on my nerves, so I implemented the solution suggested > > by the TODO file. > > [ ... ] > > > -large so the detection could be potentially slow). 2. A "notmuch > > -search" syntax could be added to allow the user to find these files, > > -(and perhaps delete them or move them away as appropriate). > > +Add a "notmuch search" syntax to allow uses to find files recorded as > > +non-emails in the database (and perhaps delete them or move them away > > +as appropriate). > > Could these messages be tagged with some fixed tag -- we already have > 'signed' and 'attachment' tag. maybe 'nonemail' (or something) could > be used for these messages ? They aren't actually messages. Messages have a lot of basic metadata that non-email files don't have, so I went with distinct types of documents, figuring that would be much less disruptive than having to deal with message objects that don't support most message methods. For example, if there were a tag (or any general way to query this), it's unclear what the output of notmuch search --output=summary tag:nonemail would be. This isn't necessarily the right approach, but if non-emails *are* represented as messages, I'm not sure what to do with things like notmuch_message_get_message_id and notmuch_message_get_thread_id or how to maintain backwards compatibility for callers that don't expect queries to return non-emails.