Comments after upgrading to 0.107

This version works better, but I'm still getting errors on some messages that can't be saved. (See my post in the Bugs forum.)

Here are some easy things I would like to see fixed in the next release:

1) Save the log file with date/time as the filename so it's easier to go back to see what was done at each program run. The log files would also make it easier to find errors.

2) Option to only display errors/warnings while program is running. I don't want to see 10,000 files scrolling by if nothing is wrong - real problems are easily missed.

3) Option to organize messages into a directory structure. Some people have suggested doing it by using the Google labels. But I would prefer a monthly archive. Maybe name the directories /YYYYMM/. People with large mailboxes need a better way to store the files.

4) After the program finishes running display the count of e-mail messages backed up, and the number of errors. The error count in particular should be big and red so we can go back to make sure there wasn't an error with an important message that we really need backed up.

5) Display the version number on the screen. Right now I think I'm running something you call 0.107, but I can't find that anywhere in the program. Instead the top of the screen says "revision 691 (2009-02-20)." Even when I click the "New Versions" button it doesn't tell me what version I'm running.

6) Include an "About" button on the program to display version number, contact information, etc.

That's it. Thanks for this program and keep up the great work.

Oh, one last thing. Please include information on your Web site and in the program letting us know how to make a donation to support your work.

http://Rstoeber.com

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Agree!

I was about to post my own message regarding the logging and runtime output suggestions here. The suggestions here mirror my own. Better logging (total message counts, counts by folder/label, errors and successes, size of backup/restore (currently reported, but do not match between a back and restore)) and runtime output (ability to just show errors) would be very useful when attempting to validate a backup/restore procedure.

I second a paypal or google checkout account to send donations!