dovecot - Aug 2008 - proxy_maybe and IPv6

Hi,

Using dovecot 1.1.2 on a dual-stack server, with the 'proxy_maybe'
attribute to forward some clients to another server, it seems that
only clients connecting with the same protocol version as the one used
by address in the 'host' attribute in the password db are recognized as
local.

If an IPv4 address is specified as 'host', a dovecot proxy is created
for clients connecting using IPv6 to this server, and symmetrically if 
the proxy is specified as an IPv6 address, clients connecting through 
IPv4 will get forwarded to the v6 address.

Is there a way to avoid that?
-- 
Matthieu Herrb
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4051 bytes
Desc: S/MIME Cryptographic Signature
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20080811/31fda753/attachment-0002.bin>

On Aug 11, 2008, at 8:23 AM, Matthieu Herrb wrote:
> If an IPv4 address is specified as 'host', a dovecot proxy is
created
> for clients connecting using IPv6 to this server, and symmetrically  
> if the proxy is specified as an IPv6 address, clients connecting  
> through IPv4 will get forwarded to the v6 address.
>
> Is there a way to avoid that?
If you're using SQL passdb, you could probably return host as either  
IPv4 or IPv6 depending on if %l or %r is an IPv4 or IPv6 address?  
Other than that I don't really see an easy way to handle this, because  
dovecot-auth has to be the one to decide if the proxying should be  
done or not, and it doesn't know all the IP addresses the Dovecot  
installation is listening on.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20080811/b06e9f8a/attachment-0002.bin>