From: David Bremner <david@tethera.net>
To: Allan Streib <astreib@indiana.edu>, notmuch@notmuchmail.org
Subject: Re: Bug/Issue: References header doesn't wrap in emacs package
Date: Fri, 02 Oct 2015 09:08:45 -0300 [thread overview]
Message-ID: <87si5t1nhu.fsf@zancas.localnet> (raw)
In-Reply-To: <87612qwh04.fsf@viking.dsc.soic.indiana.edu>
Allan Streib <astreib@indiana.edu> 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
>
> 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.
So the first step is to figure out where to best fix this. As a not so
nice workaround, if you remove References from message-hidden-headers
(using e.g. customize), you'll be able to hand wrap the references line.
d
next prev parent reply other threads:[~2015-10-02 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 19:00 Bug/Issue: References header doesn't wrap in emacs package Allan Streib
2015-10-02 12:08 ` David Bremner [this message]
2015-10-03 1:21 ` David Bremner
2016-06-07 2:50 ` Sanjoy Mahajan
2016-06-07 10:28 ` David Bremner
2016-06-07 15:51 ` Sanjoy Mahajan
2017-01-27 0:32 ` David Bremner
2017-03-05 11:45 ` David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87si5t1nhu.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=astreib@indiana.edu \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).