Agreed. This is a non-issue in 2.1 though. Please file a bug against 2.0
if you don't mind.
Brian Weaver wrote:
> I decided to take some time to check the imap specification, RFC 3501.
> In section 6.3.8 it states:
>
> An empty ("" string) reference name argument indicates that the
> mailbox name is interpreted as by SELECT. The returned mailbox
> names MUST match the supplied mailbox name pattern. A non-empty
> reference name argument is the name of a mailbox or a level of
> mailbox hierarchy, and indicates the context in which the mailbox
> name is interpreted.
>
> However when I was looking at the source file
> 'dbmail-2.0.7/imapcommands.c' lines 1405 through 1409 I noticed that a
> '.*' (match any character) pattern was being added to the mailbox
> regular expression match check regardless of the LIST reference string
> (arg[0]).
>
> If I have read and understand the specification correctly then dbmail
> is evaluating the LIST command incorrectly when the LIST reference is
> not set.
>
> -Brian
>
> P.S. here is a sample of the DBMail logging (syslog) that shows this
> in action with respect to the mutt query in the original message.
>
> Jan 4 12:40:06 localhost dbmail/imap4d[27182]: IMAPClientHandler():
> line read for PID 27182
> Jan 4 12:40:06 localhost dbmail/imap4d[27182]: COMMAND: [a0072 LIST ""
> "Lists"]
> Jan 4 12:40:06 localhost dbmail/imap4d[27182]: arg[0]: ''
> Jan 4 12:40:06 localhost dbmail/imap4d[27182]: arg[1]: 'Lists'
> Jan 4 12:40:06 localhost dbmail/imap4d[27182]: IMAPClientHandler():
> Executing command list...
> Jan 4 12:40:06 localhost dbmail/imap4d[27182]: ic_list(): build the
> pattern: [^Lists.*$]
> Jan 4 12:40:06 localhost dbmail/imap4d[27182]:
> db.c,db_list_mailboxes_by_regex: in func
>
>
> On 1/9/06, Brian Weaver <[EMAIL PROTECTED]> wrote:
>
>>Hi All,
>>
>>I've been talking with one of the Mutt developers about an issue I was
>>having using Mutt with DBMail 2.0.7. I have been using Mutt with
>>DBMail since 2.0.4 without any problems. When I upgraded to a
>>Debian/Sarge I started using a new version of Mutt and updated to
>>DBMail 2.0.7. I immediately noticed a problem using mutt's imap
>>browser. I found what I though was causing the issue within mutt and
>>fixed it so that it would work with DBMail for me.
>>
>>After talking with a mutt developer about the issue I was told that my
>>imap server (dbmail) was not processing the list command properly. I'm
>>no authority on the specification, so I'm posting the transcript of
>>mutt's conversation with dbmail 2.0.7 to ask if dbmail is properly
>>handling the LIST command.
>>
>>
>>>a0073 LIST "" "Lists"
>>
>>< * LIST () "/" "Lists"
>>< * LIST () "/" "Lists/Cryptogram"
>>< * LIST () "/" "Lists/Freshmeat"
>>< * LIST () "/" "Lists/GNessus"
>>< * LIST () "/" "Lists/LinuxFS"
>>< * LIST () "/" "Lists/LinuxKernel"
>>< * LIST () "/" "Lists/Mutt"
>>< * LIST () "/" "Lists/Oculan"
>>< * LIST () "/" "Lists/Security"
>>< * LIST () "/" "Lists/XenSource"
>>< a0073 OK LIST completed
>>
>>The mutt developer felt that the LIST command should have only sent a
>>single line response "* LIST () "/" "Lists"" and not all of the
>>children mailboxes. Is this correct?
>>
>>Thanks
>>
>>-Brian
>>
>
> _______________________________________________
> Dbmail-dev mailing list
> [email protected]
> http://twister.fastxs.net/mailman/listinfo/dbmail-dev
>
--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
