From: Steven L Baur <steve@miranova.com>
Subject: Re: Problem with multi-line References
Date: 26 Sep 1996 19:51:24 -0700 [thread overview]
Message-ID: <m2lodwd61f.fsf@deanna.miranova.com> (raw)
In-Reply-To: Richard Pieri's message of 26 Sep 1996 13:30:23 -0400
>>>>> "Richard" == Richard Pieri <ratinox@unilab.dfci.harvard.edu> writes:
>>>>> "MB" == Mark Boyns <boyns@sdsu.edu> writes:
MB> A friend mentioned to me that his newsreader is having problems with
MB> the References header that Gnus is generating. Apparently Free
MB> Agent and Netscape cannot deal with a multi-line References header.
Richard> Then they are broken. RFC <mumble> states that headers may span
Richard> multiple lines so long as you indent continuation lines with
Richard> whitespace.
Red Gnus no longer breaks References: lines, so Mark's problem is
``fixed in the next release'' ...
--
steve@miranova.com baur
Unsolicited commercial e-mail will be billed at $250/message.
What are the last two letters of "doesn't" and "can't"?
Coincidence? I think not.
next prev parent reply other threads:[~1996-09-27 2:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-09-26 16:02 Mark Boyns
1996-09-26 17:30 ` Richard Pieri
1996-09-27 2:51 ` Steven L Baur [this message]
1996-09-27 18:54 ` Paul Franklin
1996-09-27 19:30 ` Per Abrahamsen
1996-09-26 17:59 ` William Perry
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=m2lodwd61f.fsf@deanna.miranova.com \
--to=steve@miranova.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).