On Wed, 9 Aug 2006, Laurent Papier wrote:

Date: Wed, 9 Aug 2006 12:38:35 +0200 From: Laurent Papier <papier@sdv.fr> To: dovecot@dovecot.org Subject: [Dovecot] IMAP/POP3 proxying and capability

Hi, I setup a rather large POP3/IMAP configuration and want to use dovecot proxying feature.

I have noted that the capability announce when connecting via the proxies are not the same before you are authenticated and after. Before you are authenticated the proxy announce is own capability and after it announce the final server capability. The problem is that some (most ? all ?) mail client ask for capability before authenticate to the server. So if the proxy capability are not the same as the final server capability the client gets wrong information.

I use the QUOTA extension and it doesn't make sens to activate the quota feature on the proxy. Any other suggestion ? Perdition can hardcode the capability string the his configuration file. This is not perfect as the capability can change but it's an acceptable workaround for me.

You _may_ find that this, ftp://ftp.csx.cam.ac.uk/pub/software/email/proxy/ will do what you want.

HTH

-- David Sheryn david@chromiq.org

Laurent Papier wrote:

I have noted that the capability announce when connecting via the proxies are not the same before you are authenticated and after. Before you are authenticated the proxy announce is own capability and after it announce the final server capability.

The problem is that dovecot can proxy you to different servers. It can't tell the capability without determining which server you'll be forwarded to, which in turn can't be done before LOGIN/AUTHENTICATE.

The problem is that some (most ? all ?) mail client ask for capability before authenticate to the server. So if the proxy capability are not the same as the final server capability the client gets wrong information.

One solution could be for the proxy code to determine the real capabilities upon login and forward them to the user via an "unsolicited reply".

Perdition can hardcode the capability string the his configuration file. This is not perfect as the capability can change but it's an acceptable workaround

That would be the way to go if you proxy to a consistent pool of servers.

HTH, -jkt

-- cd /local/pub && more beer > /dev/mouth