StevenJ added the comment:
The only comment I have is, if the caller needs to organise when to auth and
instigate tls then for completeness getcapabilities() should have an option to
force a reget of the current capabilities, in line with rfc3977 5.2.2:
> An NNTP client MAY cache the resu
StevenJ added the comment:
Hi Julien,
>> I also don't understand why START_TLS and AUTHINFO need to change
>> how the module is interfaced to (separating log in/authentication, etc)
> Because once you have used AUTHINFO, STARTTLS is no longer a valid
> command in a sess
StevenJ added the comment:
I too was just looking at NNTPS support because I have a need for it. The
latest patch looks like great work and I think the things it implements are
needed for this library. But it seems to me that the latest patch combines 3
things which might otherwise be able
