All GNKSA/U evaluations are compiled by Tim Pierce at <URL:http://http.bsd. uchicago.edu/~twpierce/news/>. My own evaluations are also summarised at <URL:http://www.mygale.org/ 11/bubulle/gnksa>.


WARNING : Debates about NS Communicator 4.0b1 have been very hot in early January 1997, about the ability of the software to send so-called "HTML-formatted" articles in news, by default. The present review is not focused on this subject but only on GNKSA/U criteria defined by Ron Newman in 1995


The software as reviewed fails to receive the Good Net-Keeping Seal of Approval for Usenet Software (see <URL:http://www.freenix.fr /~freenix/controle> for a french translation of the Seal) for the following reason :

  1. The syntax checking of the From: address is lacking. This check was present (though incomplete) in all Netscape Navigator 3.0 releases.

Though not required by GNKSA/U, some points could be improved :

  1. Users should be warned when posting articles with lines longer than 80 characters (see 9),
  2. The software should prevent posting articles without text or only quoted text,
  3. When posting a followup, the original article should be quoted by default (see 3) .

This software may be downloaded at the following address :


Below is the detailed evaluation checklist :


Subject: The detailed evaluation checklist 
   
Req Itm                                          Sub-    Item   
rd? ##  Description                            item OK?   OK?     Notes   
   
Y    1  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 /= From:         YES
   
Y    2  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                NO                  1) 
   
Y    3  Implement cross-posting                           YES   
  Y       allow user specification                YES
  Y       cross-post (not multi-post)             YES  
   
Y    4  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
  Y       allow followup-to: poster               YES                 
  Y       change Reply-To                         YES                 
   
Y    5  Correct Subject headers in flwup/rply             YES         2)  
  Y       a) prepend "Re: " (exactly!)            YES   
  Y       b) preserve entire Subject              YES   
  Y          even subjects > 80 chars long        YES   
   
Y    6  Respect Followup-To                               YES  
  Y       use to initialize Newsgroups: in flwup  YES
  Y       recognize and act on 'poster'           YES         
  
Y    7  Followups contain References                      YES   
  Y       contains message-id of original         YES   
  Y       never truncate individual message-id    YES
  N       contains three Refs from original       YES   
  N       contains entire Refs of original        YES   
   
Y    8  Direct email reply to Reply-To                    YES
   
Y    9  Quotation and attribution                         YES         
  Y       provide method                          YES                 3)    
  Y       set off by prepend                      YES               
  Y       attribution line                        YES
  Y         identifies author                     YES                 4)                 
  N         gives message-id                      NO               
   
Y   10  Subject is mandatory                              YES   
  Y       do not post empty or provide <none>     YES                 5)               
  Y       allow change while editing body         YES   
   

Y   11  Must provide valid From: header
NO        
  Y       syntactically valid                     NO
           6)
  N       belongs to the user                     NO
           7)
   
Y   12  Must provide cancel                               YES   
  Y       of own articles                         YES                 8)   
  Y       *not* of others                         YES               
   
N   13  Respect line length, and post WYSIWYG
NO   
  N       line brks shown are present when posted YES
  N       do *not* post paragraph w/o line brks   YES   
  N       warn if body has lines > 80 chars       NO
              9)                      
  N       external editor conforms                N/A   
   
N   14  Prevent obvious errors
NO          
  N       prevent posting empty article           NO
  N       prevent posting only quoted text        NO

Notes to the checklist

First a short description of what the columns in this checklist stand for:

Req?:
A "Y" means that the item or subitem is a MUST for the software in order to get the Good Net-Keeping Seal Approval.
ITM ##:
This is the item number in the GNKS document : <http://www.cybe rcom.net/~rnewman/Good_Netkeeping_Seal>
Description:
Follow the above link to the original document for a more detailed description and an explanation of the rationale behind it.
Subitem OK ?: and Item OK?:
If the item is required, this is marked "YES" if all _required_ subitems are ok. If it is _not_ required, it is marked "YES" if if _all_ subitems are ok.
Notes:
These are given below:
  1. Mozilla uses the following names instead of the standard terminology:
       Standard terminology     Button text     Menu item
       ---------------------------------------------------
       Post (new message)       To: News        No menu item?
       Followup                 Re: News        Message/Reply/To Sender
       Reply (by mail)          No button       Message/Reply/To Newsgroup
    
    IMHO this is a quite good terminology which does not confuse the user. The "NO" in this item is just for strict GNKSA/U conformance. Anyway, this behaviour is not a required behaviour. On the other hand, it looks strange to me that no menu item exists for "Post a new article". The "Message/Compose Message" is for sending Mail messages (by default : this may be changed by changing the "To:" field to a "Newgroups" field in the composition window ). This is typical of the general confusion between mail and news in Netscape Message Center.
  2. I suspect a bug in the Windows 95 version. During my tests, any attempt to post a followup to a news article opened....Eudora (which is setup as MAPI server). It seems that the "Post followup" feature incorrectly makes a MAPI call. When I closed Eudora (and then its MAPI server functionnality), the "compose followup" window correctly opened.
  3. The original article is not quoted by default.The user has to click the "Quote" button for every answer. I found no option for automatic quote. Another little criticism : when the original article is quoted, one blank line should be added after the quoted text for improving readability.
  4. Only the name field, but not the email address of the quoted author is given. GNKSA/U document does not give details about the proper method for identifying the original author. I consider that it would be better to give both the real name and the email address (perhaps making this a configurable option?).,
  5. There is only a warning. When trying to send an article with an empty subject, Communicator opens a window with "This message has no subject. Send anyway?" and the answer defaulted to "Yes". I consider this enough for preventing uninformed users to send articles without subject.
  6. No check at all. Unfortunately...:-(
  7. This may be considered impossible on a single user (no real system administrator) platform.I noticed that Communicator inserts "X-Sender: Christian Perrier <bubulle@bubhome.frmug.fr.net> (Unverified)". I don't know what is the purpose of this. I may only suppose that Unix versions insert (Verified)......
  8. With Netscape 3.0, when the cancel message is sent, a window pops up for warning the user that it may not be apparent immediately. This should prevent people think that cancels do not work. Unfortunately, this disappeared in 4.0...:-(. Anyway, the cancel article feature is here.
  9. The composition window is 72 characters wide by default and leave the users the possibility of typing and sending articles with wider lines just by resizing it, if they want to do so. The software should however warn the user about Netiquette when posting with such long lines. I suggest this warning to be optional but ON by default.

This evaluation has been done by Christian Perrier