Bug 368517 - The KMail2 Import Wizard fails to import an export file created by KMail2
Summary: The KMail2 Import Wizard fails to import an export file created by KMail2
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: commands and actions (show other bugs)
Version: 5.1.3
Platform: Kubuntu Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-09 18:43 UTC by Jerry L Kreps
Modified: 2022-11-23 05:17 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jerry L Kreps 2016-09-09 18:43:56 UTC
Before I reinstalled Kubuntu Xenial I used the export facility in KMail to export my emails using the offered format, a zip file.  After Xenial was reinstalled I configured KMail with the exact folder structure I had originally and tested it with a few emails.  Then I used the  importwizard to import the "kmail_ emails.zip" file.  If failed to do so, complaining that it could not find a "cur" subfolder for several folders in the zip file.  Each folder failed.  Here is the pattern:
"Importing folder /transports"
"No subfolder 'cur' in folder /transports"
This pattern will repeat for the /note, /mails, /config, /data, /resources, /identities and /information folders that are present in the zip file which the exporter made.  Examining the zip file with Ark I find that it contains no subfolders named "cur".


Reproducible: Always

Steps to Reproduce:
1. Close KMail
2.  Run the KMail Import Wizard from the Xenial Utilities Menu
3.  Select the zip file
4.  It fails, every time.

Actual Results:  
No import of emails from KMail's own generated export file.

Expected Results:  
My emails to populate at least one folder.
Comment 1 Laurent Montel 2016-09-14 12:41:45 UTC
Use same program to import data.
Comment 2 Jerry L Kreps 2016-09-14 15:14:38 UTC
Doesn't matter.
When I exported my emails from WITHIN KMail  I chose a zip file as the container.
When I select the import option it told me to close KMail before importing because of possible changes by plugins.  So, I close KMAil andI select the Kmail import wizard from Kubuntu 16.04's Untilities menu.
Trying the default import option I get the response posted above.
Search for other options I notice a gzip option (but NO zip option, which is what KMail offered me as a choice).
I modified the template to read ".zip" and my zip file showed up in the directory listing.  I chose it and a status line appeared "importing from  ..." and giving the path to and including my zip file.
I let the app set for 15 minutes.  At NO time did the progress bar report any importing taking place, even though KSysMonitor showed that the import wizard was eating up 4 to 10% of CPU cycles and eventually showed 100% on all four cores.  Still no progress was shown on the progress bar.  I shut the app down.

I opened KMail back up and took the import option from its menu again and this time I closed KMail down while keeping the import GUI open.  Selecting the zip file again I got the same results.  So, using the KMail Import wizard alone or from within KMail, keeping KMail open or close, or any combination of those, the results are always the same.  Lots of CPU cycles eaten but no progress in actually importing any emails from KMail's own exported file.    Earrlier I had imported 5,200 emails from my Gmail mbox export file with no problems at all, and it went quickly.  KMail, it seems, can't eat its own dog food..
Comment 3 gerard 2016-10-01 18:52:13 UTC
Exactly the same here.
It is not very clear why I am asked to give a folder  name. I thought the folders tree reproduced the original one.
Comment 4 Justin Zobel 2022-10-24 00:46:33 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2022-11-08 05:10:44 UTC
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
mark the bug 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!
Comment 6 Bug Janitor Service 2022-11-23 05:17:13 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!