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 375633 - IMAP mailboxes can't be read that aren't in INBOX
IMAP mailboxes can't be read that aren't in INBOX
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
2.8.x (obsolete)
Other All
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-11-15 18:34 UTC by Jason Carr
Modified: 2009-09-11 04:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Jason Carr 2006-11-15 18:34:52 UTC 
Please describe the problem:
The mail server I'm using requires me to read mailboxes that are not in the normal INBOX namespace.  I've tried overriding the namespace, but it doesn't work.  If I use IMAP4rev1 style in previous versions of Evolution, it works fine, but normal IMAP doesn't work.

Example of folder names:

org.acs.xxx.yyy.zzz

Steps to reproduce:
Connect to a mail server that has mailboxes not in INBOX.

Actual results:
n/a

Expected results:
Folders should appear as normal.

Does this happen every time?
Yes

Other information:
Comment 1 Akhil Laddha 2009-07-27 13:38:36 UTC 
This version is no longer maintained, which means that it will not receive any
further security or bug fix updates.
The current stable GNOME and Evolution version is 2.26.

Can you please check again whether this issue still happens in Evolution 2.24
or 2.26 and update this report by adding a comment and changing the "Version"
field? Thanks a lot.

Again thank you for reporting this bug and we are sorry it could not be fixed
for the version you originally used here.
Comment 2 Akhil Laddha 2009-09-11 04:10:04 UTC 
Thanks for taking the time to report this bug; however, closing due to lack of
response of the reporter, sorry. if you still see this issue with a current
release of evolution (2.26.3 or later), please reopen. thanks in advance.