> > > This appears to work. Why wouldn't 'whenever possible' work?
> >
> > 'whenever possible' only works for servers that are on the standard port
> > that support the STARTTLS extension. ie, it only attempts 1 connection.
> > 'always' will attempt up to 2 connections to find a port with SSL
> > support, either via the high ssl port (ie, server is running under
> > sslwrap) or STARTTLS.
>
> This is a UI/usability problem.
>
> The option 'whenever possible' implies that it'll use SSL if it's at all
> possible. If there's a server listening on port 993 and we don't use it
> -- that's not really expected behaviour.
>
> The options 'whenever possible' and 'ssl always' shouldn't differ in how
> they try to _find_ an SSL-capable server; they should only change the
> behaviour if we don't _find_ one.
>
> We should either change the behaviour so they match -- i.e. make the
> 'whenever possible' method check port 993 too -- or rename the options.
>
> If the latter, perhaps we can call it 'upgrade if possible' instead of
> 'whenever possible' but I prefer the former option of always trying port
> 993.
I agree. I did not quite realize what 'whenever possible' meant. After
this discussion, if my understanding is right, it seems we should be
presented with something like:
o port 143 without SSL ('never')
o port 143 with TLS ('whenever possible')
o port 993 with SSL or TLS ('always')
-Pragnesh
_______________________________________________
evolution maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution
