Re: [Evolution] evolution 2.2.2 and uw-imapd problems

[Not Zed <notzed ximian com>]

On Sun, 2005-06-26 at 14:16 -0400, M. K. wrote:
> Hi,
>
> I'm a newcomer to evolution, and I'm really impressed with what I've
> seen so far.  Unfortunately I'm having problems with IMAP subscription
> to folders on my IMAP server (checking my inbox works no problem
> though).  So I would appreciate some hints on how to fix these, so I
> can fully test out evolution.  Here are the problems I'm encountering:
>
> - is there some way to limit # of IMAP connections to a server?  I
> think UW-IMAP supports only 1 (if another connection comes in, server
> sends a "kiss of death" to any other open one); I think I was
> experiencing this a lot, especially during subscription, as errors
> about imap server timing out or something to that effect, or the IMAP
> folder scan/search proceeding indefinitely sometimes...

We only ever connect once.  So either you have anohter client running,
or it is timing out.

> - I override the imap namespace to the typical "mail/" (which should
> refer to ~me/mail/ on the server); when I'm subscribing to folders, I
> get an extra level/entry, which is all blank space, as a child of
> "mail"; I don't get this under thunderbird, and there is nothing in
> that directory that I can think of that would cause this... odd

Try without the trailing / maybe.  Not something i've seen before.

> - when I subscribe by clicking on the checkboxes for some of the
> folders, how do I get them to appear in the current mail session in the
> folder list? currently I shutdown and restart evolution to see these
> folders listed  (I have "show subscribed folders only" option on)

It should just work.  Because of that extra blank folder level, its
probably confusing the tree listing code, so fixing that should probably
clean it up.

> - once these folders do show up, they are listed twice each in the
> folder tree! is this a bug or some misconfiguration on my part?  IIRC, 
> browsing of these folders does work though...

Hmmm, you're probably subscribed to them twice somehow, but with
different path-names.  So they're not matching and it thinks they are
unique.  This is just a guess, the output of LSUB would show for
certain; I would check that.  Although the imap code has plenty of bugs
and this may be one of them, it should work fine with uw-imapd if it is
configured properly.