On Wed, Sep 06, 2000 at 12:39:45PM +0100, Philip Hazel wrote:
>
> > The documentation on server_prompts is a bit sparse. Do you think you
> > could elaborate on how it works, since implementing AUTH LOGIN using
> > this option seems like the most sensible approach to take at this point.
>
> Well, I wonder what more I need to say than is in the manual:
>
> The data sent with the AUTH command or in response to subsequent prompts is
> encoded in base 64, and so may contain any byte values when decoded. If any
> data was supplied with the command, it is treated as a list of NUL-separated
> strings which are placed in the expansion variables $1, $2, etc. If there are
> more strings in server_prompts than the number of strings supplied with the
> AUTH command, the remaining prompts are used to obtain more data. Each
> response from the client may be a list of NUL-separated strings.
I was looking at the documentation for the server_prompts option itself,
which doesn't make this quite as clear.
> So, for PLAIN authentication, where the data all comes with the AUTH
> command, you don't set server_prompts at all, but for LOGIN
> authentication, where there are two prompts for two pieces of data, you
> set server_prompts to two strings (colon separated) as in the example.
> If you were to set
>
> public_name = PLAIN
> server_prompts = p1 : p2 : p3
Is what is put between the colons at all significant? Or do they just
serve as placeholders / labels for the prompts?
On a slightly related note, is there an easy way to get exim to dump its
compile time options?
Thanks,
Christi
--
Christi Scarborough, Systems Administrator, FutureTV
http://www.futuretv.com/
FutureTV Labs Ltd, Brunswick House, 61-69 Newmarket Rd, Cambridge, CB5 8EG, UK
Tel: +44 (0)1223 576100 (switchboard) +44 (0)1223 478660 (direct line)
