After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 546704 - Unable to 'see' IMAP folders at same level of hierarchy as INBOX
Unable to 'see' IMAP folders at same level of hierarchy as INBOX
Status: RESOLVED DUPLICATE of bug 428631
Product: evolution
Classification: Applications
Component: Mailer
2.22.x (obsolete)
Other All
: Normal minor
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-08-07 01:59 UTC by calie
Modified: 2012-02-14 10:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description calie 2008-08-07 01:59:27 UTC
Please describe the problem:
I'm connecting to my email server using IMAP.  The structure of my mailboxes is as follows:
  inbox
  sent-mail
  draft
  trash
  spam
  archive---->work
          |-->school
          |-->home

In Folders-->Subscriptions..., the only choice is 'inbox' and I am therefore unable to subscribe to any of the other mailboxes.

Steps to reproduce:
1. Create mailboxes at same level in hierarchy as inbox on server.
2. Folders-->Subscriptions...


Actual results:
Only 'inbox' appears in folder list.

Expected results:
All of the folders that are being exported on the mailserver should appear.

Does this happen every time?
Yes.

Other information:
I enabled logging (export CAMEL_VERBOSE_DEBUG=1) and, after launching evolution from the terminal (evolution --debug=evo.log &) I observed the following:

sending : A00002 NAMESPACE
received: * NAMESPACE (("mail/" "/")("" "/")) NIL NIL
received: A00002 OK Namespace completed.
sending : A00003 LIST "" INBOX
received: * LIST (\HasNoChildren) "/" "INBOX"
received: A00003 OK List completed.

After reading RFC 3501 and RFC 2342, it's not apparent to me why A00003 has "INBOX" as the mailbox name.  It appears that it's assuming a certain directory structure when it should be able to query the server for that information instead.
Comment 1 André Klapper 2012-02-14 10:56:33 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 428631 ***