From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Continued header lines?
Date: Tue, 02 Oct 2001 22:55:58 +0200 [thread overview]
Message-ID: <m3itdxlq1t.fsf@defun.localdomain> (raw)
In-Reply-To: <iluwv2eaqu1.fsf@barbar.josefsson.org> (jas@extundo.com's message of "Tue, 2 Oct 2001 17:35:44 +0000 (UTC)")
jas@extundo.com (Simon Josefsson) writes:
> I found a IMAP server [1] that completely garble mail (data
> corruption) if you use long header lines such as
>
> Foo: bar
> baz
>
> e.g. padding continuation header lines with SPC. Using TAB instead
> seems to work. Maybe Gnus should do what most other mailers seem to
> do (use TAB, that is)?
I think that would be wrong according to RFC 2822. If you fold
Foo: bar baz
as
Foo: bar
<HTAB>baz
Then you would get
Foo: bar<HTAB>baz
when unfolding the header, which isn't the same as the original.
next prev parent reply other threads:[~2001-10-02 20:55 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 [this message]
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
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=m3itdxlq1t.fsf@defun.localdomain \
--to=harder@ifa.au.dk \
/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).