Re: [Evolution-hackers] [Fwd: Re: [evolution-patches] [PATCH] IMAP preauth and subcommand connection.]

[David Woodhouse <dwmw2 infradead org>]

On Wed, 2003-07-23 at 14:59 -0400, Anna Marie Dirks wrote:
> Hello David, Ettore, Michael and hackers:
> 
> The plan discussed here seems fairly reasonable to me; I have only a few
> simple concerns.

> Hmm. The need for a custom command isn't predicated on the ability to
> understand syntax like '$URLUSER'. (Which, btw, if you read it aloud in
> English, is a homophone for "You are loser." eek. Hardly the message we
> want our users walking away with, is it. :) 

OK. Fixed in my tree to use %h, %u etc. The environment variables are
still there too, but the default command uses 'ssh -l %u %h...'

There was an unresolved discussion about whether we should move the
option from where it is on the 'Receiving Options' page to the main
'Receiving Mail' page as part of a 'how to connect to the server', and
how... 

To restart the discussion... I agree with Anna that as it's a
fundamental connection option, it probably should be on the main page
with the SSL options. I like the idea of something like a drop-down box
as shown in http://primates.ximian.com/~anna/mailsettings/start.png with
the connection options available. (plain, ssl-if-available, ssl-only,
command).

However, I don't really like the 'Use a secure connection...' checkbox
which is required to enable it -- after all, the command might _not_ be
a secure connection, and likewise the 'SSL if available' option. 

I see Anna's point that you want to mark this option _SECURITY_ for the
na� user in (metaphoric) big letters, because "Connection Type" as I
originally suggested won't exactly scream that to them.... so how about
something like...

---------------------------------------------------------------------

  Server Type: 	< POP >
		< IMAP >
		< ... >

  Mail Server Information

	Host: _________________________
	Username: _____________________
	Path: __________________[Browse]

  Secure Connection Options

	Connect using:  < Standard insecure connection >
			< Use Secure Sockets (SSL) if possible >
			< Use Secure Sockets (SSL) always >
			< Run a command to connect >

	Command: ______________________

---------------------------------------------------------------------


(With the Command bit either greyed out or hidden completely depending
on who out of Anna and Ettore wins the fist-fight :)

It's simple, and it should scream 'security options live here' to the
user because it says 'Secure Connection Options' _and_ the default is
'Standard insecure connection'.

-- 
dwmw2