B. Johannessen
2010-Apr-10 21:09 UTC
[Dovecot] 2.0beta4 and latest Mercurial: Folder not SELECT-able until LIST-ed
Have a look at the attached dialog. It shows the folder "shared/a at db.org/Archive" not being SELECT-able until after it's been mentioned in a LIST response. This can't possibly be right, can it? Bob -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: dialog.txt URL: <http://dovecot.org/pipermail/dovecot/attachments/20100410/11c60c50/attachment-0004.txt> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: dovecot-n.txt URL: <http://dovecot.org/pipermail/dovecot/attachments/20100410/11c60c50/attachment-0005.txt>
B. Johannessen
2010-Apr-13 19:00 UTC
[Dovecot] 2.0beta4 and latest Mercurial: Folder not SELECT-able until LIST-ed
On 10/04/10 23:09, B. Johannessen wrote:> Have a look at the attached dialog. It shows the folder > "shared/a at db.org/Archive" not being SELECT-able until after it's been > mentioned in a LIST response.Timo; have you had a chance to look at this yet? Should be easy enough to reproduce, but you are welcome to test it on my test-system; just send me your SSH key... Bob
B. Johannessen
2010-Apr-16 13:38 UTC
[Dovecot] 2.0beta4 and latest Mercurial: Folder not SELECT-able until LIST-ed
On 10 April 2010 23:09, B. Johannessen <bob at db.org> wrote:> Have a look at the attached dialog. It shows the folder > "shared/a at db.org/Archive" not being SELECT-able until after it's been > mentioned in a LIST response.It's been almost a week now, and still no feedback on this. I'm obviously new to Dovecot, so I have no idea what to expect, but I consider this to be a bug in 2.0beta4. As such I would hope someone was interested in fixing it before RC1. I'm hoping to be able to deploy 2.0 (as a replacement for Courier) for ~15.000 users closely following it's release, but need to have a working server for testing. As this (suspected) bug affects one of the premier reasons we want to switch (sensible shared and public folders), I'm no longer able to continue testing... I'm trying real hard not to sound like an ungrateful git, but I would really appreciate some feedback on this... -- Regards, B. Johannessen