Where are the hidden options?
--
S.
Opera supports TLS (=successor of SSL):
http://en.wikipedia.org/wiki/Transport_Layer_Security
Ciao,
Christian
--
(o_ http://www.linuxbasis.org
(o< _o) (o_ //\ --------------------------
(/)_ (/)_ (/)_ V_/_ http://www.linux-drivers.org
I can appreciate that. The problem arises that many accounts have
not caught up to this fact and are content to use SSLv.3 like banks
and such. TLS is used with this account in question but only for
SMTP connections. For fetching mail SSL seems to be widely
preferred. In fact I've never seen an account that uses TLS to
fetch mail.
What's wrong with having the option?
--
S
Please note that TLS v1.0 is SSL v3.1, (or SSL v3.0 is TLS 0.9) so checking off
the TLS box also means enabling SSL. Negotiating the version supported by the
server is done automatically (most should support TLS).
Also note that secure SMTP, POP and IMAP have never been defined for SSL, but
TLS, which is obvious when you consider that the command to start encryption in
all three (when starting on the unencrypted channel) is "STARTTLS". The reason
for this is that Netscape's original name (Secure Sockets Layer) was not
accepted by the IETF as a good description of the protocol, and changed it to
"Transport Layer Security", and also that none of those specifications were (or
could be) published until after the TLS specification ahd been published.
> I can appreciate that. The problem arises that many accounts have
> not caught up to this fact and are content to use SSLv.3 like banks
> and such. TLS is used with this account in question but only for
> SMTP connections. For fetching mail SSL seems to be widely
> preferred. In fact I've never seen an account that uses TLS to
> fetch mail.
For me TLS and IMAP works perfect. But I only tried one email account
(email by the provider "1&1"). Usually I use Mutt for email.
> What's wrong with having the option?
Do you use the right "portnumber"? The right "authentication" method?
Clients like Claws-mail and Icedove [Thunderbird] still have the SSL
option that goes with the standard port numbers. Some accounts to
avoid SMTP fishing use anything they like. The 'standard' ports for
SMTP requiring SSL seem to be 465 and fetching mail seems to be 993.
It has been this way for years. Safe-mail.net and gmx.net. use these
ports. Pochtamt.ru uses port: 2525 for SMTP and TLS with name and
password for sending but port 993 and SSL for fetching mail.
The point being for safe-mail.net, gmx.net, pochtamt.ru, and he.net,
IMAP accounts will not work on Opera's configuration options. None
of them accept TLS when it comes to fetching mail. I assume they are
just slow to implement the higher standard or don't think it's
important enough to do so, but this isn't helping.
Also if you want to run a POP account on opera from the above
addresses, you would be out of luck too because you will get a
message that TLS isn't one of the services offered on the mail server.
It seems to be the usual mix of standards with not a lot of
international cooperation.
--
S.
> Thanks for that enlightening illumination regarding TLS. As far as
> port numbers I'm using, that's not the problem.
>
> Clients like Claws-mail and Icedove [Thunderbird] still have the SSL
> option that goes with the standard port numbers. Some accounts to
> avoid SMTP fishing use anything they like. The 'standard' ports for
> SMTP requiring SSL seem to be 465 and fetching mail seems to be 993.
> It has been this way for years. Safe-mail.net and gmx.net. use these
> ports. Pochtamt.ru uses port: 2525 for SMTP and TLS with name and
> password for sending but port 993 and SSL for fetching mail.
If you use any of these standard ports, Opera will automatically connect
to the host using SSL instead of using TLS with STARTTLS.
Arjan
--
Gemaakt met Opera's revolutionaire e-mailprogramma:
http://www.opera.com/mail/
--
s