Hi Janos, hi list! I have to once more ask for help with pilerimport. I am in the process of doing the import of all existing Outlook archives. I wrote a small script to automate that. What gives me headaches now is the following error:
cannot open /some/file/extracted/by/readpst/1978.eml error importing: '/some/file/extracted/by/readpst/1978.eml' What I do is extract a pst with readpst and pilerimport -d all the extracted files. When done, the next pst is processed in that way. At some point during the import pilerimport will stop importing new messages but print the error message above for all remaining messages. I found that when I run pilerimport for several times it will (obviously) firstly skip the already imported messages and then succeed in importing some more messages before getting the errors again. So I modified my script to invoke pilerimport again and again as long as there are error lines in the output. However I am not sure if that will work for all the messages in the end. All files are owned by piler, the script and thus readpst und pilerimport are invoked by that user. The current working directory is owned by piler, too. I had a glance at the sources and found that pilerimport would output the above error messages if it could stat the message file in question but not open it reading. However I don't understand why that should be. Any help is highly appreciated. I also tried to contact you (Janos) by skype and would be happy to show you the box by teamviewer. Kindly Michael
