Version: unspecified (using KDE 4.6.0) OS: FreeBSD When running KMail for the first time the kmail-migration runs and reports success however after closing the dialog KMail does not appear. `ps -A` shows kmail-migration still running. If `killall -9 kmail-migrator` then KMail appears however all the emails are missing (existing directory structure present). NOTE: emails are still present on disk and no changes have been done to the the mailbox dirs. Running kmail after first run produces an error in kmail-migrator of "No backend for '' available." otherwise the same as above happens. Reproducible: Always In .kde4/share/apps/kmail I had: # ls -l drwx------ 5 DragonSA DragonSA 512 Oct 1 15:49 autosave drwx------ 2 DragonSA DragonSA 512 Oct 1 15:03 dimap drwx------ 2 DragonSA DragonSA 512 Oct 1 15:03 imap -rw------- 1 DragonSA DragonSA 58 Feb 17 12:57 lock lrwxr-xr-x 1 DragonSA DragonSA 32 Oct 1 15:46 mail -> ../../../../archive/kontact/mail -rw------- 1 DragonSA DragonSA 45 Jan 30 19:42 naylor.b.david@gmail.com:@pop.gmail.com:995 drwx------ 2 DragonSA DragonSA 512 Jan 19 08:12 search (NOTE: the symbolic link for the mailbox dir) kmailrc available on request.
Upon further fiddling I have discovered that the migration does work properly (although the above problems still apply). In order to get the emails loaded I need to "Check Mail" for "KMail Folders". It appears that KMail does not track any changes made to the maildir directory if those changes are made outside of KMail. It would be very convenient if kmail-migrator could "Check Mail" for local "KMail Folders". And, although it does not impact me as KMail is my only mail client, it would be nice if KMail could detect changes to the maildir. Also, somewhere through my fiddling kmail-migrator stopped popping up and stalling kmail load (I think it was when I "Check Mail" for "KMail Folders". After resolving the above problem KMail has been working well for me. Thank You.
Normal usage of KMail2 has resulting in two bugs: 1) Filters from KMail were not imported correctly. The destination folder was not imported or imported incorrectly (non existant folder). 2) I am unable to save a draft: "Unknown error (unknown collection)"
Similar here. (kde-4.6.0, kdepim-beta4). Migrating a previously (pim-4.4.10) disconnected IMAP Account. Migrator migrates, says "finished, no errors". But nothing happens. I look for running processes, and migrator and kmail seem to run. Alt-F2 -> kmail -> nothing happens. The problem was: akonadi synced and downloaded all the mails (>4GB in all Accounts, 45Kb-Connection...), but no Info about that! It is a great usability-issue, the migrator should not say "finished" and activate the close-button. Instead there should be a message "importing mails - please wait". Killing the migrator did not allow me to start kmail. I did the mistake and killed kmail, too. Started again -> migrator popped up starting migration again! Same game again -> killing migrator and kmail. Starting kmail -> migrator popped up, migrating. Went down and fortunately realised the network traffic (router blinking). Up again, i got a lot errors, saying "not able to log in to [...]". Opened the akonadi-settings - and realised, that i had three resources for each of my mail-accounts! Deleting the obsolete ones did not really help. In the end, I just removed all the configs from akonadi, kmail1 and kmail2, starting from scratch. I did not have the time to wait until all the mails got downloaded. Disabling the "offline Imap" feature, got all my mails instantaniously.
Hej, is this still reproducible with current version? A lot of work had been put into the migrator in the meantime. Ciao, Tobias
Migration now works, although I had to Ctrl-F5 to get all my emails to show. I didn't test filter migration. On an aside, I tried to setup a fresh KMail and it's automatic detection of my GMail account worked, except it tried to use IMAP while I prefer POP3
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug relates to a version of KDE that is no longer maintained. Closing.