Dan Boresjo wrote:
Synopsis:
The %{u} macro expands to the username returned from an ident query performed
on the incoming connection.
Dan -
I find the "explanation" that followed very confusing; you state above
that the macro expands to a username, and then later that it expands to
a uid or pid, and you provide no use cases. Likewise you start off
involving identd and then appear to discard it (generally the
appropriate action for identd, I've found).
Do you expect this to be used in an exists: or a: rule, or what type?
Please give examples.
As best I understand it you expect webservers to be able to interrogate
the DNS of a submitted email address to find out whether the
REMOTE_IP/REMOTE_PORT combination of an http session is legal for a
given user? (ok, so I don't understand it, I suspect). How is this
IP/PORT combination specified or returned?
Further this appears to have absolutely nothing to do with the core
purpose of SPF, which is to validate mail-sending machines.
Unless you can clarify the above points and explain in detail the
network mechanisms that allow a meaningful expansion of your macro, I
have to oppose it on the grounds of complexity and apparent irrelevance.
It is unclear and can only confuse the purpose of SPF and hamper adoption.
Thanks,
Wechsler
-------
Sender Permitted From: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
Latest draft at http://spf.pobox.com/draft-mengwong-spf-02.9.5.txt
Wiki: http://spfwiki.infinitepenguins.net/pmwiki.php/SenderPermittedFrom/
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname(_at_)©#«Mo\¯HÝÜîU;±¤Ö¤Íµø?¡