Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@jprc.com>
Subject: SPCs can hurt overviews (was Inexplicable all.SCORE analysis)
Date: 24 Sep 1997 21:23:46 -0400	[thread overview]
Message-ID: <vxksouugp99.fsf_-_@pocari-sweat.jprc.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "25 Sep 1997 00:17:04 +0200"

The erroneously-scored articles previously mentioned contain a Lines:
header which include trailing SPCs, e.g., "^Lines: 15        $".  This
confuses overview parsing, because the SPCs manage to survive into
INN's overview files, and Gnus does not hunt down the next TAB properly.

Looks like a user agent flaw, to start with; the articles in question
claim an agent tag of QWK v2.12.  Thereafter, it's INN's fault for
letting trailing SPCs into the overviews, though one could argue that
INN was doing the correct thing (copy blindly).  And lastly, it's
Gnus' mistake not to have hunted for the separating TAB properly.

Please experiment by implementing an "xref" score rule such as
	("xref" (".* .* .* .* .* .*" -10 nil r))
in all.SCORE and siccing it on <970923100046612@eqcity.ktb.net> in
comp.protocols.tcp-ip.domains.

(q 0.10, xemacs 19.14, inn 1.5.1.)

regards,
--karl


  reply	other threads:[~1997-09-25  1:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-09-23 18:29 Inexplicable all.SCORE analysis Karl Kleinpaste
1997-09-23 21:38 ` SL Baur
1997-09-23 23:58 ` Lars Magne Ingebrigtsen
1997-09-24 15:20   ` Karl Kleinpaste
1997-09-24 22:17     ` Lars Magne Ingebrigtsen
1997-09-25  1:23       ` Karl Kleinpaste [this message]
1997-09-27  3:35         ` SPCs can hurt overviews (was Inexplicable all.SCORE analysis) Lars Magne Ingebrigtsen

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=vxksouugp99.fsf_-_@pocari-sweat.jprc.com \
    --to=karl@jprc.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).