From: Russ Allbery <rra@stanford.edu>
Subject: Re: [Mail Delivery System <Mailer-Daemon@quimby2.netfonds.no>] Mail delivery failed: returning message to sender
Date: Sun, 30 Dec 2001 13:52:50 -0800 [thread overview]
Message-ID: <ylsn9sbcjx.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <m3wuz4jtks.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 30 Dec 2001 22:17:55 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> I don't really think it's all that helpful to fold the headers in this
> way -- folding right after the header name will probably make some
> software bug out (as we have seen here).
Yup, long-standing bug in INN that I've not gotten around to fixing.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
prev parent reply other threads:[~2001-12-30 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-30 20:57 Simon Josefsson
2001-12-30 21:17 ` Lars Magne Ingebrigtsen
2001-12-30 21:52 ` Russ Allbery [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ylsn9sbcjx.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/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.
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 NNTP newsgroup(s).