From: Luc Pardon (lucpskopos.be)
Date: Sun Oct 17 2004 - 05:02:40 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Wietse Venema wrote:
> I can also see some benefit in the ability to specify a list of
> user-controlled (name, value) pairs that get to be sent across with
> each policy service request:
>
> <policy service name>_attributes = hostname=$myhostname foo=bar
>
> But I see little benefit in a patch that adds support for a hard-coded
> hostname attribute only.
>
> Wietse

  OK, will do. Cool idea !

  The coding is (almost) done, but I have some questions before I wrap
it up.

  1) Would you mind if I left the "<policy>_myhostname" parameter in
place (in addition to "<policy>_attributes") ?

  It seems of use for any policy server that adds headers, so it might
be good to make the name of the attribute a part of the policy
delegation protocol. If not, one server will expect 'myhostname',
another 'hostname', yet another 'mailserver', ... It seems better to
cast it in stone instead of shifting the burden to the user.

  I agree that it's overlap, kind of, but then nothing stops me from
messing things really up by sticking other standard names in
_attributes.

  2a) If I leave it in, should it be 'myhostname' or simply 'hostname' ?
Since it's Postfix, the former may be more self-documenting.

  2b) If it must go, can I let <policy>_attributes default to
"[my]hostname=$myhostname" ?

  Luc Pardon
  Skopos Consulting
  Belgium

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]