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 BEBD240DF1C for ; Sat, 20 Nov 2010 03:11:04 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham 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 c0+5CJL7CYEC for ; Sat, 20 Nov 2010 03:10:54 -0800 (PST) Received: from smtp3-g21.free.fr (smtp3-g21.free.fr [212.27.42.3]) by olra.theworths.org (Postfix) with ESMTP id 06BF840DF1B for ; Sat, 20 Nov 2010 03:10:52 -0800 (PST) Received: from racin (unknown [82.239.207.166]) by smtp3-g21.free.fr (Postfix) with ESMTP id 79CAAA6276; Sat, 20 Nov 2010 12:10:46 +0100 (CET) From: Matthieu Lemerre To: Daniel Kahn Gillmor , notmuch Subject: Re: Warning when GMime is parsing broken email addresses In-Reply-To: <4CE575CF.2080309@fifthhorseman.net> References: <87ipzvk2xh.fsf@free.fr> <87d3q2sckw.fsf@free.fr> <4CE575CF.2080309@fifthhorseman.net> User-Agent: Notmuch/0.5 (http://notmuchmail.org) Emacs/23.2.1 (i486-pc-linux-gnu) Date: Sat, 20 Nov 2010 12:23:16 +0100 Message-ID: <87lj4oqlwb.fsf@free.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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, 20 Nov 2010 11:11:04 -0000 On Thu, 18 Nov 2010 13:51:59 -0500, Daniel Kahn Gillmor wrote: > Re: Warning when GMime is parsing broken email addresses: > > On 11/18/2010 01:37 PM, Matthieu Lemerre wrote: > > The problem is solved in version 2.4.18 (current is > > 2.4.20). Unfortunately the last version packaged for Debian is 2.4.14... > > is the patch that fixes the problem it backportable to 2.4.14 ? I'm > sure a report to the debian bts with a patch would be appreciated. even > if it doesn't make it into the release because of the freeze, a > narrowly-targeted patch might be acceptable for a future point release. Don't know. The main problem is that the package seems to have been more or less abandoned by its maintainer though...