dovecot - Jun 2008 - Multiple auth client sockets

I use two seperate Postfix instances as MSAs (so that different policies
are simpler to configure), and both of them require Dovecot SASL support.

Since Postfix' smtpd is chrooted (at least in the Debian package), the
client socket needs to be somewhere under the instance's queue_directory.
This means I need two different auth client socket paths.
When I simply specify two "client { ... }" in dovecot.conf, the second
takes precedence over the first.

Besides using a second dovecot instance, which I'd like to avoid, what ways
are there to run a second client socket?

Ulrich

On Mon, 2008-06-30 at 12:08 +0200, Ulrich Zehl wrote:
> I use two seperate Postfix instances as MSAs (so that different policies
> are simpler to configure), and both of them require Dovecot SASL support.
> 
> Since Postfix' smtpd is chrooted (at least in the Debian package), the
> client socket needs to be somewhere under the instance's
queue_directory.
> This means I need two different auth client socket paths.
> When I simply specify two "client { ... }" in dovecot.conf, the
second
> takes precedence over the first.
> 
> Besides using a second dovecot instance, which I'd like to avoid, what
ways
> are there to run a second client socket?
Create multiple socket listen {} sections.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20080720/9ec4d783/attachment-0002.bin>