From: Wietse Venema (wietseporcupine.org)
Date: Mon Dec 03 2007 - 05:42:46 CST

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

Victor Duchovni:
> On Sun, Dec 02, 2007 at 10:05:09PM -0500, Wietse Venema wrote:
>
> > > So the SASL code needs to use "proxymap" protocol directly, not
> > > "proxy:..." tables, which always contacts the "real" proxymap.
> >
> > To access a single-writer auth_fail_map, use
> > proxy:btree:/some/where/auth_fail_map a dedicated proxymap service,
>
> While the delivery agent concurrency to a single destination is ideally
> just "1" in this case, the process limit for the delivery agent may
> well be significantly higher. Is it acceptable for all the smtp(8)

Use different master.cf entries for proxy read and write servers.

Use the existing proxymap service name for the read-only multiserver.

Use the new proxywrite service name for the single-updater service.

This can be completely transparent to the application:

    dict_open proxy:foo O_RDONLY -> old proxymap (multiserver)
    dict_open proxy:bar O_RDWR|O_CREAT -> new proxywrite (single updater)

I'll add a few lines of code for that today.

        Wietse

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