From: Jeff Senn <senn@maya.com>
Subject: Re: Continued header lines?
Date: Thu, 04 Oct 2001 11:07:21 -0400 [thread overview]
Message-ID: <k7ybsaty.fsf@SNIPE.maya.com> (raw)
In-Reply-To: <m3k7ycfkbh.fsf@defun.localdomain> (Jesper Harder's message of "Thu, 04 Oct 2001 00:08:34 +0200")
Jesper Harder <harder@ifa.au.dk> writes:
> prj@po.cwru.edu (Paul Jarc) writes:
>
>> Gnus could use long header lines instead of wrapping them, couldn't
>> it? Or would that cause problems with other badly-written things?
>
> It would violate RFC 2822:
>
> ,----
> | There are two limits that this standard places on the number of
> | characters in a line. Each line of characters MUST be no more than
> | 998 characters, and SHOULD be no more than 78 characters, excluding
> | the CRLF.
> `----
FWIW: I've even noticed that some 80<lines<998 cause (some versions
of?) Eudora to screw up it's header parsing....
--
-Jas -------------------- www.maya.com
Jeff Senn | / / |-/ \ / /|
Chief Technologist | /|/| |/ o | /-|
Head of R&D | Taming Complexity
next prev parent reply other threads:[~2001-10-04 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 17:34 Simon Josefsson
2001-10-02 20:55 ` Jesper Harder
2001-10-03 9:26 ` Simon Josefsson
2001-10-03 14:57 ` Paul Jarc
2001-10-03 22:08 ` Jesper Harder
2001-10-04 15:07 ` Jeff Senn [this message]
2001-10-03 22:24 ` Jesper Harder
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=k7ybsaty.fsf@SNIPE.maya.com \
--to=senn@maya.com \
/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).