From: Karl Kleinpaste <karl@jprc.com>
Subject: GNKSoA
Date: 14 Oct 1997 14:35:26 -0400 [thread overview]
Message-ID: <vxkk9fgur9t.fsf@pocari-sweat.jprc.com> (raw)
I happened by Tim Pierce's archive of GNKSoA evaluations, noticing
that 5.3 failed GNKSoA by only one nit in the spec:
Gnus fails the Good Netkeeping Seal of Approval on one rather minor
count:
* You can post an article with a "From" header containing a
syntactically invalid e-mail address. Although Gnus does check the
syntax of the "From" header, its checks are not robust enough. See
note (1) for details.
I just looked into the current state of q0.12's From-checking in
message.el, around line 2301, and it seems relatively robust, though I
no longer have older Gnus versions around, against which to compare.
Is there any longer a reason why Gnus shouldn't finally and fully be
declared "GNKSoA compliant"?
next reply other threads:[~1997-10-14 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-14 18:35 Karl Kleinpaste [this message]
1997-10-14 20:04 ` GNKSoA Hrvoje Niksic
1997-10-23 22:20 ` GNKSoA Justin Sheehy
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=vxkk9fgur9t.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).