This material is copyright and is licensed for the sole use by Kliwon Klimis on 28th October 2008 425 cilce, , frood, grradt, 525254

Chapter 4

Summary

In this chapter, we covered a lot of ground. We looked at using Zimbra, and in particular the Web Client, from a user's perspective. The goal of the chapter was to help us better understand how our users will be using the system, so we could make sure we configure and maintain the system accordingly.

In this chapter, we had a look at the system requirements of our web client.

Then, we went on to see how to work with email; manage and share contacts; and manage and share calendars.

We also covered creating and sharing notebook pages, along with using the

Zimbra Assistant.

Last but not least, we discovered some of the keyboard shortcuts that

Zimbra provides.

In the next chapter, we will put our systems administrator's hat back on and look at more advanced server configurations: we'll secure Zimbra and the server it runs on.

[ 117 ]

This material is copyright and is licensed for the sole use by Kliwon Klimis on 28th October 2008 425 cilce, , frood, grradt, 525254

This material is copyright and is licensed for the sole use by Kliwon Klimis on 28th October 2008 425 cilce, , frood, grradt, 525254

Securing Zimbra

At this stage of our implementation, we have a fully operational and usable email solution. We have configured our server, created users, applied Classes of Service

(COS), and learned how to share access to calendars and address books. Now, we are at the stage where we need to consider securing our Zimbra server and our surrounding infrastructure. The assumption in this chapter is that you will be

hosting the Zimbra server, in house. However, if you will be using a hosted solution, or co-locating your server, most of this chapter still applies. To get things started, let's take a moment to look at why we need to secure our environment, and what some of the potential threats may be.

In most cases, the email server is one of only a few "internet facing" devices in your

Server Room. Along with your web server, it is assumed that the public will have access to your email server in one way or another. At the very least, other email servers need to be able to send mail to your server, and your email server needs to be able to route email out. That being the case, the email server now could be used as a means for unwanted visitors, programs, and processes into your infrastructure, if it is not properly secured.

So besides the fact that your email server could now be used as a way into your internal network from the fact that it must have ports open to allow the basic functionality of sending and receiving email, other real threats apply specifically to email. We will discuss these threats in more detail later in this chapter, but a few

examples include: SPAM, viruses, and unauthorized messages being relayed through your server. Each one of these risks may be mitigated by taking the proper steps.

This chapter will be looking at securing Zimbra through:

•Built-In Security

•Securing the Operation System

•Securing the Network