[Dovecot] IMAP/POP3 proxying and capability

[Jan Kundrát]

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://dovecot.org/pipermail/dovecot/attachments/20060810/2c79e831/attachment.pgp