Date: Wed, 3 Sep 2014 07:54:39 +0300
From: Perttu Luukko <perttu.luukko@iki.fi>
To: Jani Nikula <jani@nikula.org>
Subject: Re: How to debug 'ignoring non-mail file' issues
Message-ID: <20140903045439.GA5022@rakuuna.dhcp.inet.fi>
References: <20140831074059.GA13399@rakuuna.dhcp.inet.fi>
	<87tx4ssoux.fsf@maritornes.cs.unb.ca>
	<20140901065220.GB3901@lakka.kapsi.fi>
	<20140901071526.GA13634@lakka.kapsi.fi> <87r3ztvjwn.fsf@nikula.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87r3ztvjwn.fsf@nikula.org>
User-Agent: Mutt/1.5.22.1 (2013-10-16)
Cc: notmuch@notmuchmail.org
Precedence: list

On 2014-09-02 23:37:12, Jani Nikula wrote:
> On Mon, 01 Sep 2014, Perttu Luukko <perttu.luukko@iki.fi> wrote:
> > Yes, upgrading to GMime 2.6.20 caused all the messages on my server
> > classified as mail.
> 
> What was the old version? If it was 2.4 we should probably consider
> dropping support for that in future notmuch.

It was 2.4.33. It might still work for other people, I don't know. I
still have some ignored mails. If I can nail down why they are ignored
we might now more about why GMime 2.4 ignored even more mail. They were
from around the same time period, so it might have something to do with
the email setup I had at that time.

> > Even more reason to give a separate warning for GMime parse errors.
> 
> Not sure. We only get a binary success/fail from GMime, and that gets
> printed for all non-email files. I'm not sure it's helpful.

What I mean that there would be a separate error for cases "Does not
resemble an email message at all", i.e., some control file your mail
server happens to store in the mailbox, and "Looks like mail but we
can't parse it", i.e., better find out why it can't be parsed to avoid
potentially important messages going missing from the database.

-- 
Perttu