On Mon, 31 Jul 2006, Dean Brooks wrote:
>
> TF/03 Note in the spec that $authenticated_id is not set for local
> submissions from trusted users.
>
> Thing is, it doesn't appear to function as described above, and
> instead functions as the updated spec describes. That is, it seems to
> set authenticated_id even for trusted users (properly IMO) unless it
> is overridden using -oMai.
The change in the spec is consistent with the change log. I believe it is
correct. Which bit of the spec are you looking at, and what makes you
think Exim is setting $authenticated_id for trusted users?
--- doc-docbook/spec.xfpt 22 May 2006 17:43:09 -0000 1.4
+++ doc-docbook/spec.xfpt 31 May 2006 19:34:57 -0000 1.5
@@ -9901,8 +9901,8 @@
user/password authenticator configuration might preserve the user name for use
in the routers. Note that this is not the same information that is saved in
&$sender_host_authenticated$&. When a message is submitted locally (that is,
-not over a TCP connection), the value of &$authenticated_id$& is the login name
-of the calling process.
+not over a TCP connection) and if the submitter is not a trusted user,
+the value of &$authenticated_id$& is the login name of the calling process.
.vitem &$authenticated_sender$&
.cindex "sender" "authenticated"
Tony.
--
<fanf@???> <dot@???>
http://dotat.at/ ${sg{\N${sg{\
N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\
\N}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}
