nntps

[Roderick]

This does nor work:

nntp-server=news.eternal-september.org:563/user=xy

Any hint?

Thanks

Rod.

[Roderick]

Post by Roderick
nntp-server=news.eternal-september.org:563/user=xy

Well, it works with

nntp-server=news.eternal-september.org:563/user=xy/ssl

but not with

nntp-server=news.eternal-september.org:563/user=xy/tls

Rod.

[J.O. Aho]

Post by Roderick
nntp-server=news.eternal-september.org:563/user=xy/tls

The server do not support tls or the ciphers it allows not supported by
your local machine (upgrade of openssl may needed).

[Eduardo Chappa]

Post by Roderick

Post by Roderick
nntp-server=news.eternal-september.org:563/user=xy

Well, it works with
nntp-server=news.eternal-september.org:563/user=xy/ssl

You do not need the port in the definition. The same would work if you
wrote

news.eternal-september.org/user=xy/ssl

Post by Roderick
but not with
nntp-server=news.eternal-september.org:563/user=xy/tls

/tls is a flag that refers to upgrading an insecure connection to a secure
connection, therefore the port specifiec should be an insecure port

news.eternal-september.org/user=xy/tls

(again, it is not necessary to specify the port). However, I highly
discourage anyone from ever using /tls, it is insecure and should never be
used if /ssl is available.

[Adam H. Kerman]

Post by Eduardo Chappa

Post by Roderick
but not with
nntp-server=news.eternal-september.org:563/user=xy/tls

/tls is a flag that refers to upgrading an insecure connection to a secure
connection, therefore the port specifiec should be an insecure port

/tls is really STARTTLS, right? It's confusing.

Post by Eduardo Chappa
news.eternal-september.org/user=xy/tls
(again, it is not necessary to specify the port). However, I highly
discourage anyone from ever using /tls, it is insecure and should never be
used if /ssl is available.

[Eduardo Chappa]

Post by Adam H. Kerman

Post by Eduardo Chappa
/tls is a flag that refers to upgrading an insecure connection to a
secure connection, therefore the port specifiec should be an insecure
port

/tls is really STARTTLS, right? It's confusing.

Yes Adam, that is correct. Alpine now supports a "/starttls" parameter
that means STARTTLS (in the sense you are talking about) and that means
the same as /tls for compatibility with the past. My expectation is that
over time /tls will stop being used, and that people will start using
/starttls as a replacement for /tls.

[Adam H. Kerman]

Post by Eduardo Chappa

Post by Adam H. Kerman

Post by Eduardo Chappa
/tls is a flag that refers to upgrading an insecure connection to a
secure connection, therefore the port specifiec should be an insecure
port

/tls is really STARTTLS, right? It's confusing.

Yes Adam, that is correct. Alpine now supports a "/starttls" parameter
that means STARTTLS (in the sense you are talking about) and that means
the same as /tls for compatibility with the past. My expectation is that
over time /tls will stop being used, and that people will start using
/starttls as a replacement for /tls.

Thanks! Making sure labels are accurate makes things less confusing for
the user.

[Eduardo Chappa]

Post by Adam H. Kerman

Post by Eduardo Chappa
Yes Adam, that is correct. Alpine now supports a "/starttls" parameter
that means STARTTLS (in the sense you are talking about) and that means
the same as /tls for compatibility with the past. My expectation is
that over time /tls will stop being used, and that people will start
using /starttls as a replacement for /tls.

Thanks! Making sure labels are accurate makes things less confusing for
the user.

I am all in agreement with you, and if you any other places in Alpine
where this kind of improvement could be made, please let me know and I
will be happy to improve Alpine this way.

[Adam H. Kerman]

Post by Eduardo Chappa

Post by Adam H. Kerman

Post by Eduardo Chappa
Yes Adam, that is correct. Alpine now supports a "/starttls" parameter
that means STARTTLS (in the sense you are talking about) and that means
the same as /tls for compatibility with the past. My expectation is
that over time /tls will stop being used, and that people will start
using /starttls as a replacement for /tls.

Thanks! Making sure labels are accurate makes things less confusing for
the user.

I am all in agreement with you, and if you any other places in Alpine
where this kind of improvement could be made, please let me know and I
will be happy to improve Alpine this way.

Thank you, Eduardo. Your committment to improve communication is in
every line of the code.