Each year, GWAVA works at meeting its customers needs, especially the GroupWise community.

This year I invite you to participate in a short GWAVA customer satisfaction survey to help us become better as a company and to become better at meeting the Novell GroupWise community needs.

Here is the link to the survey:

GWAVA Customer Survey

Thank you for your support in 2008 and we look forward to a successful 2009.

On November 24, 2008, Christine Taylor wrote:
"In the court case Consolidated Aluminum v. Alco, the defendant suffered monetary sanctions for failing to properly apply litigation holds. In spite of the fact that Alco had a litigation hold policy in place, someone was asleep at the wheel. There were several serious issues: Alco issued the holds after litigation had begun, did not make the holds broad enough, and did not enforce holds when key employees deleted relevant data."

Are you using GroupWise WebAccess?
You need WASP2!

Why do you need WASP?
GroupWise WebAccess bypasses the GWIA gateway when delivering email, communicating directly with the Post Office, delivering email and their attachments into the GroupWise Post Office database. This allows unsuspecting GroupWise WebAccess users to inadvertently upload virus-infected email attachments that bypass your perimeter defense at the GWIA.

Click here to see how WASP2 works...

The following comments are from a stubbing discussion on the NGWList, a Novell GroupWise user email listserv. Charles goes into details about the issues of stubbing.

++++++++++++++++++

Simon,

It's true that the current conventional wisdom around stubbing in the
Exchange world is shifting towards only stubbing attachments (even
Microsoft is recommending it). This is not only critical from a
performance point of view, it also makes a lot sense since it's really
the attachment that consumes the space.

BTW... The initial stubbing API Novell is delivering in GroupWise 8

This is our 5th year in the US for GWAVACon and our 10th GWAVACon worldwide. The conference is still focused on Novell GroupWise but has also become a gathering place for other Novell Collaboration Solutions, including ZENworks, Novell Teaming, and now OES.

Each year the event has grown in numbers and influence. Last year, Ron Hovsepian, Novell CEO was the keynote speaker to a packed room. This year in Berlin, Volker Schmid, President of Novell EMEA was the keynote speaker.

First, what is stubbing?

The removal of a GroupWise item from the GroupWise message store that is then placed into a third party database, leaving a "stub" that appears to be the message in the GroupWise Windows Client.

The concept was developed for Microsoft because their databases were growing too large in Exchange and they need to get them smaller. Stubbing was created to move content out of the Exchange message store into something else.

The problem is now that stubbing has been out there for awhile, problems are appearing. And Microsoft is now recommending AGAINST Stubbing.

We have been speaking to many companies that run the full spectrum in size and scope, from Fortune 50 companies to SME companies with 20 employees.

It is interesting that in many instances the Legal Department or Legal advisers to these organizations like to hedge the entire archiving discussion around PIN/SMS by taking the position: "If we don't archive the data, we won't have to produce it if we are caught up in a legal action." To be more succinct: "We can't give opposing counsel something we never had."

"Andre Charland just bought an iPhone 3G, the phone from Apple (AAPL) that hit the market on July 11. But the Canadian software executive isn't giving up his BlackBerry Pearl. He says that the BlackBerry is a "workhorse" for e-mail and phone calls, while the iPhone isn't as reliable. "I’ve just had dropped calls and issues like that," says Charland. "I have the iPhone mostly for fun," like watching video or browsing the Web."

More here.