header continuation issue in notmuch frontend/alot/pythons email module

Thomas Schwinge thomas at codesourcery.com
Mon Jun 24 02:19:32 PDT 2013


Hi!

On Mon, 24 Jun 2013 10:57:10 +0200, Justus Winter <4winter at informatik.uni-hamburg.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:
> > > 
> > > ~~~ snip ~~~
> > > [...]
> > > To: someone at example.org, "line
> > >  break" <linebreak at example.org>, someoneelse at example.org
> > > User-Agent: Notmuch/0.9-101-g81dad07 (http://notmuchmail.org) Emacs/23.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 at kepler.schwinge.homeip.net

Here is the header from the message as I sent it:

    To: Samuel Thibault <samuel.thibault at gnu.org>, Justus Winter
     <4winter at informatik.uni-hamburg.de>, fotis.koutoulakis at gmail.com, Ian
     Lance Taylor <iant at google.com>, toscano.pino at tiscali.it, Luis Machado
     <lgustavo at codesourcery.com>, =?utf-8?B?6ZmG5bKz?=
     <hacklu.newborn at gmail.com>

And this is what I received from the bug-hurd mailing list:

    To: Samuel Thibault <samuel.thibault at gnu.org>, Justus Winter
    	<4winter at informatik.uni-hamburg.de>, <fotis.koutoulakis at gmail.com>, "Ian
    	Lance Taylor" <iant at google.com>, <toscano.pino at tiscali.it>, Luis Machado
    	<lgustavo at codesourcery.com>,
    	=?utf-8?B?6ZmG5bKz?= <hacklu.newborn at gmail.com>

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üße,
 Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: not available
URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20130624/0ecdd369/attachment-0001.pgp>


More information about the notmuch mailing list