Description of problem: I have a tree of mbox's in my ~/Mail which evo saw as old-style and tried to convert to 'new' style mail boxes. When it had done I ended up with duplicates of some mail boxes (they appeared twice in the tree -- though clicking the second entry wouldn't open the mailfolder). Additionally, it popped up an error dialog saying it couldn't convert a folder every time it hit a subdir. Finally, examination of the ~/Mail revealed a dozen *.ibex.* files for each folder had been created. Is this to be expected ? Crazy looking stuff like this.. -rw-r--r-- 1 davej davej 45206 Jul 12 21:36 Anaconda -rw-r--r-- 1 davej davej 13 Jul 12 21:41 Anaconda.cmeta -rw------- 1 davej davej 7168 Jul 12 21:37 Anaconda.ibex.index -rw------- 1 davej davej 8 Jul 12 21:37 Anaconda.ibex.index.data -rw-r--r-- 1 davej davej 13 Jul 12 21:41 Anaconda.ibex.index.data.cmeta -rw------- 1 davej davej 7168 Jul 12 21:39 Anaconda.ibex.index.data.ibex.index -rw------- 1 davej davej 8 Jul 12 21:39 Anaconda.ibex.index.data.ibex.index.data -rw-r--r-- 1 davej davej 13 Jul 12 21:41 Anaconda.ibex.index.data.ibex.index.data.cmeta -rw------- 1 davej davej 7168 Jul 12 21:39 Anaconda.ibex.index.data.ibex.index.data.ibex.index -rw------- 1 davej davej 8 Jul 12 21:39 Anaconda.ibex.index.data.ibex.index.data.ibex.index.data -rw-r--r-- 1 davej davej 13 Jul 12 21:41 Anaconda.ibex.index.data.ibex.index.data.ibex.index.data.cmeta -rw------- 1 davej davej 7168 Jul 12 21:41 Anaconda.ibex.index.data.ibex.index.data.ibex.index.data.ibex.index -rw------- 1 davej davej 8 Jul 12 21:41 Anaconda.ibex.index.data.ibex.index.data.ibex.index.data.ibex.index.data -rw-r--r-- 1 davej davej 13 Jul 12 21:41 Anaconda.ibex.index.data.ibex.index.data.ibex.index.data.ibex.index.data.cmeta -rw------- 1 davej davej 1024 Jul 12 21:41 Anaconda.ibex.index.data.ibex.index.data.ibex.index.data.ibex.index.data.ibex.index -rw------- 1 davej davej 8 Jul 12 21:41 Anaconda.ibex.index.data.ibex.index.data.ibex.index.data.ibex.index.data.ibex.index.data
Which version of evolution are you running, please?
dont have the box to hand to check, but its whatever was included in fc3 test 1.
I just reinstalled evolution with teh latest package from rawhide, and its better to a certain degree. (Ie, its almost usable now at least). 1. When it generates a list of available mailboxes, it still barfs when it finds a subdir. It pops up an error dialog "Error while updating vFolders for 'davej:/commits'. `/home/davej/RedHat/Mail/commits' is not a mailbox file.. commits is a subdir containing more mboxes. The strange thing is that it handles it correctly in the tree list widget afterwards. (It generates a correct nested folder icon). So the dialog is completely superfluous. 2. For every mbox it finds, it still generates lots of those index files. eg: SPAM@ SPAM.cmeta SPAM.ibex.index SPAM.ibex.index.data SPAM.ibex.index.data.cmeta SPAM.ibex.index.data.ibex.index SPAM.ibex.index.data.ibex.index.data SPAM.ibex.index.data.ibex.index.data.cmeta SPAM.ibex.index.data.ibex.index.data.ibex.index SPAM.ibex.index.data.ibex.index.data.ibex.index.data SPAM.ibex.index.data.ibex.index.data.ibex.index.data.cmeta SPAM.ibex.index.data.ibex.index.data.ibex.index.data.ibex.index SPAM.ibex.index.data.ibex.index.data.ibex.index.data.ibex.index.data 3. Clicking some folders in subdirs fails to open the mbox. example, I organise my bugzilla mail for kernel bugs against fc2 into a folder in Bugzilla/Fedora/2. Evolution has created metafiles for this mbox in Bugzilla.sbd/Fedora.sbd/2.[cmeta|ibex.index|ibex.index.data] Clicking the entry in the tree widget tries to open the mbox file from this location instead of where it actually lives.
Something else that puzzles me is why evo feels it still needs to index mailboxes at all if I turn off 'index message body data' on each mailbox. Does that tickbox do anything at all ? If that tickbox actually did what I think it does, and also defaulted to off instead of on, this would likely solve at least half of the problem. (leaving just the 'cant read mboxes in subdirs' problem) Shall I open a seperate bug for that ?
ooh, this all seems to have been fixed in what we have in FC3 currently. Great!