Home > MailSaver > MailSaver Still Collecting Feedback

MailSaver Still Collecting Feedback

I’ve still not had enough testing feedback on MailSaver, so I’m going to wait a bit longer before I publish release 4. I’d like to have some more and varied users test it and let me know how it works for them. Our in-house tests have been fairly good but I still want more feedback.

Hopefully next week I’ll release v4.0.

About these ads
Categories: MailSaver
  1. Jimmy Smith
    2006-05-24 at 15:10

    Downloaded the mailsaver 4, but was not able to save any of the emails. No error shown up, but was able to look into the logs. I was able to save the log of the error. do you need me to send you the log?

  2. 2006-05-24 at 15:22

    Please do send me the log file. Thanks.

  3. 2006-05-26 at 08:47

    how can i become a tester ? download the beta from sourceforge ? will do if i can.

  4. 2006-05-26 at 09:32

    You can get the beta at Novell Forge.

  5. 2006-09-28 at 14:59

    Great add on to Groupwise–Thanks. We are using it with Groupwise 5.5SP5 have not had luck using it with proxy but works ok when logged into normal mail box. Any way to turn off the four-digit hex “unique ID” code being added to the attachment file name? Also, c:\program files\MailSaver\mailsaver.hlp is missing when you click help on configure mailsaver.

  6. 2006-09-28 at 15:35

    Oops, I guess I forgot to build in the help file when I built the beta release. I’ll make sure it gets added when I finally post 4.0.

  7. Fritz
    2007-05-15 at 01:12

    Thank you very much for this great tool. I’ve tested version 4.0beta3 and it works so fine but i have also some suggestion for improvemenrt: The possibility to read and export mails and attachments also from the Groupwise Archive similar to the mailbox functions.

  8. Alistair
    2007-08-17 at 12:09

    The program is very helpful, but there are some things that we would like fixed and improved, namely:

    1. Help file. Promised, but not delivered

    2. Official release of version 4. Promised over a year ago, but not delivered.

    3. When you click “Save All to Project Folder” (or similar), the “Browse for Folder” window typically does not show up on the top of your desktop so the user does not know it is there and is waiting for something to happen.

    4. User has no indication of what the current “Project Folder” is.

    5. If the user decides the change the project folder (new project folder), he has no indication of whether or not the change has been made.

    6. “Syncronizing Changes to Online” takes forever. And personally, I do not see a need for it. Is there a way to turn off this feature?

    7. If the user accidently “mailsaved” a folder to the wrong location, there is no way to tell where the folder was saved. If the user changes the folder to the correct save location and then tries to save again, it will not work since the program thinks the messages have already been saved. Also, there is no way to save it in to the new location unless he remembers to “mark the messages as unsaved” first. But it may be helpful if there was some indication that certain folders were “mailsaved” already.

    8. If the user NEEDS existing “mailsaved” files to be overwritten, then it would be helpful to have a promt letting the user know that he is about to overwrite a file and to confirm.

    9. “MailSaver Completed” also does not always show up on the top of the desktop. Users typically do not know that it has completed.

    10. It would be very helpful if we could save single messages or selected messages to a specific destination instead of “by folder.”

    11. It would be very helpful if we could save nested folders to a specific destination.

    We hope that you will include some or all of these suggestions in your official release. Thank you very much!

  9. Alistair
    2007-08-17 at 15:12

    In addition to the previous items above, sometimes we want to “mailsave” our data in two locations – say onto the local hard drive or flash drive and also on a network location. But because there is no way to prevent the program from remembering the last location data was stored, users must first follow the steps outlined in item 7 above.

  10. ed
    2007-10-19 at 07:50

    The program (Ver 3) blows up and stops when encounterring Chinese characters – any wayto have it skip over these characters/ignore them/ and just keepp on running?

  11. 2007-10-26 at 15:05

    I’ve never done any work in that direction. I wouldn’t know where to begin. I’ll try next time I get the mailsaver development environment out, but right now my schedule is pretty full.

  12. ed
    2007-10-29 at 14:44

    The Chinese characters are in the Unicode range of 4E00 –>9FFF
    (There is a chart of all unicode ranges avail on the net).
    The ides is to skip any characters rather than blow the program up halfway through an extract using your program. My guess is to prompt for the character range to exclude and then do a string comparison on the strsubject and clean it out. I’ll try playing with it as well since we need it right away. Any oer suggetsions?
    efalkow@aol.com

  13. Kat
    2008-05-02 at 14:50

    Can’t get it to work at all…

    Here is the error I get when trying to save All to the Collection

    Save Messages and Attachments from
    GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Object API\GroupWise Objec
    to G:\Email
    crc16(123456789)=BB3D
    crc16(hello world)=39C1
    crc16(Hello world)=F96A
    crc16(a)=E8C1
    crc16( )=D801
    Error Executing GWCommand: 2
    Err Number: -2147352567
    Description: An invalid argument was passed in the function call.

    We’re using GW7.0 on XP pcs and others have been able to get this to work slicker than snot, but any computer I install it on only gets the “invalid argument” error….whether I’m saving to the collection or to project folders

  14. Steve Marsh
    2008-06-10 at 07:57

    We are running GW 7.0.2. Have had pretty good results with MailSaver so far. I am puzzled as to why the recipient (TO:) is frequently not reported in the output text file.

    It appears that when a full email address (example JSmith@thiscompany.com) is used when addressing a message, rather than an address book entry (John Smith) that knows the individuals email address, that the output MailSaver file will not list the recipient. All other information is placed in the file. Please let me know about workarounds or fixes. Thank you.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: