[Dovecot] Dovecot 2.0b3 IDLE not advertised
Hi,
I'm not sure whether the client or the server is at fault (probably the client), but it's clearly a regression for me.
I'm using the LCG Profimail (http://lonelycatgames.com/?app=profimail) application for my Symbian smartphone which has quite decent IMAP capabilities. Amongst others it can do IMAP IDLE (which has to be statically enabled in the server settings, so it's not used based on the server capabilities).
After upgrading from 1.2.10 to 2.0b3 it does not connect anymore. It throws the error message "This server doesn't support IMAP IDLE connection" in my face, even before it tries to authenticate
Feb 27 00:46:45 mail dovecot: imap-login: Disconnected (no auth attempts): rip=93.104.73.132, lip=83.170.x.xx, TLS: Disconnected
The main difference seems to be that 1.2 advertises IDLE in capabilities before authentication, but 2.0 does not:
1.2:
- OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. o CAPABILITY
- CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC
- ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH QUOTA STARTTLS AUTH=PLAIN o OK Capability completed.
2.0:
- OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready. o CAPABILITY
- CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN AUTH=LOGIN o OK Capability completed. o LOGIN user password
- CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1
- CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS QUOTA o OK Logged in
I know there is the imap_capability setting which might help here, but that looks like a very big hammer.
Bernhard
On 2/26/2010 6:54 PM, Bernhard Schmidt wrote:
The main difference seems to be that 1.2 advertises IDLE in capabilities before authentication, but 2.0 does not:
Correct... and according to Timo, this is proper IMAP protocol, so you'd probably be better off taking this up with the Profimail devs...
--
Best regards,
Charles
On Fri, 26 Feb 2010 22:37:59 -0500 Charles Marcus CMarcus@Media-Brokers.com articulated:
On 2/26/2010 6:54 PM, Bernhard Schmidt wrote:
The main difference seems to be that 1.2 advertises IDLE in capabilities before authentication, but 2.0 does not:
Correct... and according to Timo, this is proper IMAP protocol, so you'd probably be better off taking this up with the Profimail devs...
You are probably right; however, when reading RFC2177 http://tools.ietf.org/html/rfc2177 I noticed this:
<quote> The IDLE command may be used with any IMAP4 server implementation that returns "IDLE" as one of the supported capabilities to the CAPABILITY command. </quote>
Then in RFC2060 http://tools.ietf.org/html/rfc2060
<quote> 6.1.1. CAPABILITY Command
Arguments: none
Responses: REQUIRED untagged response: CAPABILITY
Result: OK - capability completed BAD - command unknown or arguments invalid
The CAPABILITY command requests a listing of capabilities that the
server supports. The server MUST send a single untagged
CAPABILITY response with "IMAP4rev1" as one of the listed
capabilities before the (tagged) OK response. This listing of
capabilities is not dependent upon connection state or user. It
is therefore not necessary to issue a CAPABILITY command more than
once in a connection.</quote>
This is all probably incorrect since I am terrible at comprehending RFCs anyway.
-- Jerry gesbbb@yahoo.com
|::::======= |::::======= |=========== |=========== |
On Monday mornings I am dedicated to the proposition that all men are created jerks.
H. Allen Smith, "Let the Crabgrass Grow"On 27.2.2010, at 1.54, Bernhard Schmidt wrote:
The main difference seems to be that 1.2 advertises IDLE in capabilities before authentication, but 2.0 does not:
http://dovecot.org/list/dovecot/2010-February/047011.html explains this a bit better. I'll add IDLE to pre-login capabilities if I really have to, but that's probably going to be the only exception, no other post-login capabilities will be added there. And I'd prefer not to add IDLE either, because it's the best way to find clients that can't handle changing capabilities and then get them fixed.
Do you think there's any chance of getting Profimail fixed by reporting this as a bug for them? Other new servers besides Dovecot behave in a similar way.
Hi,
Do you think there's any chance of getting Profimail fixed by reporting this as a bug for them? Other new servers besides Dovecot behave in a similar way.
I'll try. They are pretty active in development, but god knows how they handle support queries. I've raised the issue with their support, I'll keep you updated.
Best Regards, Bernhard
On 27/02/2010 17:07, Timo Sirainen wrote:
On 27.2.2010, at 1.54, Bernhard Schmidt wrote:
The main difference seems to be that 1.2 advertises IDLE in capabilities before authentication, but 2.0 does not:
http://dovecot.org/list/dovecot/2010-February/047011.html explains this a bit better. I'll add IDLE to pre-login capabilities if I really have to, but that's probably going to be the only exception, no other post-login capabilities will be added there. And I'd prefer not to add IDLE either, because it's the best way to find clients that can't handle changing capabilities and then get them fixed.
Do you think there's any chance of getting Profimail fixed by reporting this as a bug for them? Other new servers besides Dovecot behave in a similar way.
I talked to Profimail previously and they were extremely helpful. In particular I requested support for the COMPRESS extension and they emailed me back a new version about 24 hours later
Suggest drop them a line in the first instance? (You could check that the COMPRESS stuff made it into the released build also since Timo kindly added support for that to 2.0)
Ed W
Ed W lists@wildgooses.com wrote:
Suggest drop them a line in the first instance? (You could check that the COMPRESS stuff made it into the released build also since Timo kindly added support for that to 2.0)
Lonelycat Games has sent me a fixed build and promised to have it incorporated into the next version. Absolutely awesome.
Bernhard
On 2010-03-01 2:56 PM, Bernhard Schmidt wrote:
Suggest drop them a line in the first instance? (You could check that the COMPRESS stuff made it into the released build also since Timo kindly added support for that to 2.0)
Lonelycat Games has sent me a fixed build and promised to have it incorporated into the next version. Absolutely awesome.
Impressive - almost as fast as Timo... ;)
--
Best regards,
Charles
On 01/03/2010 19:56, Bernhard Schmidt wrote:
Ed Wlists@wildgooses.com wrote:
Suggest drop them a line in the first instance? (You could check that the COMPRESS stuff made it into the released build also since Timo kindly added support for that to 2.0)
Lonelycat Games has sent me a fixed build and promised to have it incorporated into the next version. Absolutely awesome.
They are very good aren't they!
Anyone using supported Symbian phones should definitely give Profimail a try. It's an excellent mailreader and to be honest I would like Thunderbird to support IMAP as well as Profimail!
Good luck
Ed W
participants (5)
-
Bernhard Schmidt
-
Charles Marcus
-
Ed W
-
Jerry
-
Timo Sirainen