Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Problem importing EML files with structure #42

Open
cleidigh opened this issue Nov 20, 2019 · 29 comments
Open

Problem importing EML files with structure #42

cleidigh opened this issue Nov 20, 2019 · 29 comments
Assignees
@cleidigh
Labels
EML import Windows Live Mail Windows 10

Comments

@cleidigh
Copy link
Collaborator

cleidigh commented Nov 20, 2019 •
edited
Loading

@cameronjpu
@cleidigh cleidigh self-assigned this Nov 20, 2019
@buggyboy
Copy link

buggyboy commented Nov 21, 2019 •
edited
Loading

I think I get same issue as reported there : #41
trying to import eml from WLM and all I get is an empty folder structure, no file at all. That's on Windows 10 x64 Home 1909, TB 68.2.2 32bits

This WLM has, in addition to a few mail accounts, a lot of local folders on several levels.
A local folder is created in TB, then menu (also tried with context menu) "Import/Export etc"/"Import all eml"/"Include subfolders" (bad translation from French)

Please let me know if I can provide other useful details.

EDIT : In the folder structure to be imported, I deleted all local storage folders, for test purposes, and now it is importing the other msgs, and that's a lot of them : 30305. I don't know if this has to do with the total number of msgs, or with local storage folders as such.

@Jerry46151
Copy link

Conversion project not going well.
Using Thunderbird 68.2.2 (32-bit) with ImportExporttools NG.

Used BitRecover PST Converter to export Office 365 Exchange to eml

The first time it created maybe a dozen folders with no emails and quit. Additional trys would do one or maybe a few folders with no emails and quit.
The folder structure look like this.
Afolder - (no eml files) sub folders have no sub folders, some sub folders are empty
CompanyA - eml files
CompanyB - eml files
CompanyC - empty
CompanyD - eml files
93 folders

@cleidigh
Copy link
Collaborator Author

@buggyboy
@Jerry46151
I do not seem to be getting notifications on their sorry for the delay.

I have done several support issues relating to this, including very large imports successfully.
So we have to figure out what's different. Keep in mind that personally do not have real experience with WLM.

Under tests I have started to create several test trees for import testing. There is a LiveMail
folder with a EML set of files. It would be good to know if you both can import that successfully.
Also either with that or your own files, capturing and posting the debug log (Shift-Control-J)
maybe helpful to catch errors.

Let me know your progress...
https://github.com/thundernest/import-export-tools-ng/blob/import-tests/tests/import.zip

@cleidigh
Copy link
Collaborator Author

@buggyboy
Can you describe what you mean by the "local folders" that you deleted?

@Jerry46151
Copy link

Jerry46151 commented Nov 24, 2019 via email

@Jerry46151
Copy link

Jerry46151 commented Nov 24, 2019 via email

@cleidigh
Copy link
Collaborator Author

@Jerry46151
Great! This is a good thing to be aware of. Was there anything that led you to do that? I can imagine some thrashing between an antivirus program and Thunderbird for processing so many files.

@buggyboy
Copy link

These 2 screenshots show what I meant when talking about "local folders", basically first level stuff in the tree that is not a mail box, the same concept exist in both TB and WLM:

This other Screenshot showsthe debug log, where, then again, the folder structure was imported but not the messages, and the log show an error message. This tests was done without an antivirus (I had deactivated all built-in Windows 10 AV, as far as I can tell) : https://drive.google.com/open?id=1mw_qopx0vNzpse3vyMZn8J2bkbNgAjXm

Importing your test import structure worked fine, 6 mails were imported.

@cleidigh
Copy link
Collaborator Author

cleidigh commented Dec 5, 2019

@buggyboy
It's not clear to me yet if by removing some of the files WLM creates did or did not solve the problem?
Also does the file structure you have to generally match my test files?
I just had someone go through updating/importing WLM files on over one thousand workstations so we are probably missing something basic.

@buggyboy
Copy link

buggyboy commented Dec 6, 2019

Yes, removing some files "solves" the problem. Well, I can do a partial import then, but I need a full import, so it is not a real valid "solution". It just shows that I can import some stuff, but not what I need.

as to the file structure, in mine there is a big mess in the "local folders", i.e. many sub-levels (it was created by a friend I'm trying to help). We might be running into file paths that are too long, for example, but I have no way to know. Or a limit on the number of sublevels? Or a limit on the total number of files?

@cleidigh
Copy link
Collaborator Author

cleidigh commented Dec 7, 2019

@buggyboy
I do not believe the extra files would be a problem, I think they should just be ignored, I may need to add some more debugging information to catch what's going on.
Regardless, it would be good to try a small subset of files.
Since you appear to have a significant import you can actually easily break that up by selecting sets of folders to keep each import to a smaller size.
I would like to eliminate the quantity as a problem and make sure we can import subsets without a problem.

@buggyboy
Copy link

buggyboy commented Dec 9, 2019

I did the following test

  • copy only the folders of the WLM folder structure into an then empty folder structure
  • then copy a sample .eml file in all empty subfolders
  • then try to import this almost empty folder structure

In TB, I then get the folder structure, but no mail imported.

I did this again, after having deleted a big chunk of the "almost empty" folder structure (the part related to local storage), and the I get test mails imported correctly.

This seems to prove that the problem is with the folder structure. Not with the number of mails, or the antivirus

@buggyboy
Copy link

buggyboy commented Dec 9, 2019

I sent you by email a copy of the folder structure, with one .eml file in each subfolder

@cleidigh
Copy link
Collaborator Author

@buggyboy
Somehow I still don't get all The Notifications, can you tell me the subject line of the e-mail because I did not see it.

@buggyboy
Copy link

buggyboy commented Dec 18, 2019 •
edited
Loading

Fwd: Re: [thundernest/import-export-tools-ng] Problem importing EML files with structure (#42)

I just resent it

edit : had sent to your github address. Resent to your gmail address

@cleidigh
Copy link
Collaborator Author

@buggyboy
Still don't see the e-mail
[email protected] ?

@cleidigh
Copy link
Collaborator Author

@buggyboy
some progress!
I finally got the old WLM to export a basic folder structure.
For the first time I got a new error referencing creating subfolders.
The end result matches yours, foldersno e-mail.
I have to look at recent changes as this was working before.
at least now I have something to go on

@buggyboy
Copy link

great, thanks for the update !

@cleidigh
Copy link
Collaborator Author

arrg
it is inconsistent
just imported the same folder structure successfully
...

@buggyboy
Copy link

did you get a chance to try with the folder structure I sent you?

@cleidigh
Copy link
Collaborator Author

@buggyboy
after more tests with your set as well as my own , I now have an isolated model that generates errors on subfolder creation. It is completely opaque to the extension , will have to pursue with the team.

@buggyboy
Copy link

thank you, please keep me updated.
What team do you mean?

@cleidigh
Copy link
Collaborator Author

I am the extension developer liaison but their core team members who know and work with the internals. I'm working to get them to take a look. I am still trying to find a workaround but no luck yet.

@cleidigh cleidigh mentioned this issue Dec 25, 2019
Closed
@cleidigh
Copy link
Collaborator Author

@buggyboy
Progress! see #57
When I have a beta will you be able to test?
Thanks
Happy Holidays!

@buggyboy
Copy link

Happy Holidays to you too !

Yes, send a beta, I will test it.

@danielehrhardt
Copy link

Something new here?

@ioneater
Copy link

fyi I run into the same problem today with a longish file path:
"C:\Users\USERNAME\AppData\Local\Microsoft\Windows Live Mail\Storage Folders (1)\XYZ\ASD\Storage Folders\Importierte 631\Lokale Ordner"
After moving all sub directories to "C:\Lokale Ordner" import worked without issues

@cleidigh
Copy link
Collaborator Author

@ioneater
This is probably an issue with the final path exceeding the Windows limit of 250 characters.
Windows live Mail appears to like long paths.
I am curious . did you look at the debug console? (Control-Shift-J)
I am in the process of finding a check for this.

@ioneater
Copy link

@cleidigh
I have no access to the original computer at the moment but reproduced the issue locally.
This is what the debug console displays after a failed import:

TypeError: msgFolder is undefined mboximport.js:1041:4
buildEMLarray chrome://mboximport/content/mboximport.js:1041
RUNimportALLasEML chrome://mboximport/content/mboximport.js:1011
importALLasEML chrome://mboximport/content/mboximport.js:1004

@slrslr slrslr mentioned this issue Oct 27, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cleidigh cleidigh

Labels
EML import Windows Live Mail Windows 10
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@danielehrhardt @buggyboy @cleidigh @ioneater @Jerry46151