hello,

je recopie le passage de la RFC et le message que j'ai envoye au
newsmaser de stben

3.1 AUTHINFO

   AUTHINFO is used to inform a server about the identity of a user of

  the server.  In all cases, clients must provide this information when
  requested by the server.  Servers are not required to accept

   authentication information that is volunteered by the client.
   Clients must accommodate servers that reject any authentication
   information volunteered by the client.

   There are three forms of AUTHINFO in use.  The original version, an
   NNTP v2 revision called AUTHINFO SIMPLE and a more recent version
   which is called AUTHINFO GENERIC.

3.1.1 Original AUTHINFO

   AUTHINFO USER username
   AUTHINFO PASS password

   The original AUTHINFO is used to identify a specific entity to the
   server using a simple username/password combination.  It first
   appeared in the UNIX reference implementation.

   When authorization is required, the server will send a 480 response
   requesting authorization from the client.  The client must enter
   AUTHINFO USER followed by the username.  Once sent, the server will
   cache the username and may send a 381 response requesting the
   password associated with that username.  Should the server request
a
   password using the 381 response, the client must enter AUTHINFO
PASS
   followed by a password and the server will then check the
   authentication database to see if the username/password combination
   is valid.  If the combination is valid or if no password is
required,
   the server will return a 281 response.  The client should then
retry
   the original command to which the server responded with the 480
   response.  The command should then be processed by the server
   normally.  If the combination is not valid, the server will return
a
   502 response.

 Clients must provide authentication when requested by the server.  It
 is possible that some implementations will accept authentication
 information at the beginning of a session, but this was not the
 original intent of the specification.  If a client attempts to

c'est ce que fait FREE AGENT... et DNEWS sait gerer ca car ca c'est OK
mais remarque le "but this was not the original intent of the
specification"
qui veut dire qu'on peut demander "l'authinfo" a un autre moment ;)

 


  If a client attempts to
   reauthenticate, the server may return 482 response indicating that
   the new authentication data is rejected by the server.  The 482
code
   will also be returned when the AUTHINFO commands are not entered in
   the correct sequence (like two AUTHINFO USERs in a row, or AUTHINFO
   PASS preceding AUTHINFO USER).