Description of problem: Evolution cannot pick default folders for Draft/Sent for an IMAP account. Version-Release number of selected component (if applicable): 2.24.2-1.fc10 How reproducible: Always. Steps to Reproduce: 1. Open Preferences, Accounts (select an IMAP account), Defaults. 2. Attempt to pick an IMAP folder for Draft/Sent. 3. Reverts to local folders. Actual results: Reverts to local folders. Expected results: Should pick IMAP folders, as requested. Additional info: This worked in Evo shipped with F-9. In fact, if old config is kept, it still work (i.e. messages end up in correct folders), but the GUI won't let folders be picked properly.
Can't reproduce. Seems to work fine here.
Have you tried upgrading from where you have an existing Evo IMAP account?
BTW, I just tried after cleaning my home directory of all files and directories. Upon unsuccessfully selecting Drafts/Sent folders, Evo actually crashed.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I'm seeing this too. At some point during F10 development, my sent and drafts folders got reset to the local ones instead of my imap ones on my desktop system. I didn't realize it until I went looking for a sent message and it wasn't where I expected it. I went to change it and the preferences dialog allows me to choose the new correct imap ones but once chosen, they don't get reflected in the GUI (still says Drafts instead of <account@imap>/Drafts) and when I close the preferences dialog, evo crashes. I've got two F10 systems. My desktop is broken as stated above. My laptop works fine but the Defaults tab for each of my two imap accounts don't correctly show the folders for Drafts or Sent (like above). Trying to change them also causes a crash. This is with evo 2.24.2.
Thanks for the bug report, the same issue as in the bug #474257, thus marking as a duplicate. *** This bug has been marked as a duplicate of bug 474257 ***