From: Sanjoy Mahajan <sanjoy@olin.edu>
To: David Bremner <david@tethera.net>, Allan Streib <astreib@indiana.edu>,
 <notmuch@notmuchmail.org>
Subject: Re: Bug/Issue: References header doesn't wrap in emacs package
In-Reply-To: <878u7k21d8.fsf@zancas.localnet>
References: <87612qwh04.fsf@viking.dsc.soic.indiana.edu>
 <87si5t1nhu.fsf@zancas.localnet> <878u7k21d8.fsf@zancas.localnet>
User-Agent: Notmuch/0.22 (http://notmuchmail.org) Emacs/24.5.1
 (x86_64-pc-linux-gnu)
Date: Mon, 6 Jun 2016 22:50:45 -0400
Message-ID: <87d1ntg1a2.fsf@insight.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list

On 2015-10-02 21:21, David Bremner <david@tethera.net> wrote:

>>> The problem is a References header that is too long/not wrapped.
>>>
>>
>> Hi Allan;
>>
>> Thanks for the report.  I can see how notmuch-reply would generate a
>> long references header in that situation. We rely on message-mode (part
>> of Gnus) to actually send the message, and it isn't clear to me yet if
>> message-mode (or some function it invokes) normally folds long headers.
>
> I have reported this as an emacs bug.
>
>   http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21608

I'm not sure whether fixing it in emacs is right.  The command 'notmuch
reply' is itself (with the sexp or json formats) generating the too-long
References: header.  Shouldn't it generate an RFC-compliant message?

Or should the json/sexp formats remain agnostic about line length,
because wrapping doesn't make sense with key/value pairs?  In that case,
I agree that message-mode should fix any long lines.

By the way, the latest Exim release (4.87), at least as configured in
Debian, does limit lines to 998 characters, and that limit has been
causing me a few hiccups -- usually when I reply to a message sent by
gmail with a zillion references (perhaps it lists every message in the
thread).

-Sanjoy