[NNTP] LIST EXTENSIONS (again)

[Ken Murchison]

Mark Crispin wrote:
> 
>>> After Mark's messages, I've been convinced that we should mandate the
>>> order of the state change commands.  The correct order as near as I can
>>> tell would be:
>>>     MODE READER
>>>     STARTTLS
>>>     AUTHINFO
>>
>> If we do this, then I can add the same language to STARTTLS and 
>> AUTHINFO that I proposed for yesterday for OVER, etc.
> 
> 
> I wish that I could sign off on this, but I don't recall precisely which 
> server(s) issued a 480 to MODE READER.  I won't sign off on this unless 
> that 480 is explicitly forbidden.

If it was my Cyrus NNTP server, its a mistake.

I'll defer to others on whether forbidding 480 will work in the wild.

>>> Do we want to get into advertising whether commands are permitted for a
>>> particular client?  (POST and NEWNEWS are the ones most frequently not
>>> permitted.)
>>
>> Doesn't the 201 response signal that POST is disabled, or I'm I 
>> completely clueless?  NEWNEWS can probably just spit back 503, correct?
> 
> 
> Yes!!  There should be a POST and NEWNEWS capability, and less reliance 
> upon magic response codes.

So, you're proposing "POSTDISABLED" and "NEWNEWSDISABLED" capabilities?

-- 
Kenneth Murchison     Oceana Matrix Ltd.
Software Engineer     21 Princeton Place
716-662-8973 x26      Orchard Park, NY 14127
--PGP Public Key--    http://www.oceana.com/~ken/ksm.pgp