Re: How to debug 'ignoring non-mail file' issues
authorPerttu Luukko <perttu.luukko@iki.fi>
Wed, 3 Sep 2014 04:54:39 +0000 (07:54 +0300)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 18:04:25 +0000 (10:04 -0800)
b3/826f17c2dfeab8499d230634f9e934e1931b72 [new file with mode: 0644]

diff --git a/b3/826f17c2dfeab8499d230634f9e934e1931b72 b/b3/826f17c2dfeab8499d230634f9e934e1931b72
new file mode 100644 (file)
index 0000000..ef7ea96
--- /dev/null
@@ -0,0 +1,85 @@
+Return-Path: <perttu.luukko@iki.fi>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id AD748431FB6\r
+       for <notmuch@notmuchmail.org>; Tue,  2 Sep 2014 21:55:10 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id rI8+Slouokl0 for <notmuch@notmuchmail.org>;\r
+       Tue,  2 Sep 2014 21:55:02 -0700 (PDT)\r
+Received: from mail.kapsi.fi (mail.kapsi.fi [217.30.184.167])\r
+       (using TLSv1 with cipher AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 04F3A431FAF\r
+       for <notmuch@notmuchmail.org>; Tue,  2 Sep 2014 21:55:01 -0700 (PDT)\r
+Received: from dsl-jklbrasgw1-54fb12-136.dhcp.inet.fi ([84.251.18.136]\r
+       helo=localhost)\r
+       by mail.kapsi.fi with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16)\r
+       (Exim 4.72) (envelope-from <perttu.luukko@iki.fi>)\r
+       id 1XP2al-0005cQ-2B; Wed, 03 Sep 2014 07:54:47 +0300\r
+Date: Wed, 3 Sep 2014 07:54:39 +0300\r
+From: Perttu Luukko <perttu.luukko@iki.fi>\r
+To: Jani Nikula <jani@nikula.org>\r
+Subject: Re: How to debug 'ignoring non-mail file' issues\r
+Message-ID: <20140903045439.GA5022@rakuuna.dhcp.inet.fi>\r
+References: <20140831074059.GA13399@rakuuna.dhcp.inet.fi>\r
+       <87tx4ssoux.fsf@maritornes.cs.unb.ca>\r
+       <20140901065220.GB3901@lakka.kapsi.fi>\r
+       <20140901071526.GA13634@lakka.kapsi.fi> <87r3ztvjwn.fsf@nikula.org>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+Content-Disposition: inline\r
+In-Reply-To: <87r3ztvjwn.fsf@nikula.org>\r
+User-Agent: Mutt/1.5.22.1 (2013-10-16)\r
+X-SA-Exim-Connect-IP: 84.251.18.136\r
+X-SA-Exim-Mail-From: perttu.luukko@iki.fi\r
+X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false\r
+Cc: notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Wed, 03 Sep 2014 04:55:10 -0000\r
+\r
+On 2014-09-02 23:37:12, Jani Nikula wrote:\r
+> On Mon, 01 Sep 2014, Perttu Luukko <perttu.luukko@iki.fi> wrote:\r
+> > Yes, upgrading to GMime 2.6.20 caused all the messages on my server\r
+> > classified as mail.\r
+> \r
+> What was the old version? If it was 2.4 we should probably consider\r
+> dropping support for that in future notmuch.\r
+\r
+It was 2.4.33. It might still work for other people, I don't know. I\r
+still have some ignored mails. If I can nail down why they are ignored\r
+we might now more about why GMime 2.4 ignored even more mail. They were\r
+from around the same time period, so it might have something to do with\r
+the email setup I had at that time.\r
+\r
+> > Even more reason to give a separate warning for GMime parse errors.\r
+> \r
+> Not sure. We only get a binary success/fail from GMime, and that gets\r
+> printed for all non-email files. I'm not sure it's helpful.\r
+\r
+What I mean that there would be a separate error for cases "Does not\r
+resemble an email message at all", i.e., some control file your mail\r
+server happens to store in the mailbox, and "Looks like mail but we\r
+can't parse it", i.e., better find out why it can't be parsed to avoid\r
+potentially important messages going missing from the database.\r
+\r
+-- \r
+Perttu\r