Allan Streib writes:
> Notmuch/0.20.2 (http://notmuchmail.org) Emacs/24.4.1
>
> Replying to a message in a deeply nested thread can trigger a complaint:
>
> sendmail: command failed: 550 5.7.1 Delivery not authorized, message
> refused: Message is not RFC 2822 compliant
>
Sanjoy Mahajan writes:
> On 2016-06-07 06:28, David Bremner wrote:
>
>> Sanjoy Mahajan writes:
>>
>>
>>> I'm not sure whether fixing it in emacs is right. The command 'notmuch
>>> reply' is itself (with the sexp or json formats) generating
On 2016-06-07 06:28, David Bremner wrote:
> Sanjoy Mahajan writes:
>
>
>> 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
Sanjoy Mahajan writes:
> 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
On 2015-10-02 21:21, David Bremner 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
Allan Streib writes:
> Notmuch/0.20.2 (http://notmuchmail.org) Emacs/24.4.1
>
> Replying to a message in a deeply nested thread can trigger a complaint:
>
> sendmail: command failed: 550 5.7.1 Delivery not authorized, message
> refused: Message is not RFC 2822 compliant
>
David Bremner writes:
> Allan Streib writes:
>
>> Notmuch/0.20.2 (http://notmuchmail.org) Emacs/24.4.1
>>
>> Replying to a message in a deeply nested thread can trigger a complaint:
>>
>> sendmail: command failed: 550 5.7.1 Delivery not authorized,
Notmuch/0.20.2 (http://notmuchmail.org) Emacs/24.4.1
Replying to a message in a deeply nested thread can trigger a complaint:
sendmail: command failed: 550 5.7.1 Delivery not authorized, message refused:
Message is not RFC 2822 compliant
The problem is a References header that is too