On Thu, 8 Jul 2004, Daniel Miller wrote:
>I'm curious if this is a Mozilla Thunderbird issue or a bincimap problem.
>Thanks for your help

Neither of the above; Binc IMAP is configured for Maildir++, which doesn't
allow root level folders. You need to use IMAPdir to get root level
mailboxes. The protocol dump doesn't demonstrate deleting of any sublevel
mailboxes. Are you sure this is the problem?

>Debugging info:
>write(1, "13 OK CLOSE completed\r\n", 23) = -1 EPIPE (Broken pipe)
>--- SIGPIPE (Broken pipe) @ 0 (0) ---
>Process 26721 detached

This should be handled better by Binc IMAP.. The client closed the
connection immediately after sending LOGOUT, and Binc IMAP should accept
this.

>Protocol Dump:
>* OK Welcome to Binc IMAP Copyright (C) 2002-2004 Andreas Aardal Hanssen
>at 2004-07-08 09:24:42 MDT
>1 capability
>* CAPABILITY IMAP4rev1 STARTTLS AUTH=LOGIN AUTH=PLAIN
>1 OK CAPABILITY completed
>2 authenticate plain
>+
>AHRoaXNpc2l0AHRoaXNpc2l0
>2 OK AUTHENTICATE completed
>3 lsub "" "*"
>* LSUB (\Unmarked) "/" "INBOX"
>3 OK LSUB completed
>4 list "" "INBOX"
>* LIST (\Unmarked) "/" "INBOX"
>4 OK LIST completed
>5 list "" "Trash"
>5 OK LIST completed
>6 create "Trash"
>6 NO CREATE failed: invalid mailbox name

Binc doesn't accept Trash, because it's not a child of INBOX. This is
proper Maildir++ behavior.

>7 select "INBOX"
>* 0 EXISTS
>* 0 RECENT
>* OK [UIDVALIDITY 1089300286]
>* OK [UIDNEXT 1] 1 is the next UID
>* FLAGS (\Answered \Flagged \Deleted \Recent \Seen \Draft)
>* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)] Limited
>7 OK SELECT completed
>8 create "RootLevelFolder"
>8 NO CREATE failed: invalid mailbox name

Same as above.

>9 create "INBOX/InboxLevelFolder"
>9 OK CREATE completed

Good, that's more like it!

>10 subscribe "INBOX/InboxLevelFolder"
>10 OK SUBSCRIBE completed
>11 list "" "INBOX/InboxLevelFolder"
>* LIST (\Unmarked) "/" "INBOX/InboxLevelFolder"
>11 OK LIST completed
>12 expunge
>12 OK EXPUNGE completed
>13 close
>14 logout
>* BYE The server died unexpectedly. Please contact your system
>administrator for more information.

This error is caused by the SIGPIPE, not by any mailbox behavior.
This dump doesn't show any errors.. In particular it doesn't list any
attempts to delete a folder. (?)

>It seems that binc and Thunderbird disagree on what the root level is.
>When the 'InboxLevelFolder' was created it was done as
>~/Maildir/.InboxLevelFolder instead of
>~/Maildir/INBOX.InboxLevelFolder.   Step 1 fails because binc can't go

The first is Maildir++, and it means INBOX/InboxLevelFolder. The next is
IMAPdir, and it means the same.

>any higher in the directory tree then ~/Maildir/.  Step 3 seems to fail

True, Binc IMAP stores all mailboxes of any IMAP level in the Maildir
directory, the depot. It doesn't use UNIX folders to represent IMAP
folders.

>because it trys to move the 'InboxLevelFolder' folder into the 'Trash'
>folder which doesn't exist because binc was unable to create the 'Trash'
>folder for the same reason that Step 1 fails.  One thing interesting to
>note is that if I try to create a 'Trash' folder myself in Mozilla
>Thunderbird I get an error that says the folder already exists and I
>need to pick a different name.  This may show that Mozilla Thunderbird
>thinks the 'Trash' folder exists at the root level.
>The protocol dump shows the communication on the creation of the 'Trash'
>folder as: 6 create "Trash" 6 NO CREATE failed: invalid mailbox name.
>This situation means that no folders or messages can be deleted no
>matter where they are in the directory structure because there is no
>'Trash' folder to put them in.

Right, Thunderbird needs to be set up to use INBOX/Trash if you're using
Maildir++.

>Is this conclusion totally off?  If it is correct how can I change
>things so that Thunderbird will create ~/Maildir/.Trash and think of it
>as being at the root level?

Well, that won't work. .Trash is not a root level folder - it's a Maidir++
representation of INBOX/Trash. If you want root level folders, you need to
use IMAPdir.

>I was also curious about the protocol dump.  The instructions on the
>wiki say to wipe out the username and password, but I couldn't find my
>username and password in the dump file.  Did I perform the protocol dump
>incorrectly, or have things changed with binc to where this is no longer
>a requirement?

They're base64 encoded after AUTHENTICATE.... :-)

Andy

--
Andreas Aardal Hanssen   | http://www.andreas.hanssen.name/gpg
Author of Binc IMAP      |  "It is better not to do something
http://www.bincimap.org/ |        than to do it poorly."

Reply via email to