From: Wietse Venema (wietseporcupine.org)
Date: Sun Dec 02 2007 - 18:34:18 CST

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

Wietse Venema:
> > > Is "cache" really a good choice for a Postfix daemon name?
> >
> > The cache service is a generic cache, it is in no way tied to just
> > being used to cache auth failures. In theory any service can use it
> > for storing any data. Hence "auth_cache" represents a specific
> > application of the generic cache.
> > Another alternative might be "dict" or "dictionary" service.
>
> Postfix already has a "dict" daemon. It's called proxymap. I am
> not convinced that two "dict" daemons is desirable.
>
> If the proxymap service had a "put" operation, would that suffice?
> Adding "put" support involves less code than adding an entire daemon
> and client module to Postfix. This would require a new parameter
> proxy_write_maps that complements the existing proxy_read_maps
> feature.

The file at:

    ftp://ftp.porcupine.org/tmp/proxy_update.patch

adds update support to the proxymap protocol. I could not test the
code but if it doesn't work the necessary change should be trivial
(no time to implement postmap support for updating proxied maps).

After installing the patch, edit the mail_params.h line that
specifies the default list of writable maps here:

    #define VAR_PROXY_WRITE_MAPS "proxy_write_maps"
    #define DEF_PROXY_WRITE_MAPS "" /* Add here: "$" VAR_AUTH_FAIL_MAP */
    extern char *var_proxy_write_maps;

(instead of VAR_AUTH_FAIL_MAP specify the parameter name that you
chose).

With this, all you need is to specify

main.cf:
   auth_fail_map = proxy:btree:/some/where/auth_fail

and proxymap will do the updates for you.

        Wietse

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