Upgrading courier-imap from 3.0.2 to 3.0.4 seems to break shared folders on courier imap. Talking directly to the imap server on 3.0.2 shows the following for LSUB 02 lsub "" "*" * LSUB (\HasNoChildren) "." "shared.Allstar.archive" * LSUB (\HasNoChildren) "." "shared.Allstar.voicemail" * LSUB (\HasNoChildren) "." "shared.Allstar.Offers" * LSUB (\HasNoChildren) "." "shared.Allstar.sales" * LSUB (\HasNoChildren) "." "shared.Allstar.fax" * LSUB (\HasNoChildren) "." "shared.Allstar.GTW" * LSUB (\HasNoChildren) "." "INBOX.villa" * LSUB (\HasNoChildren) "." "INBOX.eg" * LSUB (\HasNoChildren) "." "INBOX.asterisk" * LSUB (\HasNoChildren) "." "INBOX.spam" * LSUB (\HasNoChildren) "." "INBOX.newmedia" * LSUB (\HasNoChildren) "." "INBOX.Drafts" * LSUB (\HasNoChildren) "." "INBOX.manager" * LSUB (\HasNoChildren) "." "INBOX.sent" * LSUB (\HasNoChildren) "." "INBOX.allstar" * LSUB (\HasNoChildren) "." "INBOX.security" * LSUB (\HasNoChildren) "." "INBOX.tech" * LSUB (\HasNoChildren) "." "INBOX.Trash" * LSUB (\Noselect \HasChildren) "." "shared.Allstar" * LSUB (\Noselect \HasChildren) "." "shared" * LSUB (\Noselect \HasChildren) "." "INBOX" 02 OK LSUB completed However on 3.0.4 the "shared" folders are not listed. Reproducible: Always Steps to Reproduce: 1. Upgrade to courier-imap 3.0.4 2. Run imap client 3.
I too am experiencing this on 3.0.4... spent about four hours on this tonight before seeing this bug report...
FYI, I'm on courier-imap-3.0.4-r1
i believe this is fixed in the upstream 3.0.5 that is going into portage shortly, please test it out and re-open this bug if required.
Still seems to be broken in 3.0.5
Agreed... I upgraded to 3.0.5 and shared folders still do not function for me either.
argh. could somebody please go and talk with upstream about it? (on the courier-imap mailing list) i don't have the time to do it at the moment, but i do read the list.
Interesting... last time I spoke to developers upstream about a bug I was having, a Gentoo developer yelled at me :) I posted it on the Courier-IMAP list. I've mentioned it there before, but got a "works for me" type of answer... I tried asking again with a little more specificity.
it really depends on the nature of the bug as to how we treat it. we'd like to be more responsive ourselves, but the task of QA is a lot of work, and it's good for responsible and knowledgeable users to talk with the wider community ;-).
I had a conversation with Brian Candler back on 6/8/04... he suggested adding some lines to the source and recompiling to see where it was bombing, but I couldn't get the raw source to compile. Brian Candler wrote: > On Mon, Jun 07, 2004 at 06:47:23PM -0500, Vermyndax wrote: > >> Brian... >> >> Do you think you could point me in the direction of a good HOWTO for virtual shared folders? I Googled myself to death and couldn't find a good guide. Perhaps I'll have to try that. > > > > No, the only guide I know of (and have ever needed) is > maildir/README.sharedfolders.{txt,html}. Make sure you're using the one > within the source tarball, as someone mentioned here recently that there's > an out-of-date version on the web (but unfortunately did not provide the > URL, so it probably won't get fixed). > > >> I compared my steps to yours and still can't figure out why the shared folders aren't showing up... totally baffling. > > > > Well, if it were me, next thing I'd be doing is putting fprintf(stderr,...) > in the relevant bits to see what's happening. > > I do note the following in maildir/maildirshared.c: > > /* Prerequisited for shared folder support */ > > #if HAVE_READLINK > #if HAVE_SYMLINK > #if HAVE_DBOBJ > > #define YES_WE_CAN_DO_SHARED 1 > > #endif > #endif > #endif > > You can try replacing those three #endif's with: > > #else > #error Oops, we don't have DBOBJ > #endif > #else > #error Oops, we don't have SYMLINK > #endif > #else > #error Oops, we don't have READLINK > #endif > > which will cause the compilation to abort with a suitable message if shared > folders are not available for one of those three reasons. That's just my > guess as to the source of the problem. > > (Note for Sam: I didn't realise these conditions were in place. If sharing > is not available, I think that NAMESPACE should not advertise shared. / > #shared. - or there should be some other way to determine at configure time > or compile time that shared support was not compiled in and why) > > Brian. > > >> --JM >> >> Brian Candler wrote: >> >> >>> On Sat, Jun 05, 2004 at 11:44:28AM -0500, Vermyndax wrote: >>> >>> >>> >>>> a LOGIN vermyndax <password> >>>> a OK LOGIN Ok. >>>> a LIST "" "shared.*" >>>> a OK LIST completed >>>> >>>> Doesn't look like the server is seeing them... >>>> >>>> >>> >>> Hmm. Well I've never used filesystem shared folders myself, but here goes: >>> following the instructions in maildir/README.sharedfolders.txt I'll make a >>> new set of shared folders and add them to my main Maildir. >>> >>> $ /usr/lib/courier-imap/bin/maildirmake -S ~brian/Test >>> $ /usr/lib/courier-imap/bin/maildirmake -s write -f testfolder ~brian/Test >>> $ /usr/lib/courier-imap/bin/maildirmake --add Test=/u/home/brian/Test ~brian/Maildir >>> >>> Quick check: >>> >>> $ telnet localhost 143 >>> Trying 127.0.0.1... >>> Connected to localhost. >>> Escape character is '^]'. >>> * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP >>> ready. Copyright 1998-2004 Double Precision, Inc. See COPYING for >>> distribution information. >>> a login brian XXXXXXXX >>> a OK LOGIN Ok. >>> a list "" "shared.*" >>> * LIST (\HasNoChildren) "." "shared.Test.testfolder" >>> * LIST (\Noselect \HasChildren) "." "shared.Test" >>> a OK LIST completed >>> >>> Well, that all looks pretty simple to me. What did you do differently? >>> >>> Brian. >>> >>> P.S. A quick poke around after creating the shared folder setup: >>> >>> $ ls -lA ~brian/Test >>> total 8 >>> drwxr-xr-t 5 brian brian 512 Jun 7 12:12 .testfolder >>> drwx------ 2 brian brian 512 Jun 7 12:11 cur >>> drwx------ 2 brian brian 512 Jun 7 12:11 new >>> drwx------ 2 brian brian 512 Jun 7 12:11 tmp >>> >>> $ cat ~brian/Maildir/shared-maildirs Test /u/home/brian/Test >>> >>>
I have tried discussing this upstream in the courier-imap mailing list but my posts about it are being ignored.
I should say *now* being ignored... Brian Candler asked me to try a few things, which I did, and they didn't lead me to any conclusions. (Ran courier-imap with strace). After I did that and posted my results twice, I never heard back.
I have a feeling this is a problem with a dependency. Earlier, I was running a test server that was set for the unstable tree across the board. Shared folders did not work on any courier-imap version for me - 3.0.2, 3.0.4 or 3.0.5. I set up a server on just the stable tree (with no unstable packages) and shared folders works fine on 3.0.2.
The problem is USE=berkdb. Try this: echo "net-mail/courier-imap -berkdb" >> /etc/portage/package.use emerge -v courier-imap Please report back if that works for you.
Still no shared folders with 3.0.5
Ok, I've misspoke in last comment. I narrow it down to fam. Please replace "-berkdb" in /etc/portage/package.use with "fam". Without "fam" support, courier-imap won't be able to do shared folder (need to check this with upstream, Vermyndax, volunteer?)
Thanks that seems to have fixed it.
Just to test, I emerged 3.0.5 (stable) without +fam, and shared folders were broken. I reemerged it with +fam and the folders started working. Thanks!
If you don't mind testing, please try 3.0.7 (unstable) with -fam. I think I got a fix for it. It works on my system but I would like to have someone else test it too before I back port the fix to the stable version. Thanks.
3.0.7 with USE=-fam has shared folders working and stable for me on x86.
langthang: i'm inclined to push 3.0.7 for all arches, rather than backport fixes.
robbat2, I myself using courier-imap ever since it came out so I would say it's stable (at least on x86). As for stable on other arch, they would ask for a test procedure (lately) and I am not capable of doing that. There are too many different packages/setup involved and I don't know them all. I am only comfortable with the setup in Gentoo virtual mailhosting guide. So I'll leave to you to ask other arches stable 3.0.7.
done.
