From: Thomas Schwinge Date: Mon, 24 Jun 2013 09:19:32 +0000 (+0200) Subject: Re: header continuation issue in notmuch frontend/alot/pythons email module X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=a6c20d07ffdecf7761855596ed4aa86c8f02f1e5;p=notmuch-archives.git Re: header continuation issue in notmuch frontend/alot/pythons email module --- diff --git a/43/7a26b5274048f303f03003b5c207f780cc884e b/43/7a26b5274048f303f03003b5c207f780cc884e new file mode 100644 index 000000000..9b2fa4fbd --- /dev/null +++ b/43/7a26b5274048f303f03003b5c207f780cc884e @@ -0,0 +1,142 @@ +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 3E093431FBD + for ; Mon, 24 Jun 2013 02:20:34 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: 0 +X-Spam-Level: +X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] + 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 MXA+P9tj0aZV for ; + Mon, 24 Jun 2013 02:20:28 -0700 (PDT) +Received: from relay1.mentorg.com (relay1.mentorg.com [192.94.38.131]) + by olra.theworths.org (Postfix) with ESMTP id 46E3D431FAF + for ; Mon, 24 Jun 2013 02:20:28 -0700 (PDT) +Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58]) + by relay1.mentorg.com with esmtp + id 1Ur2wc-0004eJ-O0 from Thomas_Schwinge@mentor.com ; + Mon, 24 Jun 2013 02:20:18 -0700 +Received: from SVR-IES-FEM-01.mgc.mentorg.com ([137.202.0.104]) by + SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft + SMTPSVC(6.0.3790.4675); Mon, 24 Jun 2013 02:20:14 -0700 +Received: from feldtkeller.schwinge.homeip.net (137.202.0.76) by + SVR-IES-FEM-01.mgc.mentorg.com (137.202.0.104) with Microsoft SMTP + Server id 14.2.247.3; Mon, 24 Jun 2013 10:20:13 +0100 +From: Thomas Schwinge +To: Justus Winter <4winter@informatik.uni-hamburg.de>, Austin Clements + +Subject: Re: header continuation issue in notmuch frontend/alot/pythons email + module +In-Reply-To: <20130624085710.31827.41792@thinkbox.jade-hamburg.de> +References: <20130623131145.2526.439@thinkbox.jade-hamburg.de> + <20130623165938.GA2214@mit.edu> + <20130624085710.31827.41792@thinkbox.jade-hamburg.de> +User-Agent: Notmuch/0.9-101-g81dad07 (http://notmuchmail.org) Emacs/23.4.1 + (x86_64-pc-linux-gnu) +Date: Mon, 24 Jun 2013 11:19:32 +0200 +Message-ID: <8738s7kgrf.fsf@schwinge.name> +MIME-Version: 1.0 +Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; + protocol="application/pgp-signature" +X-OriginalArrivalTime: 24 Jun 2013 09:20:14.0525 (UTC) + FILETIME=[08DDF6D0:01CE70BC] +X-Mailman-Approved-At: Mon, 24 Jun 2013 02:50:13 -0700 +Cc: notmuch mailing list +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: Mon, 24 Jun 2013 09:20:34 -0000 + +--=-=-= +Content-Type: text/plain; charset=utf-8 +Content-Transfer-Encoding: quoted-printable + +Hi! + +On Mon, 24 Jun 2013 10:57:10 +0200, Justus Winter <4winter@informatik.uni-h= +amburg.de> wrote: +> Quoting Austin Clements (2013-06-23 18:59:39) +> > Quoth Justus Winter on Jun 23 at 3:11 pm: +> > > I recently had a problem replying to a mail written by Thomas Schwinge +> > > using an oldish notmuch. Not sure if it has been fixed in more recent + +"Oldish", yeah, yeah, I know... (Mumbles someting about long TODO list.) + +> > > versions, but I think notmuch could improve uppon its header +> > > generation (see below). Problematic part of the mail: +> > >=20 +> > > ~~~ snip ~~~ +> > > [...] +> > > To: someone@example.org, "line +> > > break" , someoneelse@example.org +> > > User-Agent: Notmuch/0.9-101-g81dad07 (http://notmuchmail.org) Emacs/2= +3.4.1 (i486-pc-linux-gnu) +> > > [...] +> > > ~~~ snap ~~~ + +> > Do you happen to know how the strangely folded "to" header was +> > produced for this message? + +I just entered/copied all the addresses into one long To: line, and then +let message-mode do its thing. + +> No, but Thomas might. Thomas, the problematic message is +> id:877ghpqckb.fsf@kepler.schwinge.homeip.net + +Here is the header from the message as I sent it: + + To: Samuel Thibault , Justus Winter + <4winter@informatik.uni-hamburg.de>, fotis.koutoulakis@gmail.com, Ian + Lance Taylor , toscano.pino@tiscali.it, Luis Machado + , =3D?utf-8?B?6ZmG5bKz?=3D + + +And this is what I received from the bug-hurd mailing list: + + To: Samuel Thibault , Justus Winter + <4winter@informatik.uni-hamburg.de>, , "I= +an + Lance Taylor" , , Luis Macha= +do + , + =3D?utf-8?B?6ZmG5bKz?=3D + +So the "corruption" (if it is declared as one; I don't have time right +now to follow your RFC interpretation) must have happened after sending +it off -- perhaps my company's Microsoft Exchange server (as Justus +received a direct copy from that one), or even msmtp used as the local +MTA. + + +Gr=C3=BC=C3=9Fe, + Thomas + +--=-=-= +Content-Type: application/pgp-signature + +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.11 (GNU/Linux) + +iQEcBAEBAgAGBQJRyA8kAAoJENuKOtuXzphJ3e8H/2SOhqjUnh0EqSgERmqwApsb +bb05uBqjkeEPEnBWvlP3lLNDDiLBqo365W4l/UDulVLnBGZpziiVdtnYcwVvnQiB +ttqhrDSTkWb2fnk41j6fda64xP+UJP36NGECPjmLPi+eU8dpaNfeF+41ZEShN2uZ +Bp1wbwMwOxEJwkLdShQPlZ6qMDrX8skCx5vxErdRTBb/ZLHLTJ4wDuMrWXL6IXXk +3Dg+S5VPCtDUL6QHrbp0fgJEtKanDrXn4cp/pMZ98HUuuwdsILiQVMD2OZqDMIiC +UI6m4AG2J8ZNUjgqzpoD3uVRgaBi9ggz4vPVCFaWPraVJBPP8qB6+sznVLX7zrE= +=MWpo +-----END PGP SIGNATURE----- +--=-=-=--