From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ricardo Wurmus <rekado@elephly.net>
Subject: Re: Mumi now uses raw emails and Mu
Date: Tue, 23 Jul 2019 15:49:24 +0200
Message-ID: <87y30oc13v.fsf@elephly.net>
References: <87ef2jdtuc.fsf@elephly.net>
 <alpine.DEB.2.20.1907212035220.9756@marsh.hcoop.net>
 <87blxme6pk.fsf@elephly.net> <875zntc8ux.fsf@elephly.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:37970)
 by lists.gnu.org with esmtp (Exim 4.86_2)
 (envelope-from <rekado@elephly.net>) id 1hpvAl-0005P7-3d
 for guix-devel@gnu.org; Tue, 23 Jul 2019 09:49:44 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <rekado@elephly.net>) id 1hpvAk-0002Xq-5S
 for guix-devel@gnu.org; Tue, 23 Jul 2019 09:49:43 -0400
Received: from sender-of-o51.zoho.com ([135.84.80.216]:21223)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
 (Exim 4.71) (envelope-from <rekado@elephly.net>) id 1hpvAj-0002WY-Pm
 for guix-devel@gnu.org; Tue, 23 Jul 2019 09:49:42 -0400
In-reply-to: <875zntc8ux.fsf@elephly.net>
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Jack Hill <jackhill@jackhill.us>
Cc: guix-devel@gnu.org


Ricardo Wurmus <rekado@elephly.net> writes:

> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> Forking Mu requires a rough understanding how it currently works.
>> Obviously, it must parse emails and extract certain headers.  We only
>> need it to extract a few more headers such as =E2=80=9CX-Debbugs-Envelop=
e-To=E2=80=9D,
>> which contains the Debbugs bug number.  (I don=E2=80=99t know if that he=
ader is
>> set for *all* emails that end up in the bug tracker, but that=E2=80=99s
>> something we have to figure out.)
>>
>> Mu is written in C and the header extraction probably happens in the C
>> code as well.
>
> I forked Mu and let it store the =E2=80=9CX-Debbugs-Envelope-To=E2=80=9D =
header in the
> database:[=E2=80=A6]
> This seems to actually work.  Still don=E2=80=99t know if all emails actu=
ally
> have that header

They don=E2=80=99t.  Most obviously the first email that causes the bug to =
be
registered doesn=E2=80=99t include the header.  In mumi we can assume that =
the
file name of the email includes the bug number, though, so that=E2=80=99s an
easy albeit ugly workaround.

--
Ricardo