Mailstore Home Review

[Carri Seargent]

CloudNine Discovery Portal is the gateway to uploading, processing and reviewing your data in CloudNine Review. Follow these simple steps and your data will be available in CloudNine Review in no time.

When you launch CloudNine Discovery Portal you are presented with several workflows. If you have raw (unprocessed) eDiscovery data or processed data with corresponding load files, the File System - CloudNine Review workflow is used.

After launching CloudNine Discovery Portal, connecting to CloudNine Review, and choosing the data upload type, Native/Raw Data, the next screen is Upload to CloudNine Review: Case Selection and Custodian. On this screen, you will select an existing CloudNine Review case (project), and enter a Custodian name to upload the data. A new CloudNine Review case (project) can also be created here.

Now that you are familiar with the Upload to CloudNine Review screen, you can proceed with entering a Custodian name and selecting the Case the data will be loaded to.

The Pre-Upload Filtering screen gives you the option to inventory your data and gain insight into the data before actually uploading it. Once inventoried, you are able to cull data by folders, file type, specific files, or date range to exclude data from processing and uploading to CloudNine Review.

? Use the Pre-Upload Filtering to obtain preliminary reports about the data. This information can be useful to determine priority order based on folder/directory structure and if any pre-upload exclusions (culling) may be implemented based on file type or date range filtering.

Pre-Upload Filtering is an option available to you but is not necessary. If you are familiar with your data and do not wish to exclude anything bypass inventory and filtering and proceed to the final step.

The Pre-Upload Filtering feature in CloudNine Discovery Portal allows you to take an inventory of your data, and if desired cull (exclude) data based on folders/directories, file type, individual files, and date range filters. Filtering is run before the upload process begins. Any files meeting the exclusion criteria are omitted from upload and processing into CloudNine Review.

If at anytime the information appears to be inaccurate, or you decide you want to stop the inventory process click the Cancel Selection button on the bottom right to cancel the inventory progress. If you choose to cancel, you are returned to the initial Pre-Upload Filtering screen. At this time, you can go Back to select/remove data or simply choose a different inventory option. When the inventory process completes, the Pre-Upload Filtering Inventory Results screen appears.

Once the file inventory process completes, the Pre-Upload Filtering screen displays the results. At this time you can review the data and determine if you want to Cull (exclude) any data prior to uploading. There are three tabs on the Pre-Upload Filtering Screen:

? Want to start reviewing sooner? Consider uploading in "batches" by including/excluding specific folders based on size or priority. For example, if the directory is organized by custodians then you can prioritize which custodian to import first.

The File Type column provides a list of all top-level file types identified during inventory. Here you can choose to exclude an entire file type or individual files. This feature is often used to exclude executable files and common system files.

The following Filetypes are Not filterable (as shown in the Filtered Count/Size column). By default, these file types are included. You can manually deselect to remove from upload.

The Mailstore tab gives you the opportunity to review PST files found within your data set. On this tab, you will see a list of PSTs, the number of messages, and the total file size. When you expand the top mailstore folder you can see the folder organization of the mailstore.

Your data has been inventoried and you have gained insight into the data you will be uploading to CloudNine Review. Filter options are applied based on the scope of your project. Click Next to proceed to Step 5: Confirm & Upload.

The Global Monitor Screen is used to monitor the upload progress through CloudNine Discovery Portal. Once data is uploaded to CloudNine servers the status on the Global Monitoring Console will reflect that the upload is complete and the processing to CloudNine Review phase begins. You will receive status emails during processing, with a final email advising your data is ready in CloudNine Review. Click Global Monitor Console for additional information about the console.

I haven't tested the new version (I've seen it on another machine and didn't like it) but my existing system runs around 15 email accounts, all nicely segregated and visitble. I don't want something that looks like Outlook on Android.

Well, I certainly do. With IMAP your client only 'reflects' the data that is on the server. Sounds OK...until that email server decides to change their terms of service. Say, only keeping old emails for 2 to 3 years or so, or even change / lower the storage space limits.

Make a copy at the folder level for all the mail, and, if it's an Exchange account, do the same for contacts and calendars from your active Outlook file. If you do it today, you will have some 2024 entries that you could then manually remove them, or leave 'em.

If you want, you can delete those emails (I wouldn't delete the contacts or calendar), and if you don't change anything else, that .pst will be opened every time you open Outlook, and they will be searchable.

If you have Outlook connected to those accounts on multiple computers, I would first make sure the item counts for each look right (sometimes sync isn't 100% the same among systems), then close Outlook, copy the .pst file to another computer, and open the file from within Outlook on that machine.

"I don't see why you can't archive IMAP mail to a local folder/mailbox and then it doesn't matter who deletes the original mail or when it happens." - That would be a PST file, though, wouldn't it? Which is also not supported (er, "yet")

Theoretically IMAP can be used like POP; the actual protocol is a functional superset. However, nobody implements it that way. Outlook and Thunderbird treat it as a synchronized viewport on a corporate mail server, so the mail lives on the server and maybe you have a local copy. That doesn't work with ISPs. Nor with Yahoo, which now limits IMAP to seeing only the newest 10,000 messages, even though others can be seen via their webmail.

And for backups and archives you shouldn't rely on a single point of failure anyway. Set up journaling rules (auto-forwarding to an archive) or a similar method to store incoming and outgoing emails on a different server. There are better ways to achieve your goals here, because anything you do with POP3, you can do with IMAP too, with the added benefit of having an extra safeguard where emails remain on the server if things go wrong somehow.

It doesn't have to as POP3 has no hand in this -- it's down to settings on your email client, which either does or does not send a delete command after retrieving the email. It's perfectly possible to retrieve over POP3 and still leave all emails on the server if your email client allows this.

I concur. I use IMAP on all my household devices except for one PC where I use POP3 to get local copies of all email. I have it set to not delete emails that are pulled down, but do delete emails off the server if I move emails to Trash on the POP3 client. This way I can manage my email without having to access my ISP's terrible web-based email interface.

Can you not get local copies with IMAP? My email clients use IMAP, and Kmail, certainly, has the option to keep local copies. It also has various synchronisation options so email sent from any device ends up in the server's Sent folder and email deleted on the server can, or can not, also delete the local copy. It's been a while since I used Thunderbird but I think it had similar facilities.

Local copies once made my wife in to a bit of an IT star, when a group she was involved with held a committee meeting at a venue with no WiFi and no mobile coverage. None of her colleagues could access the emailed minutes or agenda or other notes whereas Kmail had everything locally.

I do this too and already use Thunderbird to pull all email using POP3, leaving them on the servers. Deletes go through if deleted from Thunderbird. I then use FairEmail on phones / tablets, accessing using IMAP, but only keeping a month or so of email on the devices. It means I can manage newest stuff easily via IMAP, but I know I'm capturing all of them on my main server. I too am old, so Belt, braces and shoelaces. This setup works for me, but everyone needs to find what works for them.

And when that IMAP supplier goes bankrupt or puts up the bills? You have to pay or move everything... IMAP can still disappear. Only difference is now the user doesn't realise that deleting that email from his phone also destroyed his desktop copies... Don't blame the protocol for bad email habits.

A different reason for the same conclusion: I don't want any work documents on my personal devices. Ever. Nor am I willing to give corporate IT any control over my personal devices, which is what I'd have to do if I wanted to have work materials on them.

And THAT'S the huge issue. If you change providers (change ISP, for example), you lose your emails, don't you? With IMAP, unless you make a local repository and manually copy all your emails to those folders, you lose your emails, correct? If you downloaded with POP3 it is already done, or if you wish to sync with a POP3 client it is a single operation rather than manually selecting and copying possibly thousands of emails.

c80f0f1006