Description of problem: Evolution does not show my system mailbox on my imap server Version-Release number of selected component (if applicable): evolution-2.6.0-1 How reproducible: Steps to Reproduce: 1. Configure an account on an imap server (details later) 2. Try to read your mail 3. Actual results: System mailbox is not displayed Expected results: System mail box should be displayed Additional info: Imap server : Fedora core 4, uw-imap-2004g-3.fc4 from Fedora Extras Folders stored in ~/Courrier on the server can be read normaly. Option "Overrife server supplied namespace" is checked, Namespace is set to "Courrier". If the option is unchecked, evolution gets a lot of data from the server (several minutes at 100Mbit/s), and then use 100% of CPU for a very long time (I always stopped it before the end...). The previous version (under Fedora Core 4), or Thunderbird works fine on thise server. My mailbox on my home access provider (imap.free.fr) is corretly accessed through Imap and evolution (UW imap also, AFAIK).
I have encountered the same problem. Previously I had no problem reading the Inbox on my mail server using IMAP with evolution 2.2.3 in FC4. I updated from FC4 to FC5 by doing a fresh install while preserving the data in my home directory. I can still read all the folders in ~/mail on my mail server, but I can't access the Inbox. The email account in question is configured with the "Override server supplied namespace" option checked and with Namespace set to "mail" (which worked before). Unchecking the override option seems not to change anything. I tried to solve the problem by configuring evolution from scratch again. I moved ~/.evolution to another directory and removed (and backed up) all of evolution's gconf keys. When I tried to set up the email account without checking the "Override server supplied namespace" option, evolution just sat there consuming 100% of the processor time but doing nothing else (no network activity). Eventually I killed it. When I selected the override option, it behaved as before: I could read the folders in ~/mail, but not the Inbox.
Same problem here. It broke on upgrade from FC4 top FC5. It currently works with Thunderbird in FC5, so I rule out server misconfiguration. My situation is similar. In FC4 I had "Show only subscribed folders" checked and had not overrided the server namespace (it worked fine since I subscribed to folders using SquirelMail, can't remeber why, but I remember doing it just once). When I upgraded to FC5, evolution would just stuck, doing nothing. Then I tried to restrict the server namespace to mail (witch is stricly correct in my setup, even though it worked without the override before). This time it worked, but the INBOX vanished, with a strage message about it already being subscribed. If anyone need more info, just ask.
I can only add a "me too" here, since the situation has already been described. I had to temporary switch to thunderbird, which seems to work all right, but I really would like to go back to Evolution sometime soon. Please let me know if I can provide additional information, but my scenario is the same than the others.
Me too. Simliar scenario described above, but the IMAP server is RHEL3U7.
There is a temporary workaround, for those who have a shell access to their mail server : on the server, create a symnlink to your system mailbox (/var/spool/mail/login_name) in your mail directory.
I'm having the same issue: FC5 x86_64 evolution 2.6.0-1 connecting to a RHL9 box running uw-imap 2001a-18.2.legacy. I did manage to use the symlink workaround to at least view mail. If you let the evolution try to process the entire contents of the folder (don't override the server namespace) you will eventually get subscribed to all the files in your home folder. I do see the INBOX when this completes though. Depending on how many files you have in your home folder and what they range from in size, it could take evolution a long time to load. Once it is loaded and you try to go and unsubscribe all folders but the ones in "~/mail", evolution will most likely crash.
Is this bug corrected with evolution-2.6.1-1.fc5.2 released today? I don't have time to test it yet :(
No, it is not.
The distribution against which this bug was reported is no longer supported, could you please reproduce this with the updated version of the currently supported distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue turns out to still be reproducible, please let us know in this bug report. If after a month's time we have not heard back from you, we will have to close this bug as INSUFFICIENT_DATA. Setting status to NEEDINFO, and awaiting information from the reporter. Thanks in advance.
For me it was fixed with an update to FC5, can't remember exactly when. I has not reappeared in FC6 or F7.