From: Mark Borges <mdb@cdc.noaa.gov>
Cc: Ding Gnus List <ding@ifi.uio.no>
Subject: Re: Q: Cross posted articles
Date: 23 Feb 1996 13:30:08 -0700 [thread overview]
Message-ID: <vkag29yecv.fsf@revelle.cdc.noaa.gov> (raw)
In-Reply-To: ckd@loiosh.kei.com's message of 23 Feb 1996 18:37:15 GMT
>> On 23 Feb 1996 18:37:15 GMT,
>> Christopher Davis(ckd) wrote:
ckd> Try this trick:
ckd> Telnet to the news server's nntp port.
ckd> Type "list overview.fmt".
ckd> See if it includes a line "Xref:full".
ckd> It probably doesn't.
good guess!
mine doesn't (see below). Is this one of those things I "should
complain bitterly to the NetNews administrators" about?
ckd> (PS to Lars: maybe a Red Gnus feature? M-x gnus-check-for-evil-nov ? :)
Does this mean my NOV is eVIl? (I don't really understand the full
repercussions, apart from the obvious that scoring on Xref won't
work). Would I be better served by setting g-n-i-e:
------------------------------------------------------------------------------
gnus-nov-is-evil's value is nil
Documentation:
If non-nil, Gnus backends will never output headers in the NOV format.
------------------------------------------------------------------------------
Thanks for any advice,
-mb-
200 boulder InterNetNews NNRP server INN 1.4unoff2 7-Aug-95 ready (posting ok).
list overview.fmt
215 Order of fields in overview database.
Subject:
From:
Date:
Message-ID:
References:
Bytes:
Lines:
.
next parent reply other threads:[~1996-02-23 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <v0wwx5zkwpt.fsf@corinth.cs.uni-magdeburg.de>
[not found] ` <w8sivhh6570.fsf@aegir.ifi.uio.no>
[not found] ` <x43f869lcc.fsf@fly.cnuce.cnr.it>
[not found] ` <w47mxddh2e.fsf@loiosh.kei.com>
1996-02-23 20:30 ` Mark Borges [this message]
1996-02-23 22:45 ` Steven L Baur
1996-02-24 7:44 ` 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=vkag29yecv.fsf@revelle.cdc.noaa.gov \
--to=mdb@cdc.noaa.gov \
--cc=ding@ifi.uio.no \
/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).