From: Toby Speight <Toby.Speight@streapadair.freeserve.co.uk>
Subject: Broken References (was: Cups)
Date: 25 Nov 1999 17:52:56 +0000 [thread overview]
Message-ID: <ubt8isbk7.fsf_-_@lanber.cam.citrix.com> (raw)
In-Reply-To: Gunnar Evermann's message of "25 Nov 1999 17:18:28 +0000"
Gunnar> Gunnar Evermann <URL:mailto:ge204@cam.ac.uk>
0> In article <mqqk8n6v6aj.fsf@eng.cam.ac.uk>, Gunnar wrote:
Gunnar> [Jan Vroonhof's] References header[in article
Gunnar> <byso1ucxdh.fsf@bolzano.math.ethz.ch>] is broken:
>> References: <m34sef90y1.fsf@quimbies.gnus.org> <sdg0xyh1vv.fsf@wanderer.dcn.davis.ca.us> <m3ln7nn0mq.fsf@quimbies.gnus.org> <86903n762l.fsf@megalith.bp.aventail.com> <vafu2mblylj.fsf@lucy.cs.uni-dortmund.de> <k8zd7sydabl.fsf@alcatel.de> <86wvr6v9sb.fsf@me
Gunnar> is that a known bug?
It's probably an MTA bug somewhere (or feature - I can't remember
what the line-length limit is on headers). Perhaps we should be able
to tell Gnus that we're passing the message to a network that does
this. In times gone past, Gnus used to wrap long References lines,
but no longer does (in order to coddle broken readers). Can we go
back to doing this? Or remove the oldest references to reduce the
line length?
next prev parent reply other threads:[~1999-11-25 17:52 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-21 18:03 Cups Lars Magne Ingebrigtsen
1999-11-22 17:28 ` Cups Wes Hardaker
1999-11-23 7:18 ` Cups Steinar Bang
1999-11-23 14:51 ` Cups Wes Hardaker
1999-11-23 16:18 ` Cups Bud Rogers
1999-11-23 16:45 ` Cups Harry Putnam
1999-11-23 16:58 ` Cups Mats Lvfdahl
1999-11-23 17:42 ` Cups Wes Hardaker
1999-11-23 18:31 ` Cups Jeff Senn
1999-11-23 21:20 ` Cups Wes Hardaker
1999-11-24 7:51 ` Cups Steinar Bang
1999-11-24 15:35 ` Cups Wes Hardaker
1999-11-24 15:42 ` Cups Hrvoje Niksic
1999-11-24 22:08 ` Cups Wes Hardaker
1999-11-23 18:44 ` Cups Bud Rogers
1999-11-23 17:32 ` Cups Felix Hagemann
1999-11-23 20:12 ` Flying terminator (was: Re: Cups) Jeff Senn
1999-11-23 21:35 ` leafnode - gnus Pieter Wenk
1999-11-24 14:51 ` Pieter Wenk
1999-11-23 22:52 ` Flying terminator (was: Re: Cups) Dan Mills
1999-11-24 17:04 ` Jeff Senn
1999-11-30 7:49 ` Rob Browning
1999-11-24 19:35 ` Cups Lars Magne Ingebrigtsen
1999-11-24 22:03 ` Cups Wes Hardaker
1999-11-25 0:44 ` Cups William M. Perry
1999-11-25 9:17 ` Cups Kai Großjohann
1999-11-25 12:28 ` Cups Colin Marquardt
1999-11-25 15:33 ` Cups Kai Großjohann
1999-11-25 16:03 ` Cups William M. Perry
1999-11-25 16:30 ` Cups Simon Josefsson
1999-11-25 16:35 ` Cups Lars Magne Ingebrigtsen
1999-11-25 16:44 ` Cups Hrvoje Niksic
1999-11-25 17:38 ` Cups Lars Magne Ingebrigtsen
1999-11-25 19:54 ` Cups Felix Hagemann
1999-11-25 23:41 ` Cups William M. Perry
1999-11-26 4:10 ` Cups Bud Rogers
1999-11-26 17:11 ` Cups Per Abrahamsen
1999-11-26 8:13 ` Cups Daniel Pittman
1999-11-29 21:01 ` Cups Bill White
1999-11-25 17:08 ` Cups Jan Vroonhof
[not found] ` <86wvr6v9sb.fsf@me <byso1ucxdh.fsf@bolzano.math.ethz.ch>
1999-11-25 17:18 ` Cups Gunnar Evermann
1999-11-25 17:52 ` Toby Speight [this message]
1999-11-25 18:06 ` Broken References (was: Cups) Hrvoje Niksic
1999-11-25 20:00 ` Russ Allbery
1999-11-25 20:09 ` Hrvoje Niksic
1999-11-25 20:23 ` Russ Allbery
1999-11-25 20:43 ` Hrvoje Niksic
1999-11-25 21:00 ` Lars Magne Ingebrigtsen
1999-11-25 18:37 ` Cups Jan Vroonhof
1999-11-25 18:55 ` Cups Jan Vroonhof
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=ubt8isbk7.fsf_-_@lanber.cam.citrix.com \
--to=toby.speight@streapadair.freeserve.co.uk \
/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).