From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: [news.software.readers] GNKSA: Gnus 5.0.15
Date: 27 Mar 1996 05:11:55 +0000 [thread overview]
Message-ID: <w8sohpj86hw.fsf@hler.ifi.uio.no> (raw)
*sob*
Gnus didn't pass. So I think I'll have to make Gnus a bit stricter.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
------- Start of forwarded message -------
From: gdr11@cl.cam.ac.uk (Gareth Rees)
Newsgroups: news.software.readers
Subject: GNKSA: Gnus 5.0.15
Date: 25 Mar 1996 18:57:59 +0000
Organization: Garbanzo Creative Media
Message-ID: <yxs68btyp8o.fsf@stint.cl.cam.ac.uk>
This is an evaluation of the newsreader Gnus 5.0.15 according to Ron
Newman's "Good Netkeeping Seal of Approval" (GNKSA).
Gnus 5.0.15 (hereafter "Gnus") is a newreader written by Lars Magne
Ingebrigtsen in Emacs LISP for the GNU Emacs editor. A slightly earlier
version, Gnus 5.0.13, is distributed with GNU Emacs 19. A new version
of Gnus ("September Gnus") is in development.
For more information, see the following references.
* Gnus: <http://www.ifi.uio.no/~larsi/ding.html>
* Good Netkeeping Seal of Approval:
<http://www.cybercom.net/~rnewman/Good_Netkeeping_Seal>
* Other GNKSA evaluations:
<http://http.bsd.uchicago.edu/~t-pierce/news/index.html>
Gnus fails the Good Net-Keeping Seal of Approval for the following
reasons.
* You can post an article with an empty "Subject" header.
* You can post an article with a "From" header containing a
syntactically invalid e-mail address.
Note that, in both cases, Gnus recognises that the header is incorrect,
and it asks whether you really mean to post the article. But if you
answer "yes" then the article is posted anyway. It is not clear to me
whether the GNKSA means that the news posting agent should prevent
posting of *all* article with incorrect headers, or merely prevent
*accidental* posting of such articles. If the latter, then Gnus
certainly passes the GNKSA. However, I think that posting such articles
should be made more difficult than just answering "yes" to a prompt.
Perhaps the readers of this evaluation can comment further on this
issue?
The full evaluation follows.
------------------------------------------------------------------------
Item number in GNKSA document Sub-item passes test?
| Item is required to pass the GNKSA? | Item passes?
| | Description of item | | Notes
------------------------------------------------------------------------
1 Y Display all essential header info YES
Y default is to display YES
Y a) display author YES
Y b) display subject YES
Y c) display newsgroups list YES
Y d) display Followup-To list YES
Y e) display Reply-To if different from From YES
------------------------------------------------------------------------
2 Y Provide standard commands YES
Y clear YES
Y separate YES
Y a) post a new article YES
Y b) post a followup article YES
Y c) reply by email YES
N use standard terminology YES
------------------------------------------------------------------------
3 Y Implement cross-posting YES
Y allow user specification YES
Y cross-post (not multi-post) YES
------------------------------------------------------------------------
4 Y Change essential headers YES
Y change headers while editing body YES
Y change Subject YES
Y allow at least 70 chars in subject YES
Y change Newsgroups YES
Y change Followup-To YES (1)
Y allow Followup-To: poster YES
Y change Reply-To YES
------------------------------------------------------------------------
5 Y Correct Subject headers in followup/reply YES
Y a) prepend "Re: " (exactly!) YES
Y b) preserve entire Subject YES
Y even subjects longer than 80 characters YES
------------------------------------------------------------------------
6 Y Respect Followup-To YES
Y use to initialize Newsgroups in followup YES
Y recognize and act on Followup-To: poster YES
------------------------------------------------------------------------
7 Y Followups contain References
Y contains Message-ID of original YES
Y never truncate individual Message-ID YES
N contains three References of original YES
N contains entire References of original YES
N contains any message-id mentioned in body YES
------------------------------------------------------------------------
8 Y Direct email reply to Reply-To YES
------------------------------------------------------------------------
9 Y Quotation and attribution YES
Y provide method YES
Y set off by prepend YES
Y attribution line YES
Y identifies author YES
N gives message-id YES
------------------------------------------------------------------------
10 Y Subject is mandatory NO
Y do not post empty Subject or "<none>" NO (2)
Y allow change while editing body YES
------------------------------------------------------------------------
11 Y Must provide valid From header NO
Y syntactically valid NO (3)
N belongs to the user NO
------------------------------------------------------------------------
12 Y Must provide cancel YES
Y of own articles YES
Y *not* of others YES
------------------------------------------------------------------------
13 N Respect line length, and post WYSIWYG YES
N line breaks shown are present when posted YES
N do *not* post paragraph without line breaks YES
N warn if body has lines longer than 80 chars YES
N external editor (if any) conforms N/A (4)
------------------------------------------------------------------------
14 N Prevent obvious errors NO
N prevent posting empty article NO (5)
N prevent posting only quoted text NO (5)
------------------------------------------------------------------------
Notes:
(1) It is possible to configure Gnus so that it prompts you whenever you
are following up an article that has been cross-posted, and so that
it prompts you whenever the Followup-To header is different from the
Newsgroups header. These options provide a useful defence against
maliciously or accidentally inappropriate Newsgroups and Followup-To
headers.
(2) Gnus allows you to post an article with an empty "Subject" header.
Gnus does recognise when the "Subject" header is empty and asks
whether you really mean to post it, but if you answer "yes" then the
article is posted anyway.
(3) Gnus allows you to post an article with a "From" header containing a
syntactically invalid e-mail address. Gnus does recognise when the
"From" header is bogus and asks whether you really mean to post it,
but if you answer "yes" then the article is posted anyway.
(4) Gnus uses the editing facilities of Emacs, so has no external
editor.
(5) The documentation says that these errors should be tested for and
detected, but they aren't. Presumably this is a bug that will be
fixed in later releases.
--
Gareth Rees
------- End of forwarded message -------
next reply other threads:[~1996-03-27 5:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-27 5:11 Lars Magne Ingebrigtsen [this message]
1996-03-27 6:13 ` Steven L. Baur
1996-03-27 6:14 ` Lars Magne Ingebrigtsen
1996-03-27 7:18 ` d. hall
1996-03-28 4:57 ` Lars Magne Ingebrigtsen
1996-03-27 23:56 ` Russ Allbery
1996-03-28 4:59 ` Lars Magne Ingebrigtsen
1996-03-28 6:33 ` Russ Allbery
1996-03-28 6:48 ` Lars Magne Ingebrigtsen
1996-03-28 8:48 ` Gareth Rees
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=w8sohpj86hw.fsf@hler.ifi.uio.no \
--to=larsi@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).