All posts tagged Email Management

Last week Bloor research released a new report: Email archiving best practices- a competitive overview of the major players and if you’re thinking about buying email archiving and want to compare vendors, it’s a great resource.

The report was authored by Fran Howarth, whom I last met in April at infosec and had a great conversation with. One of the things I really liked about Fran’s perspective on email archiving is that she doesn’t just look at it from a retention or compliance only basis. Fran believes that the productivity gains from effective email archiving are just as important when selecting an email archiving vendor:

Email is of vital importance as a communications and collaboration tool as it is one of the prime ways that business information is communicated and shared. This makes its storage and archiving a necessity for maintaining and improving productivity by being able to retrieve information as it is needed. Yet operational efficiency is not the only driver for investing in email archiving technology. Owing to the amount of business information that it contains, email constitutes the leading type of evidence requested for litigation purposes and its preservation is also essential for complying with the requirements of a variety of governmental and industry regulations.

For the comparison- Fran analyses:

  • Autonomy
  • Google (Postini)
  • LiveOffice
  • Microsoft
  • Mimecast
  • Sonian
  • Symantec
Each company is analysed on:
  • Company Background
  • Current Offering
  • Strategy
  • Market Presence
  • Strengths
  • Weaknesses

It’s a really interesting report- and available to download here.

Add your comment (0)

Cloud Strategist
Mimecast

Email has evolved to be one of the most important and relied upon forms of communication and collaboration within the workplace. Unfortunately, the second email goes down, employees are often quick to either blame IT or jump to another email service during the downtime.

We polled some of our favorite IT people about their key pet peeves when it comes to email. There were lots—but the most critical ones are summarized below. Remembering these will not only help conserve IT resources, but will also ensure that you don’t end up on your IT manager’s hit list.

Peeve #1: Users copying themselves on all emails

While you may think copying yourself on every single email is being proactive, doing this quickly takes up a business’ existing storage space. This practice creates many unnecessary data redundancies, especially since many businesses have data archiving practices in place. Find out what your company’s archiving policy is and you will no longer a need to copy yourself on every single outgoing message.

Peeve #2: Emailing Company documents to personal addresses

In a recent study, we found that 79% of respondents claimed to have sent work emails to or from their personal accounts. Unfortunately, these were not sporadic instances as our respondents admitted to sending company information to personal addresses on a regular basis. Sending and receiving key business documents or messages through external sources means businesses won’t have any eDiscovery insight into those email platforms or conversations, which can become a significant legal headache down the road or create a data loss nightmare for the IT team. At all times possible, keep company information within the business.

Peeve #3: Saving every email

It goes without saying that as professionals, we are sometimes slaves to our attachments. Yet, by overusing attachments or not removing them from email messages, users quickly clog up the available space within an inbox and slow the delivery of email to other users. Additionally, in the absence of an endless inbox limit, employees have often experienced the huge frustration of a crashed inbox because it exceeded the size limit.

To avoid this pain, file only that which absolutely needs to be saved and delete the emails that are not work-related. For example, guaranteed in two weeks you won’t have a need for that email discussing the location and menu of where your team is planning a dinner.

When it doubt, refer to Justin Pirie’s thoughts on the Getting Things Done and how it can help tame the inbox monster.

Peeve #4: Not protecting mobile devices

With the introduction of tablets and more sophisticated smart-phones, today’s enterprise is more mobile and consumerized than ever. As discussed above, around 85% of business information is held within company email and with email and documents available via these devices, there is a greater chance for exposure of confidential information. Additionally, it’s inevitable that an employee will leave their mobile device, laptop or tablet in a cab, on a train, in the back seat pocket of an airplane or on the table in a coffee shop. That said, take easy security precautions, such as password protecting the device and email, to ensure business information is protected as best as possible.

Peeve #5: Ignoring the compliance risks

Our Generation Gmail research has found 36% of inbound email to work inboxes is not work related. While it can be easier for all email to be funneled into one account, personal email not only congests company storage space (see pet peeve #1), but can also be retrieved in a company compliance investigation. Additionally, certain key words within a personal email can trigger a notification to the IT team. For dignity’s sake, don’t give out your work email address to personal contacts and encourage friends and family to email your personal account only. For example, if all personal emails reside within the business, there is a risk that your boss will see how fun a friend’s bachelor party really was.

In our experience, email snafus are to be expected. While the best email policy will meet the needs for both the business and the users, there are a few ways to help an IT friend out.

Let us know if there are any other top email peeves that should be highlighted here – we would love to hear your thoughts!

Add your comment (0)

CISSP, CCSK
Mimecast, North America.

Article Tags

, ,

It’s natural and understandable that cloud computing comes under intense scrutiny, not least because it has become the de facto ‘next big thing’ to hit IT since we realised mainframes took up too much space in the living room.  Tim Weber of the BBC has wrote about the subject last Friday, talking about how Amazon’s supposedly indestructible cloud infrastructure has been brought to a crashing halt and Sony has been hit by hackers.  Questions are being asked about the claims that cloud suppliers make with regards to resilience and security, and the suggestion is that the cloud may not be all it’s cracked up to be.  Of course, it would help if we had a common definition of what cloud is, and as my colleague Justin Pirie has forcefully pointed out, Sony’s PlayStation Network (PSN) is not a cloud solution by any stretch.

But back to the way cloud is being reported, even Microsoft has not been immune to negative press, with reports of BPOS downtime depriving customers of their email.  And the debate is likely to hit fever pitch as Microsoft ramps towards the launch of its new cloud messaging platform(and successor to BPOS), Office 365.

There are two important considerations here for businesses considering deploying cloud technologies.  The first goes back to a drumbeat we’ve hammered on this blog for more than a year, and that is that companies need to do their due diligence.  We still don’t have satisfactory standards for assessing cloud technology, despite the best efforts of the Cloud Security Alliance and other bodies, which means the onus is still on the customer to find out how watertight a cloud supplier’s claims are, how verifiable its SLAs are, where and how it stores information and how easy it might be to get your data back if need be.  There are a few assurances available, such as the CESG Claims Tested Mark (CCTM), that guarantee that a cloud service does what it says on the tin.  But they are few and far between.

But the second consideration is that there are always choices available to address specific concerns IT folk might have about moving applications to the cloud.  Office 365 is a good case in point.  Although Microsoft’s shiny new cloud platform, will scale to meet the needs of businesses of all sizes, it has undoubted appeal to the small business.  Get rid of your email server and all the IT clutter that you don’t have the time, expertise or resource to manage yourself, and let Microsoft do it all.  All you need to worry about is Outlook on your laptop.  Do these companies worry about SLAs?   Will they even be perturbed by rare periods of email downtime?  Probably not.  They will buy Office 365 off the shelf, and they’ll love it.

For larger businesses, though, there is no single blueprint that captures their IT priorities.  Far from it.  Some companies will have read about the potential vulnerabilities of cloud infrastructures – not just Microsoft’s, but Amazon’s, Google’s … and they will be genuinely concerned.  Others will look through the functionality list on Office 365 and feel there are gaps there that need filling.  Perhaps it’s eDiscovery, or long-term searchable email archiving, or granular litigation hold for companies who need to be prepared for scenarios where these features are critical.  Whatever their misgivings will be, they will be equalled in numbers by those that look at the offering for what it is, understand what they will get and what the benefit to their business is and will leap happily to take up the service.

It is wrong to poke holes at BPOS, or Office 365 when it comes on stream, if it can’t be all things to all people.  It’s not designed that way.  It’s designed to be most things to most people, but for those who need extra functionality, or enhanced SLAs in certain key areas, these will be available through an ecosystem of third party suppliers that integrate with the Office 365 system.  At Mimecast we’re very excited about Office 365 for exactly this reason.  We think some people will want our enhanced archiving while others will want an additional layer of services that  ensure that there is absolutely no email downtime, particularly while they are negotiating the tricky path to the cloud.    There may not be one perfect cloud solution out there, but when you think of an ecosystem of interoperable, proven cloud technologies that work together to deliver a holistic and comprehensive service to your end users, like Microsoft Office 365 and Mimecast, you can get pretty close to perfection after all.

Add your comment (0)

Communications Director
Mimecast

With so many administrators around the world asking users to send them the message headers of any email that behaved strangely, it is a wonder that Outlook 2010 has made it far more difficult to get to them.

In this blog post, Bharat Suneja [MSFT] gives us a view on how to get back to the message headers.

Essentially the steps are:

To access message headers, you must double-click to open the message, click File to access the Backstage view and click the Properties button.

He has also highlighted a way that administrators can set up a single click access to headers using the Quick Links shortcut bar. I am not sure which I would find easier to talk a user through when I am on the other end of a mobile call and they are screaming for blood…

Either way, what this shows is that while the end user experience is improving, administrators are not being forgotten…

I have asked the team at MSFT if this quick link can be automatically rolled out and will report back here when I get a response.

Add your comment (0)

Enterprise Consultant
Mimecast

Part 0:  An Introduction

People have always asked me questions about the work I’ve done on email technology, but the most commonly asked questions have changed radically over the last thirty years.  ”What’s email?” used to be the most common by far, but I haven’t heard it in a remarkably long time.  For a few painful months in 1985, the most common question I heard was “why is email so unreliable?”   Later there was an idyllic period when what I heard most was, “how can I get all my friends and family to use email?” — for a brief period, it felt like we were changing the world entirely for the better.

Unfortunately, of course, once dotty Aunt Millie (and  my own former county treasurer) joined the net, their gullibility attracted the attention of scammers and spammers, and soon the most common question became, and for a long time remained, “why am I getting so much spam?”

Recently, however, I’ve noted a new trend, perhaps suggesting a certain maturation of the technology and its users.  Once they’ve heard enough discourses on the causes (many) and prognosis (poor) of the spam problem, most people seem to gravitate towards a deeper and better question: “Why is Email so Complicated?”

Why is Email so Complicated?

I’d venture to guess that most common cause of complexity, in a wide range of situations, is simple quantity.  Consider, for example, the telephone.  Alexander Graham Bell connected two prototypes by a single simple wire, just in time for Mr. Watson to hear his famous cry for help.   Watson would have heard nothing, however, if their devices had been separated not by a single wire, but by a complex network of wires and switches, requiring interconnection either by human operators or, later, automatic switching machines, analog to digital conversion, time slice multiplexing, and conversion of electrical signals to optical ones and back again.  At a minimum, Bell would have had to initiate a connection, and Watson would (probably) have had to accept it.  The simple idea of an audio connection between Bell and Watson inevitably became insanely complicated to support billions of humans wanting to talk.

Or consider postal mail.  The concept is simple:  ”Joe, give this letter to Bill.”  But by the time there are six billion Joes and Bills, spread all over the planet, we end up with high speed sorting machines and optical addresses readers, along with international mail tariffs and regulations and endless variations on delivery speed, confirmation, and price.

People complain about email more than these other technologies, not just because it is newer but because it doesn’t seem to work quite as smoothly, despite being almost automated.  Some of this is attributable to its success:  The zero incremental cost of an email message has pretty much eliminated pricing as a mechanism for regulating the flow.  This has brought us such obvious problems as spam and phishing, and also the more subtle problems of email overload, email-driven prioritization, and accidental over-disclosure of information by email.

Every few years, someone makes a sincere and serious-sounding attempt to redesign a simpler version of email, in the hope of solving some of these problems.  For a host of reasons, I don’t think any of them will ever work.  I think, instead, that it is time to begin to come to grips with the inherent complexity of email — most of which is equally true of other forms of informal communication on the net.

This is a complex topic, and would be hard enough to encompass in a serious and lengthy book that few people would read.  With this post, therefore, I’m initiating a series of short essays devoted to specific aspects of the complexity of modern email.   I’m going to try to cover it all if I live long enough, but if you have specific questions you’d like me to try to answer before senility sets in, I’d be happy to give it a go. For reasons I can’t even pretend to understand, I never get tired of answering questions about email!

Add your comment (4)

The Email Monster

The complexity monster

The complexity monster

Dan Tyan over at Infoworld wrote a great piece; ITs Biggest Money Wasters. Tyan poses six significant drains on your IT budget. Number four on Tyan’s list is the “Email Monster.” He sums this up perfectly;

“You already knew email was a productivity suck, but it also sucks money out of your organization in terms of storage, maintenance, software licenses, server upkeep, and the constant battle against spam, malware, and data leaks. It’s a problem that will only get worse.”

What an excellent term ‘Productivity Suck” is. It just sums up the sickness you feel at the thought of all that complexity that surrounds your email server. And let’s not forget email is actually a relatively simple concept; it’s all the demands and brouhaha the business aims at this poor little service that force IT departments to build a tangle of technology made of  various point solutions that don’t cooperate.

The email monster, or in our case the ‘Complexity Monster’, is a creature (above left) that we recently took to Dev Connections in Las Vegas where a lucky few got the opportunity to slay the beast. But the analogy of an email or complexity monster is much more powerful, and slaying that monster is comparable to the task ahead of some CIOs and IT teams who are trying to get on top of their email management infrastructure.

Looking into the eye of your monster might be a scary prospect, but there are ways around the impending doom. As everyone knows all Dragons & Monsters have a blind spot of some sort, and finding a way to exploit that in your Monster will be key.

More on the Blind Spot

I’m beginning to stretch the analogy a bit far here I know, but the idea of a blind spot is about getting to the soft underbelly of that Monster and finding a way to slay it once and for all. For example your blind spot might be compliance based, you might need to archive email but you know your storage is already creaking; simply adding more disk to the mail server isn’t going to solve the problem. So as a way of exploiting that problem (blind spot), make this a business issue; take the problem to the business, explain the risk of not retaining email correctly in light of your compliance requirement. Then importantly suggest a solution that encompasses everything that’s wrong with your email management infrastructure. Poking at one small part of the Monster with a pointy stick merely annoys it and endangers your own health.

In Tyan’s article, Gary Bahadur of KRAA Security suggests that sub 1000 user companies can gain efficiencies by outsourcing their email to the Cloud. This blog has long extolled the virtues of the Cloud and email management but I think the key point is; in order to slay your Monster you’re going to need a weapon that won’t give up on you or break halfway through the process – you essentially need a weapon that slays this thing once and for all. I think the Cloud is going to be the only sensible weapon to choose. Everything else is simply a pointy stick.

I would love to hear your heroic stories of Monster slaying… email them to monsters@mimecast.com and we’ll publish the best on this blog.

Add your comment (0)

CISSP, CCSK
Mimecast, North America.

Article Tags

, ,

Yes that’s right, Exchange 2010 for a single user deployment.

I track all sorts of data that moves across Twitter and today one of my feeds showed me a sysadmin that was out in the field and busy deploying a full Microsoft Exchange 2010 server for one single user.

A groupware server for a single user?

Luckily he was able to merge the CAS, HUB and MB roles onto a single server, at least this installation did not waste too much additional tin.

After I had rolled my tongue back into my mouth I thought about it for a little while to see what reasons I could possibly think of that would lead me to the conclusion that a fully deployed MS Exchange server would be the right solution for a single user.

I have to say I came up with nothing.

For my money this was not the right way to go though I am sure this user will never understand what all the fuss about management of complex systems is, their mailbox will be able to grow to multi gigabytes easily and still be backed up onto tape with rapid restore times. Maybe they will deploy a DAG later on so they can remove the backups from the picture? Who knows.

Surely a single user would be far better off using BPOS or EHS or any one of the myriad of hosted Exchange systems out there?
Or simply purchasing Microsoft Outlook and using that as a standalone application. Ok, so maybe activesync would be nice, remote access and the like, but that simply draws me right back to a hosted Exchange platform!

That is assuming of course that this single user actually needed any of the groupware functionality that a system like Exchange provides. Groupware… Does one single user make a group?

I would be very interested to hear your views on this one as I am still thinking about what would motivate someone to request this type of install.

Add your comment (0)

Dave is a busy email administrator, yet suddenly he seems to have a lot more time on his hands. Why? He no longer needs to worry about email archiving, email continuity and email security.

Add your comment (0)