Groupwise native email conversion to PST

Posted on 2014-08-05
Last Modified: 2014-09-13
Good morning,

Currently working on a project where I have been asked to convert Groupwise email to PST.  However, I'm new to the whole Groupwise email process.  I've converted email in the past using Transend Migrator, but I used the Groupwise client and connected to the server while on the actual groupwise domain.  

However, I'm offsite at the lab, and have received a disk containing a series of files (of which I'm not sure is groupwise by the way).

At the top level of the directory are a series of alphanumeric named files
eg. 4d5b8c8c.006

At that level is a folder called index

Within index are a 2nd series of alphanumerically named files with the extensions of:
.inc, .idx, and .xca, .xgx, .xwn and a series of other extension with various alphnumeric names.

Is it possible the administrator copied off the entire database structure?  What am I looking at.  Am I able to access anything without credentials (which I highly doubt)? is there anything we can do with these to convert?

Any help would be appreciated.

Thank You!
Question by:WinterRanger
    LVL 19

    Accepted Solution

    the 000 ... 006 files are groupwise Archive files; They can be opened with a groupwise client, but only if you have a working groupwise infrastructure in place.

    .inc and .idx files are index files, .xca and ,xgx are temporary files created when the postoffice indexer is running, and .xwn files are work files from the novell file search index process.

    Somehow your method of migration seems  a little odd. Usually when you migrate you don't tear down the running groupwise server until migration / conversion is complete. Is there any change to get access to the running system?

    If you cannot get access you will have to build a groupwise server yourself. With a groupwise client you can then open a archive, move your mail out of the archive into your online mailbox, and with an imap client (e.g. outlook) move the mail to a different server (e.g. exchange) or pst archive.

    Here is a link to documentation for Groupwise to Exchange migration:
    LVL 18

    Expert Comment

    As deroode explains your files appear to be either an index of a personal archive created with the GroupWise client or as I would take a wild guess and suggest you've got either a remote mailbox or a caching mailbox directory.  Can you take a screen shot of the folder structure you're look at or post back the name of the top level?  If the folder name includes OFxxxARC where the xxx is a user unique FileID, you've got an archive that can only be opened with the GW client.  One vendor we work with has created a utility to directly open the archive and migrate it to PST and I'm sure there may be others.

    If you have an archive, you have to have as deroode mentions a GroupWise server infrastructure including a Post Office, POA, domain and MTA along with ConsoleOne to manage the system.  I recently completed a project for a legal issue where the customer had 10 or so old personal GW archives.  I built a GW system as mentioned on a Windows 7 Pro, including Novell eDirectory and was able to manage each of the 10 user accounts to un-archive and then open their created GW accounts with Outlook.  Once that was done, I could export to PST easily for hand-off to lawyers.


    Author Comment

    Unfortunately, we don't "easily" have access to the environment.  This is a client environment, and the client self-collected and sent us this data on a hard drive asking us to process and host for an eDiscovery matter.

    I've seen vendors advertising that they deal with Groupwise archives, but they mention a user name and password.  What credentials would I need to access this data?  End-user username and password, or a groupwise administrator account?  Or is there a vendor (highly doubtful) that has circumvented the groupwise protection?

    Thanks for the help fellas!  Your assistance has been invaluable.

    Author Comment

    To further answer your question, I, unfortunately, cannot provide a screenshot due to client confidentiality (even as obscure as this might be).  We don't have any directory structure to report other than the "Index" folder.  Everything is at the root of the drive.

    We've always done groupwise collections in the past by sending a Computer forensics team on site and collecting using the groupwise client and Transend Migrator.  However, this particular client preferred a self-collect so we're trying to troubleshoot how to handle the data.
    LVL 18

    Expert Comment

    There are two types of credentials: user/password from eDirectory (or perhaps AD) plus the user/password from GroupWise.  In all likelihood, the username is identical in the directory and in GW but the password(s) can be very different.  The only way a vendor has circumvented the GroupWise security is with a Trusted Application Key and their software would have to know how to do that.  They would have to be a Novell-developer partner in order to go there.

    If you don't know the passwords mentioned, only ConsoleOne connecting to eDirectory will allow you to change them and access the accounts in order to un-archive as I mentioned previously.  I can't ask for business here but perhaps you can see a way to contact me and we can talk briefly but keep this EE post on-going so everyone can learn.

    Author Comment

    It turns out the Paraben's Network Email Examiner allows for the conversion of these archive files without the credentials.  I appreciate the discussion.  I learned far more from this discussion that if I had stumbled across paraben first.  Thank you all for the help!

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Too many email signature changes to deal with?

    Are you constantly being asked to update your organization's email signatures? Do they take up too much of your time? Wouldn't you love to be able to manage all signatures from one central location, easily design them and deploy them quickly to users. Well, you can!

    Explanation:- SPF = Sender Policy Framework. This is basically a file that can be published with you DNS (Domain Name Service) records, These are the records on the internet that tell everyone else who is. (eg. When an email is se…
    The Microsoft Exchange server database may become damaged or corrupted due to many reasons, such as system failure. When this happens, it is usually urgent to restore the system to a stable and working state. There are different symptoms and causes …
    Familiarize people with the process of utilizing SQL Server views from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Access…
    In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…

    794 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    14 Experts available now in Live!

    Get 1:1 Help Now