Bug 524485

imap_capability is not ignored, there is only one small difference. Both dovecot 1.1.x and 1.2.x return correct answer for 'A CAPABILITY' question:

A CAPABILITY
* CAPABILITY IMAP4 IMAP4rev1 ACL NAMESPACE CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT IDLE STARTTLS AUTH=PLAIN
A OK Capability completed

the only difference is initial hello message: for dovecot 1.1 it's only:
* OK Dovecot ready.

but for dovecot 1.2 it's:
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready.

so CAPABILITY information in hello message is not complete. But this message is not complete even when imap_capability is not used at all.

I'll ask upstream about capability differences in hello message and capability answer.

This is not correct
After upgrade to f11 we had some troubles
In fact this was because the wrong output

> so CAPABILITY information in hello message is not complete. 
> But this message is not complete even when imap_capability is not 
> used at all.

This is wrong abnd must be also a bug in 1.2
Version 1.1 had "login_greeting_capability = yes" which is gone away since 1.2 does this implicit, anyways 1.2 is not working as imap-proxy because it lies to the client!

I have excluded dovecot in our infrastructure from updates and made a rebuild of the f10-1.1 package (own build and repo-infrastructure) because our clients would kill me if they can not check their mails

I've asked upstream, from response:

> The capability in greeting message is short on purpose.
> It's only enough capabilities to get client logged in.
> After login Dovecot sends an updated full capability list
> to the client. It uses a few different tricks to get most
> clients understand the change.

> So the only potential problem I see here is if client
> understands the greeting capability and permanently
> remembers that the server supports LITERAL+, ID and
> ENABLE after login but the destination server actually
> doesn't.

> The other capabilities are relevant only before login.

> I'd anyway like to hear what exactly is the problem and
> with what client, preferably with IMAP traffic logs showing
> what's happening wrong.

So, could you describe your mail environment in more details?
Is it possible for you to capture imap traffic what happens when problem occurs?

thanks

Why are such simple things so complicated?
If i configure the imap_capability there is a reason to do that
There is no reason at any point of connection to make a different output

It is a bug to lie in the greeting because the sense of the greeting is for clients which do support it to reduce requests

The imap-server is dbmail which supports "IMAP4 IMAP4rev1 ACL NAMESPACE CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT IDLE" and in version 1.1 it worked fine

The problem sue is "LITERAL+" what dbmail does not support
As said the problem client was apple iphome


It makes no sense to play around which clients works in which way

Hi,

dovecot upstream has made necessary changes and dovecot now shows imap_capability in greeting message if it's set. So this should be fixed in dovecot-1.2.6-3.fc11

dovecot-1.2.6-3.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/dovecot-1.2.6-3.fc11

dovecot-1.2.6-4.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/dovecot-1.2.6-4.fc12

Confirmed - THANK YOU for your help upstream!
Apple iPhone now connects fine to dbmail behind dovecot-proxy

[harry@nb-rhsoft:~]$ telnet dbmail 143
* OK [CAPABILITY IMAP4 IMAP4rev1 ACL NAMESPACE CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT IDLE STARTTLS
AUTH=CRAM-MD5 AUTH=DIGEST-MD5 AUTH=PLAIN AUTH=LOGIN AUTH=NTLM] thelounge.net Mail-Service

Oct 22 17:31:13 mail dovecot: dovecot: Killed with signal 15 (by pid=4865 uid=0 code=kill)
Oct 22 17:31:13 Info: Dovecot v1.2.6 starting up (core dumps disabled)
Oct 22 17:31:13 auth-worker(default): Info: mysql: Connected to localhost (dbmail)
Oct 22 17:31:14 imap-login: Info: proxy(h.reindl): started proxying to 127.0.0.1:143:
user=<h.reindl>, method=CRAM-MD5, rip=10.0.0.245, lip=10.0.0.15, TLS

dovecot-1.2.6-3.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update dovecot'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-10859

dovecot-1.2.6-3.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.