Roberto Celi
Downloads: 0
Posts: 3
Smile Score: -1
About Me
I am a Free member


Visit Stats
Last Visit: 210 days ago
Member Since: 15 Sep 2008
Profile Views: 201

Roberto Celi's Posts
Average Rating from Roberto:
(2)

sort: smiles | time
burypromote
-1

Robertoc reviewed on 11 Jun 2012
Additional bug:

I restarted the importing process from scratch (I want to get a screen shot of the final error message). I also selected the "File > Export selected mailbox" menu item. A window opened and the program froze (I had to Force-quit it and restart it).
[Version 3.0]


1 Reply

burypromote
-1

-1
Robertoc replied on 11 Jun 2012
I add this as a reply to my own post, so I don't keep piling up low ratings.

The error message was: "An exception of class NilObjectException was not handled. The application must shut down".

The error occurred at a different place in the mailbox import procedure (in fact, early in the process, after about 40 minutes), and in a mailbox that had been imported correctly the first time. So, it's probably not caused by something in a specific e-mail.
burypromote
+2

Robertoc reviewed on 11 Jun 2012
Still not ready for prime time. I hope to increase the rating very shortly. I need this program.

I downloaded 3.0 and tried it on an old MBP 10.6.8 with a Eudora folder only a few months out of date. About 1GB of e-mails, 5GB of attachments, very good test for my "true" e-mail folder.

The program "had to quit" after about 12 hours of importing e-mails. Note: mailboxes were not compacted, and the "extended" import was used since many are in a foreign language, so admittedly, not ideal conditions. Long conversion time not a big deal, progress bars show what is going on.

Key problems so far:
1 - No way to gracefully stop importing. There is no "stop" button (and obviously no "restart" button following a stop). It's an "all or nothing" proposition.

2 - No way to import selected mailboxes, or for MailForge to recognize that some mailboxes have already been imported, are current, and don't need to be re-imported.

3 - No crash report. Note that the program quit, did not crash, so there was no system crash report from OS X. The error dialog box announcing that "MailForge had to quit" referred to some object that could not be found. The log file "DebugLog.txt" did not contain any useful information (the last line was the subject of the last e-mail imported).
[Version 3.0]



There are currently no troubleshooting comments by this member.

Displaying 1-2 of 2
Please login or create a new
MacUpdate Member account
to use this feature


- -