>Вот именно в эту. И вместо информации о предназначении server_set_id, как и
>в каких случаях его надо заполнять, а когда он не нужен,
>а также о том, как пристегнуть к авторизации имеющиеся хешированные пароли
>из /etc/shadow, вижу, сами понимаете, фигу. Эх-эх...
server_set_id Use: authenticators Type: string* Default: unset
When an Exim server successfully authenticates a client, this string is
expanded using data from the authentication, and preserved for any
incoming messages in the variable $authenticated_id. It is also included
in the log lines for incoming messages. For example, a user/password
authenticator configuration might preserve the user name that was used to
authenticate, and refer to it subsequently during delivery of the message.
If expansion fails, the option is ignored.
что касается shadow:
pam {<string1>:<string2>:...}
"Pluggable Authentication Modules"
(http://www.kernel.org/pub/linux/libs/pam/) are a facility which is avail-
able in the latest releases of Solaris and in some GNU/Linux distributions.
The Exim support, which is intended for use in conjunction with the SMTP
AUTH command, is available only if Exim is compiled with
SUPPORT_PAM=yes
in Local/Makefile. You probably need to add -lpam to EXTRALIBS, and in some
releases of GNU/Linux -ldl is also needed.
....
${hash{<string1>}{<string2>}{<string3>}}
This is a textual hashing function, and was the first to be implemented in
early versions of Exim. In current releases, there are other hashing
functions (numeric, MD5, and SHA-1), which are described below.
etc...
