From: Wietse Venema (wietseporcupine.org)
Date: Mon Dec 03 2007 - 07:38:14 CST

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

Keean Schupke:
> On 03/12/2007, Wietse Venema <wietseporcupine.org> wrote:
> > 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.
>
> As the code will only work with proxywriter, should I prepend "proxy:"
> to the map name in the code, validate the string (make sure it starts
> with proxy: but not actually alter the string), or should I allow
> invalid settings in the conf file to be accepted?

I see no need to hard-code the dependency on proxied maps.
For example, the SMTP client could connect directly to *SQL
maps etc., once someone adds "update" support to those.

The single updater is required only for "local file" maps.
The documentation can give guidelines to avoid direct
access to maps that don't support multiple updaters.

        Wietse

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