[Dovecot] Strange output from LIST command
Hi,
i'm using Dovecot 2.1.7 (Debian Wheezy) and output from LIST command looks strange:
C: 4 LIST () "" (INBOX INBOX.Karantena INBOX.Spam) RETURN (STATUS (UNSEEN)) S: * LIST () "." "INBOX" S: * LIST () "." "INBOX.Karantena" S: * STATUS "INBOX.Karantena" (UNSEEN 0) S: * LIST () "." "INBOX.Spam" S: * STATUS "INBOX.Spam" (UNSEEN 0) S: 4 OK List completed.
The UNSEEN information for INBOX is completely missing. It is correct behavior? If not, is this a known bug in 2.1.7? Thank you.
azur
Quoting azurIt <azurit@pobox.sk>:
No. RFC 5819 [2]:
"For each selectable mailbox matching the list pattern and selection
options, the server MUST return an untagged LIST response followed by
an untagged STATUS response containing the information requested in
the STATUS return option."
INBOX matches the list pattern (It is explicitly contained in the
search list) and the selection options (which is empty), so the server
MUST return both a LIST response -AND- a STATUS response.
2.1.10 changelog has this cryptic entry: - imap: Various fixes to listing mailboxes.
Maybe that is what fixed things (I don't see this behavior in 2.2.6).
michael
Ok, i have this in my config:
namespace inbox { prefix = INBOX. separator = . inbox = yes list = yes }
Based on migration instructions from here: http://wiki2.dovecot.org/Migration/Courier
and here: http://wiki2.dovecot.org/Namespaces
Difference is that second page is using namespace 'inbox' and first not. I tried both and the second was working ok while first was doing problems in IMAP clients (it puts folder tree to different location than it was with Courier).
The problem with LIST command disappears when i comment out line "prefix = INBOX.". Any hints? Thank you.
azur
Here's the complete IMAP communication, see the (1) only: http://bugs.horde.org/view.php?actionID=view_file&type=log&file=imap-ok.log&...
I also find out that it's working ok when i LIST the INBOX alone like this: C: 4 LIST () "" (INBOX) RETURN (STATUS (UNSEEN)) S: * LIST () "." "INBOX" S: * STATUS "INBOX" (UNSEEN 2) S: 4 OK List completed.
The information about UNSEEN messages is correct. It's only doing problems when listing multiple folders at once.
azur
On Thu, Oct 17, 2013, at 09:21 PM, azurIt wrote:
Yeah, that definitely looks like a bug! I've CC'd Timo to grab his attention :)
Hey Timo, it works right in Cyrus :p
. list () "" (INBOX INBOX.Trash INBOX.Archive) RETURN (STATUS (UNSEEN))
- LIST (\HasChildren) "." INBOX
- STATUS INBOX (UNSEEN 0)
- LIST (\Trash) "." INBOX.Trash
- STATUS INBOX.Trash (UNSEEN 0)
- LIST (\HasChildren \Archive) "." INBOX.Archive
- STATUS INBOX.Archive (UNSEEN 0) . OK Completed (0.010 secs 113 calls)
(I have specialusealways configured, doesn't seem to break anyone)
Bron.
-- Bron Gondwana brong@fastmail.fm
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 21.10.2013 22:11, schrieb azurIt:
2.1.7 is out of date update to 2.1.17 or 2.2.6 and try again
Best Regards MfG Robert Schetterer
[*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSZab9AAoJEP8jBObu0LlEr60IAJR4REJ+cgdgCE10Z4iouHC/ mOHqAgbhzS7ZctzL/BQxurO92jjSFV2dcUCp+eijg6VPPBUy7wrQTP6QCCCJO481 CJhDKjzMMCWi7z7H2xEYjKU0J6P9wo+uCGZAk0R7GcaJiRzEv6u7nRtwsks6lROV krvZOOkGMBGpMa2leHDxgVHGjLtmMPZgSGgvusTlxTw1iVhRdYk8gvW+cm9g3WbH bEHF87lP0LO9aab4HcrtuM4U7hllhvDV05f3aCF5+qhA4ZDSNr0SKGg/Q4DUYLP4 sD2cbdvyJ1P/UdwqI0BLBnmUp2cdmeLxJskkSZENS8TOhPeW18KfFd0m3w+soeQ= =jSY1 -----END PGP SIGNATURE-----
As i already said, i tried 2.1.17 and problem persists: http://dovecot.2317879.n4.nabble.com/Strange-output-from-LIST-command-tp4481...
azur
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 24 Oct 2013, azurIt wrote:
Timo monitors this list well. So maybe:
a) he is occupied with paid work or vacation, b) you've sent in no patch, c) this bug is not fatal in order to have him kick in immediately.
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux)
iQEVAwUBUmkjfF3r2wJMiz2NAQJbUwf8DK0tFdw8zrcSv3B4727jdgCboGcO7AXx jkfCIxesoRyi1BNpOVZI9am6wijvvHXMMZrztc0NO9bRrg9Ld+Ww+Caza8Rmn5KL WIPtuZlMVc1G8FkFEO0fz7ReTZC9c5fbcH1XtrmcR3uUNYn0WdQyHGyWZqqFixYE U/skSSbuupfUNinotS3h4lqWV8QTptt9OtlIzQpDrYeB1ssFCRnIkzM18a0dFBmS YIO0sWteUouUVh7M3xLkUvV5tbTKCYRCxeJO/dd574tnrxV5Xvlqy+uDHbciq/Ba 8uZaJ3m/2fdx1nuTbONY72+unZLD/c9b0+UO27zKRBpi9FuOgCadnw== =6hap -----END PGP SIGNATURE-----
On 25/10/2013 17:20, azurIt wrote:
of course it is, you report an alleged bug, now you wait until developer notes, and attempts to reproduce it, and if he can commits a fix, else he will tell you he can not reproduce it.
I do see your point about needing confirmation the report was made, its why we use bugzilla, it would be beneficial if Timo did as well, but he chooses not to, he did give a reason for this, but it was many many years ago when he had more free time, now his time is scarce, one day he may reconsider it, so in meantime you need to wait it out, hence, patience. Dovecot does have a commercial side as Steffen alluded to, so if your bug is debilitating your business, you could always engage the commercial side of Dovecot, the fix which obviously is not affecting the masses, would likely gain priority.
On Thu, Oct 24, 2013 at 03:48:27PM +0200, azurIt wrote:
Again: take Steffen's word for it. Timo monitors this list well. Sometime's he's busy. If it's worth it to you, contact his company and sponsor a fix. Otherwise, wait.
Sometimes Timo gets behind on replies here, but he goes back and answers every significant thread. He will reply.[1]
[1] Offer void where taxed or prohibited, or if, God forbid, he got hit by a bus.
http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
Quoting Bron Gondwana <brong@fastmail.fm>:
Except as I read 5819, this is completely irrelevant. LIST-STATUS !=
STATUS. LIST-STATUS produces STATUS-like responses, but isn't
controlled by any of the rules of the original STATUS. At least
that's how I interpret it.
Looking at the rest of this thread, I think we are all in agreement
that something is fishy. As OP reported, it appears to be something
specific with personal namespaces (possibly 'INBOX.' only).
michael
On Thu, Oct 17, 2013, at 11:46 PM, Michael M Slusarz wrote:
Yeah, that may be - except at least in Cyrus they share quite a lot of common code. Probably in Dovecot as well. Such things are a fertile ground for bugs, particularly in IMAP with all the ugly special case corners that exceptions create over time. I wish "SELECTED" was less special in a bunch of ways.
Yep, definitely looks fishy!
Bron.
-- Bron Gondwana brong@fastmail.fm
On 14.10.2013, at 21.28, azurIt <azurit@pobox.sk> wrote:
Fixed: http://hg.dovecot.org/dovecot-2.1/rev/d16e212531ec
It was also already working for v2.2.
participants (9)
-
/dev/rob0
-
azurIt
-
Benny Pedersen
-
Bron Gondwana
-
Michael M Slusarz
-
Noel Butler
-
Robert Schetterer
-
Steffen Kaiser
-
Timo Sirainen