If your network has only one Exchange server, deploying PureMessage for Microsoft Exchange is straightforward: install PureMessage for Microsoft Exchange on the Exchange server and conﬁgure it according to your email security policy.

2.2 Deploying PureMessage for Microsoft

Exchange to multiple Exchange servers

PureMessage for Microsoft Exchange can protect both front-end (hub transport) servers and backend (mailbox) servers.

If you don't want to expose your mailbox servers directly to the internet, you can use an Edge

Transport server in your perimeter network. The Edge Transport server role is available in Microsoft

Exchange Server 2013 Service Pack 1 (SP1) or later.

Note

In such hybrid environments, it is recommended that you perform anti-spam scanning on the edge server to ﬁlter spam, and install the anti-virus only version of PureMessage for Microsoft

Exchange on your back-end servers that do not require anti-spam scanning.

Example: Separate Exchange Edge Transport server and Exchange

Mailbox server

This example illustrates how PureMessage for Microsoft Exchange can be installed on several

Exchange servers with dedicated roles.

Note

Install the appropriate version of PureMessage for Microsoft Exchange on each server. For

PureMessage for Microsoft Exchange system requirements, see knowledgebase article 118640 .

PureMessage for Microsoft Exchange 2013 and 2016

Figure 1: Separate Exchange Edge Transport server and Exchange Mailbox server

PureMessage for Microsoft Exchange 2013 and 2016

3 Installing PureMessage for Microsoft

Exchange

This section describes how to install PureMessage for Microsoft Exchange.

Note

If you are installing PureMessage for Microsoft Exchange to an Exchange cluster, check the system requirements and then go to

Appendix A: Deploying PureMessage for Microsoft

Exchange clusters (page 27).

PureMessage for Microsoft Exchange consists of two components:

• The PureMessage for Microsoft Exchange service.

• The PureMessage for Microsoft Exchange administration console.

This section tells you how to install both on a single server and also how to install a separate administration console in order to manage remote PureMessage for Microsoft Exchange servers.

Installation involves the following steps:

• Checking the system requirements.

• Preparing for installation.

• Preconﬁguring updates (Sophos Enterprise Console customers only).

• Installing PureMessage for Microsoft Exchange.

• Installing a PureMessage for Microsoft Exchange console on a separate computer (optional).

3.1 System requirements

PureMessage for Microsoft Exchange 4.0.4 and later can be installed on Microsoft Exchange Server

2013 and 2016. The minimum requirement for the database is Microsoft SQL Server 2008.

For a full list of PureMessage system requirements, see knowledge base article 118640

3.2 Preparing for installation

Note

If you are running Windows 2008 or Windows 2008 R2 Server, read http://www.sophos.com/ support/knowledgebase/article/109664.html

before installing PureMessage for Microsoft

Exchange.

Before you begin installation, you should do the following:

• Read the PureMessage for Microsoft Exchange release notes for details of new features and known issues. The release notes are published at http://www.sophos.com/en-us/support/ documentation/puremessage-for-microsoft-exchange.aspx

• Make sure that a backup has been made of the mailboxes and databases.

PureMessage for Microsoft Exchange 2013 and 2016

• Make sure that the Exchange Autodiscover service is conﬁgured correctly. The service is used by

PureMessage for Microsoft Exchange during scanning of Exchange stores. For more information, see http://www.sophos.com/en-us/support/knowledgebase/119506.aspx

• PureMessage for Microsoft Exchange installation may require a restart, so schedule the installation for a time when restarting the server will cause the least inconvenience.

If you want to use spam blocking:

• Make sure that you have a valid anti-spam license and download credentials from Sophos so that you can download anti-spam updates.

• Make sure that PureMessage for Microsoft Exchange is installed on a computer with Internet access, as anti-spam updates are only available direct from Sophos.

• If you use Sophos Enterprise Console to protect your PureMessage for Microsoft Exchange server, make sure that the server is conﬁgured to download anti-spam updates directly from

Sophos as described in

Preconﬁguring updates

(page 5).

If you are installing PureMessage for Microsoft Exchange on multiple servers, make sure that your

SQL server is set up for remote access. See the PureMessage for Microsoft Exchange release notes for further details.

3.3 Preconﬁguring updates

If you use PureMessage for Microsoft Exchange for spam blocking, it needs to update regularly with the latest rules for detecting spam. These spam rules can only be downloaded directly from

Sophos via the internet.

If you are going to install PureMessage for Microsoft Exchange on a computer that does not already have Sophos Anti-Virus installed, updating will be set up for you and you need take no further action. Go to

Installing PureMessage for Microsoft Exchange (page 6).

If you are going to install PureMessage for Microsoft Exchange on a computer already running

Sophos Anti-Virus and managed by Sophos Enterprise Console, you must follow the instructions below.

Note

You will need the username and password that you use for downloads from the Sophos website.

1. Go to the computer running Sophos Enterprise Console and start Sophos Enterprise Console.

2. Ensure that the computer(s) running PureMessage for Microsoft Exchange are in a group of their own or have their own policy setting.

3. Create an Updating policy (or edit the existing policy) for the group.

4. In the Updating Policy dialog box, click the Secondary server tab.

5. In the Secondary server dialog box, select Specify secondary server details . Then in the

Address ﬁeld, click the drop-down arrow and select Sophos . Enter your username and password.

6. If necessary, enter proxy details.

You have preconﬁgured updating and are ready to install PureMessage for Microsoft Exchange.

PureMessage for Microsoft Exchange 2013 and 2016

3.4 Installing PureMessage for Microsoft

Exchange

To install PureMessage for Microsoft Exchange, do as follows:

Note

The following services (and any dependent services) may be stopped and started during the installation of PureMessage for Microsoft Exchange:

• Internet Information Services (IIS)

• Microsoft Exchange Transport service

• Microsoft Exchange Frontend Transport service

• Microsoft Exchange Information Store service

• Distributed File System Replication (DFSR) service

1. Log on to the server as an administrator, based on your environment:

• If you are in a domain, log on with domain administrative privileges.

• If you are in a workgroup, log on with local administrative privileges.

Note

Make sure you are a member of the Exchange Organization Management group.

2. Visit the Sophos product download page at http://www.sophos.com/support/updates/ . You will need credentials to download products and documentation.

3. Browse to the PureMessage for Microsoft Exchange page and download the PureMessage for

Microsoft Exchange for Microsoft Exchange installer package you require. Choose Anti-virus and anti-spam or Anti-virus only (as your license permits).

4. Using Windows Explorer, browse to your download folder and start the installer package. The installation wizard begins.

Note

Ensure that the installer is not run from a network share.

5. In the Welcome dialog box, click Next .

6. In the License Agreement dialog box, read the agreement. If you agree with the terms, click I accept the terms of the license agreement and click Next .

7. In the Select Features dialog box, select the components you want to install and click Next .

8. In the Choose Destination Location dialog box, you see the default folder where PureMessage for Microsoft Exchange will be installed. If you want to install it in a different folder, click Browse and select a folder. Click Next .

9. In the Sophos Download Credentials dialog box, enter the User name and Password that were supplied by Sophos.

If you access the internet via a proxy, click Proxy Details and enter your proxy settings.

Otherwise, click Next .

PureMessage for Microsoft Exchange 2013 and 2016

10. In the PureMessage Database settings dialog box, specify the database (SQL Server) where

PureMessage for Microsoft Exchange will store reporting data, central quarantine, and policy conﬁguration information. Click Next .

PureMessage for Microsoft Exchange will automatically detect any local SQL database instances. If a local database instance is detected, you choose it by selecting the Local option.

If no database is detected and Local is chosen, then PureMessage for Microsoft Exchange will install a local instance of SQL Server Express. To use a database instance located on a different computer, choose the Remote option. The database Browse dialog displays only SQL Server instances with the current domain.

Note

For information on how to conﬁgure database mirroring, see

Appendix F: Database Mirroring

(page 37).

Note

PureMessage for Microsoft Exchange 4.0.4 and later supports TLS 1.2. Using TLS to connect to a SQL Server database requires server side changes, see knowledge base article 132092 .

11. In the PureMessage Service Credentials dialog box, click Create and enter a password and conﬁrm it to create a SophosPureMessage user. If the user account already exists, you will be prompted to enter its password. This account is used by Sophos PureMessage services. Click

Next .

12. In the PureMessage Conﬁguration Group dialog box, select a group you want to join or create a new group. Click Next .

PureMessage for Microsoft Exchange installations can be grouped together to share the same policy conﬁguration and be managed from a single management console. For more information, see

PureMessage for Microsoft Exchange Conﬁguration Group

(page 9).

13. If you are installing PureMessage for Microsoft Exchange on an Exchange server that is conﬁgured as a mailbox-only role, the PureMessage Mailbox Role Settings dialog box is displayed. Select the Exchange transport server which PureMessage for Microsoft Exchange should use to send alert email messages. Click Next .

14. In the PureMessage Administration Settings dialog box, enter an Administrator email address.

PureMessage for Microsoft Exchange will send alerts to this email address. You can change this address later too. Click Next .

Note

PureMessage for Microsoft Exchange creates a security group in Active Directory called

Sophos PureMessage Administrators, which includes all PureMessage for Microsoft

Exchange administrators. By default, the current user will be added to this group.

15. In the PureMessage Routing settings dialog box, do as follows.

a) Enter your company’s email domain(s), such as mycompany.com, in the top panel.

Note

You need not specify sub-domains. When you specify a domain, the sub-domains are included automatically.

b) Enter the IP addresses of any trusted email relays, such as your ISP’s SMTP server and any email gateway server or appliance upstream of your Exchange servers. Click Next .

PureMessage for Microsoft Exchange 2013 and 2016

Note

PureMessage for Microsoft Exchange uses the upstream relays conﬁguration to determine mail direction. Not conﬁguring an upstream relay can cause PureMessage for Microsoft

Exchange to classify mail from upstream relays as internal, and hence skip spam scanning

for those messages. For information on conﬁguring upstream (trusted) relays, see Appendix

B: How to conﬁgure upstream (trusted) relays (page 30).

16. In the Company Information dialog box you can enter details relating to the size, location, and market sector of your company or organization. This valuable feedback helps SophosLabs analyze email security trends. Click Next .

17. In the Start Copying Files dialog box, ensure the settings are correct. If they are not, use the back button to return to previous dialog boxes and change the settings. When they are correct, click Next .

18. PureMessage for Microsoft Exchange displays the installation progress and installs Sophos

Anti-Virus and Sophos AutoUpdate (if not already installed). Sophos AutoUpdate automatically downloads updates to virus data and anti-spam rules.

Note

In certain circumstances the installation may require you to restart the server. The installation will continue after restarting.

19. When installation is complete, the InstallShield Wizard Complete dialog box is displayed. Click

Finish .

If you also want to install a separate PureMessage for Microsoft Exchange administration console,

see Installing a PureMessage for Microsoft Exchange console on a separate computer

(page 8).

Note

If you have Microsoft Exchange server installed on your network, you may need to disable or exclude ﬁles from scanning. For more information see knowledge base article 40065 .

To start using PureMessage for Microsoft Exchange, see Getting started with PureMessage for

Microsoft Exchange (page 11).

3.5 Installing a PureMessage for Microsoft

Exchange console on a separate computer

The PureMessage for Microsoft Exchange administration console can be installed on a computer without the PureMessage for Microsoft Exchange service in order to manage remote PureMessage for Microsoft Exchange services.

To install PureMessage for Microsoft Exchange console onto a separate computer:

1. On the computer where you want to install the console, start the PureMessage for Microsoft

Exchange installer.

2. In the Welcome dialog box, click Next .

3. In the License Agreement dialog box, click I accept if you agree to the terms.

4. In the Select Features dialog box, clear the PureMessage Service check box and leave the

Administration Console check box selected. Click Next .

PureMessage for Microsoft Exchange 2013 and 2016

5. In the Choose Destination Location dialog box, select your preferred destination folder, and click

Next .

6. When installing in a workgroup, the PureMessage Service Credentials dialog box will appear.

Click Create and enter a password and conﬁrm it to create a SophosPureMessage user. If the user account already exists, you will be prompted to enter its password. This account is used to connect to Sophos PureMessage for Microsoft Exchange services. Click Next .

7. In the Start Copying Files dialog box, click Next .

8. When installation is complete, the InstallShield Wizard Complete dialog box is displayed. Click

Finish .

9. Double-click the PureMessage for Microsoft Exchange icon on your desktop to start the

PureMessage for Microsoft Exchange administration console.

In certain circumstances the installation may require you to restart the server. The installation will continue after restarting.

3.6 PureMessage for Microsoft Exchange

Conﬁguration Group

If several PureMessage for Microsoft Exchange servers are required to implement the same policy then they should be installed to the same PureMessage for Microsoft Exchange group. This is achieved by selecting the same database and PureMessage for Microsoft Exchange group name during installation.

Once the ﬁrst PureMessage for Microsoft Exchange server has been installed in a group, the group name becomes available from the PureMessage Conﬁguration Group dialog box so that additional servers can be easily installed to the same group:

PureMessage for Microsoft Exchange 2013 and 2016

All PureMessage for Microsoft Exchange servers in a group should be in the same Windows domain or workgroup. If your Exchange servers are in separate domains or workgroups, they should be managed separately.

For more information on installing PureMessage for Microsoft Exchange to an Exchange cluster,

see Appendix A: Deploying PureMessage for Microsoft Exchange clusters

(page 27).

PureMessage for Microsoft Exchange 2013 and 2016

4 Starting and conﬁguring PureMessage for Microsoft Exchange

This section tells you how to:

• Start PureMessage for Microsoft Exchange

• Conﬁgure PureMessage for Microsoft Exchange to acknowledge your mail domain and upstream trusted email relay (if not done during installation)

• Connect to your directory server.

4.1 Getting started with PureMessage for

Microsoft Exchange

To start PureMessage for Microsoft Exchange, do as follows:

1. Double-click the PureMessage icon on your desktop.

2. In the PureMessage for Microsoft Exchange console, the left-hand pane (console tree) gives you access to the features you can conﬁgure. The right-hand pane (details) displays information or conﬁguration options.

If you set up a mail domain and upstream email relay during installation, see

Connect to Active

4.2 Set up a mail domain and upstream trusted relay

For PureMessage for Microsoft Exchange to determine inbound, outbound and internal mail correctly, you should conﬁgure your mail domains and any upstream (trusted) relays.

For information on conﬁguring upstream (trusted) relays, see Appendix B: How to conﬁgure upstream (trusted) relays

(page 30).

1. In the console tree, click Conﬁguration > System and then click Routing .

2. In the Routing dialog box, do as follows: a) Click Add , and enter an address in the Mail domains panel, such as mycompany.com.

Note

You need not specify sub-domains. When you specify a domain, the sub-domains are included automatically.

b) To add an upstream trusted relay, click Upstream (trusted) relays .

3. In the Upstream (trusted) relays dialog box, click Add to specify an upstream trusted relay address or range of addresses.

4. In the Specify Host IP Addresses dialog box, enter a single IP address or a range of addresses.

You can also enter a comment for administrative use and click OK .

5. In the Upstream (trusted) relays dialog box, click OK to save your relay(s).

6. In the Manage changes menu, click Save changes .

PureMessage for Microsoft Exchange now recognizes your speciﬁed mail domains and upstream

(trusted) relays.

Now connect to Active Directory. See Connect to Active Directory

(page 12).

4.3 Connect to Active Directory

You can conﬁgure PureMessage for Microsoft Exchange to integrate with Microsoft Active

Directory. You can then use recipient validation features and create message policies based on users and groups already conﬁgured in the directory server. If you do not need to use these features, skip this section.

Note

To conﬁgure directory server settings when using ADAM/AD LDS, see the PureMessage for

Microsoft Exchange help .

1. In the console tree, click Conﬁguration > Users and groups and click Active Directory .

2. In the Active Directory dialog box, click Detect Active Directory . The directory server settings should be ﬁlled in automatically. If not, you may need to ﬁll in the directory server settings manually.

3. Enter the user name and password in the Logon Credentials pane if you are synchronizing with an instance of ADAM/AD LDS or if you are synchronizing with the Active Directory

PureMessage for Microsoft Exchange 2013 and 2016

Global Catalog Server. Otherwise, PureMessage for Microsoft Exchange will log on using the

SophosPureMessage service account.

4. Click Verify settings . PureMessage for Microsoft Exchange will attempt to log on to your directory server.

5. Ensure the Synchronize with Active Directory checkbox is checked. You can then conﬁgure

PureMessage for Microsoft Exchange to synchronize with Active Directory (refresh its local copy) automatically or periodically.

PureMessage for Microsoft Exchange keeps a local copy (cache) of the users and groups from

Active Directory for performance reasons.

6. Click Synchronize now to start the synchronization process instantly.

If you have selected Automatic synchronization and if a change is made to an entity in Active

Directory, it may take about 15 minutes for the change to reﬂect in PureMessage for Microsoft

Exchange.

Before you can set up your transport (SMTP) and Exchange store conﬁguration, you need to set up

alerts. See Setting up alerts (page 14).

PureMessage for Microsoft Exchange 2013 and 2016

5 Setting up alerts

In order to receive PureMessage for Microsoft Exchange administrator alerts, you must conﬁgure this feature. You can also set up a template for alerts.

5.1 Setting up an address for alerts

1. In the console tree, click Conﬁguration > System and then click Alert conﬁguration .

2. In the Email addresses tab of the Alert conﬁguration dialog box, click Add . Enter the administrator’s email address in the Send administrator alerts to panel.

3. Enter an email address in the Sender email address panel. The email address will be used for sending out alerts and other PureMessage for Microsoft Exchange generated messages.

4. Click OK to save your changes.

5.2 Setting up a template for email alerts

The default email template for alerts is sufﬁcient for some users’ needs. However, you can customize the template as described below.

1. In the console tree, click Conﬁguration > System > Alert conﬁguration and then click the Alert template tab.

2. In the Alert subject panel, enter the subject line of the alert. Right-click in the edit panel to view available substitution symbols.

Substitution symbols can insert variables such as date or other information speciﬁc to the message.

3. In the Alert body text panel, create the main body of your alert. Right-click within the text ﬁeld to view substitution symbols.

4. In the Text for each incident panel, enter any unique per-incident text you want to display.

5. In the Alert Templates tab, click OK .

6. In the Manage changes menu, click Save changes .

PureMessage for Microsoft Exchange alerting is now conﬁgured.

Now see

Ensuring anti-virus scanning is enabled

(page 15).

PureMessage for Microsoft Exchange 2013 and 2016

6 Ensuring anti-virus scanning is enabled

By default, anti-virus scanning is enabled for inbound, outbound, and internal mail.

To check that anti-virus scanning is enabled, follow these steps:

1. In the console tree, click Conﬁguration > Transport (SMTP) scanning policy and then click Antivirus .

2. In the Anti-virus screen, ensure that the scanning status icons in the inbound, outbound, and internal message title bars are Green, and display ON .

Note

You can define separate policies for each direction of mail, and you can define specific policies for exempt users and groups. For more information, see the PureMessage for

Microsoft Exchange help .

PureMessage for Microsoft Exchange now protects against viral threats.

Next, see

Blocking ﬁles which may contain threats

(page 16).

PureMessage for Microsoft Exchange 2013 and 2016

7 Blocking ﬁles which may contain threats

Sophos recommends that you block inbound email attachments that are most likely to contain threats.

The On suspicious attachment policy rule is preconfigured to block file types that are commonly used to transport email threats, such as executable files (.exe, .scr, .com, .pif, etc). By default this rule is turned off.

1. In the console tree, click Conﬁguration > Transport (SMTP) scanning policy and then click

Content .

2. In the Content ﬁltering screen, ensure the status icon for inbound mail title bar is Green and displays ON .

3. Select the On suspicious attachment checkbox. Click Define to view and edit file types predefined by Sophos as suspicious attachments.

4. In the Inbound messages - Suspicious attachment type dialog box, click the Attachment types tab.

5. In the Attachment types tab, the attachment types in the Executable and Object Code groups are selected by default. On the Attachment names tab the Block multiple extensions option is selected by default.

6. Check the Block potentially unwanted applications (PUAs) except checkbox.

7. If you wish to allow users access to otherwise blocked applications, click Add to enter a PUA that you want to allow. PUA names can be found at http://www.sophos.com/security/analyses/ .

8. Click OK to save your changes and return to the Content ﬁltering pane.

9. In the Content ﬁltering dialog box, under the Inbound messages bar, in the On suspicious attachment panel, select Quarantine message from the drop-down menu.

10. Under the Inbound messages bar, in the On suspicious attachment panel, click Alert .

11. In the Alert configuration dialog box, check one or more check boxes to specify who will be notified in the event of PureMessage quarantining a suspicious attachment. Click OK to save your changes and return to the Content filtering pane.

12. In the Manage changes menu, click Save changes .

Note

For information on conﬁguring the content settings of your policy, see PureMessage for

Microsoft Exchange help .

PureMessage for Microsoft Exchange now:

• blocks and quarantines inbound messages with suspicious attachments.

• sends alerts to those you speciﬁed.

Now you can enable spam blocking, scan the Exchange message store, and tell users about quarantined mail. These functions are described in the sections that follow.

PureMessage for Microsoft Exchange 2013 and 2016

8 Blocking spam

You can conﬁgure PureMessage for Microsoft Exchange to deal with spam (unwanted incoming email). A typical anti-spam setting would be to delete spam and quarantine suspected spam.

1. In the console tree, click Conﬁguration > Transport (SMTP) scanning policy and then Antispam .

2. In the Anti-spam screen, in the Inbound messages bar, ensure the ON/OFF icon displays ON . If it displays OFF , click the icon to turn it on.

3. In the On-spam panel, select Delete message (or your preferred setting) from the drop-down menu.

4. In the On suspected spam panel, select Quarantine message (or your preferred setting) from the drop-down menu.

5. In the Manage changes menu, click Save changes .

Next you specify which mails you will categorize as spam and suspected spam by setting the spam ratings for PureMessage for Microsoft Exchange.

8.1 Change anti-spam settings

PureMessage for Microsoft Exchange gives each email a spam rating. The higher the rating, the more likely the email is to be spam. PureMessage for Microsoft Exchange uses this rating to decide whether the email should be treated as spam or suspected spam.

1. In the console tree, click Conﬁguration > Transport (SMTP) scanning policy > Anti-spam and then Change anti-spam settings .

2. In the Anti-spam settings dialog box, use the slider controls to adjust the threshold, above which

PureMessage for Microsoft Exchange regards an email as spam or suspected spam.

Note

Sophos recommends you set your ratings above 50 to avoid legitimate mail being classed as spam or suspected spam.

3. Ensure the Check reputation of message relays against external DNS block lists checkbox is checked. Enabling this option will check incoming messages against the IP addresses of known spam sources and will ﬁlter out any messages coming from these IP addresses.

4. In the Anti-spam settings dialog box, you can check the Check reputation of first external relay only checkbox only after configuring upstream (trusted) relays correctly. This option will only check the first external relay, for more deterministic spam scoring.

5. If you want to add the spam score as a SCL rating, check the Add spam score to message as

Microsoft Spam Conﬁdence Level (SCL) rating checkbox. Messages delivered to end users with a SCL rating higher than a particular value are diverted into the user’s Junk mail folder in

Microsoft Outlook. Click OK to save your changes.

6. In the Manage changes menu, click Save changes .

For optimal spam detection, ensure PureMessage for Microsoft Exchange has up-to-date information regarding the addresses of any upstream (trusted) relays. For more information on conﬁguring the anti-spam settings of your policy, see the PureMessage for Microsoft Exchange help .

PureMessage for Microsoft Exchange 2013 and 2016

9 Scanning Exchange Message Stores

You can conﬁgure PureMessage for Microsoft Exchange to run background scans of both private and public Exchange stores. Background scanning is done continuously at off-peak times.

For more information, see Enable store scanning and alerts (page 18).

Note

On-access and proactive scanning options are not supported on Exchange Server 2013 or later.

9.1 Enable store scanning and alerts

1. In the console tree, click Conﬁguration > Exchange store scanning policy .

2. In the Anti-virus dialog box, in the Exchange store scanning panel, ensure the ON/OFF icon displays ON . If it displays OFF , click the icon to turn it on.

3. In the On infection panel, select Replace attachment with text from the drop down menu. The

Text button appears. If you click the Text button, you can edit the text shown when PureMessage replaces an infected attachment.

4. In the On infection panel, click Alert .

5. In the Alert conﬁguration dialog box, ensure the Administrator checkbox is checked and click

OK to save your changes and return to the Anti-virus (Exchange store scanning) pane.

6. In the Manage changes menu, click Save changes .

PureMessage for Microsoft Exchange now

• scans the Exchange information store for viruses, and replaces the attachment with the conﬁgured text.

• sends an alert to the Administrator.

Now conﬁgure scanning of Exchange stores.

9.2 Conﬁgure scanning of Exchange stores

Note

The Exchange Store is made up of both public and private stores.

• A public store is a database that is accessible to multiple users.

• A private store (example, a mailbox) is usually only accessible to a single user.

You can conﬁgure PureMessage for Microsoft Exchange to run background scans at scheduled times on both the private and public stores.

1. In the console tree, click Conﬁguration > Exchange store scanning policy and then click

Change exchange store scan settings .

2. In the Exchange store scan settings dialog box, on the Exchange tab, select the Enable background scanning check box in the Exchange private store panel, Exchange public store panel, or both.

PureMessage for Microsoft Exchange 2013 and 2016

Note

On-access and proactive scanning options are not supported on Exchange Server 2013 or later.

3. If you want background scanning to be enabled only outside ofﬁce hours, select the Enable background scanning only for out of working hours check box, and select your working days and times.

4. Click OK to save your changes.

5. In the Manage Changes menu, click Save changes .

PureMessage for Microsoft Exchange now scans items as conﬁgured by your settings.

PureMessage for Microsoft Exchange 2013 and 2016

10 Dealing with quarantined items

Depending on your conﬁguration, PureMessage for Microsoft Exchange can quarantine mail that:

• is infected.

• is spam, or suspected spam.

• is encrypted, or has an encrypted attachment.

• has a suspicious or unwanted attachment.

• contains a blocked phrase or offensive language.

• is unscannable, or creates a scanning error.

Quarantined messages are isolated in a secured format in a central location on disk.

Administrators can deal with these messages in a number of ways, such as disinfect, delete, or deliver them.

You can also enable users to access a spam quarantine website, where they can review and deal with their quarantined spam messages.

This section tells you how to:

• do quarantine database housekeeping.

• deal with quarantined messages.

• enable end-users to access the spam quarantine website.

• set up digests to tell users about spam and suspected spam.

10.1 Quarantine housekeeping

You can specify the number of days to keep quarantined mail before deleting it.

1. In the console tree, click Quarantine .

2. In the Conﬁguration menu, click Change quarantine settings .

3. In the Quarantine settings dialog box, specify the number of days you want to keep quarantined mail before deleting it in the Number of days to keep mails in quarantine before deletion box.

4. Click OK to save your settings, and return to the Quarantine pane.

5. In the Manage Changes menu, click Save changes .

10.2 Dealing with quarantined messages

1. In the console tree, click Quarantine .

PureMessage for Microsoft Exchange 2013 and 2016

From this pane, you can enter search criteria in the Search panel, searching on subject, sender, recipient, message ID, reason for quarantine, or any combination of these. You can also ﬁlter your search by date using the To and From ﬁelds.

2. The list of quarantined messages is displayed in the details pane. Double-click an item for more details such as reasons for quarantining.

3. To deal with an item, highlight it, select an action from the drop-down menu in the Actions pane, and then click Go . You can delete a quarantined item or, remove the virus(es) and deliver it. If you believe mail to be wrongly classiﬁed please submit the item to Sophos for analysis. If you selected Deliver/Forward , go to step 4, otherwise the selected action is performed.

PureMessage for Microsoft Exchange 2013 and 2016

4. If you choose Deliver/Forward from the drop-down Actions menu, the Deliver message(s) dialog box appears. In the Deliver messages dialog box you can deliver the selected message(s) to intended recipients or to speciﬁed recipients. You can use this feature to forward quarantined items to an administrator to review the content of the email.

For more information, see the PureMessage for Microsoft Exchange help .

5. Note that PureMessage for Microsoft Exchange delivers a copy of the email. The original ﬁle remains in the quarantine folder for the number of days speciﬁed in the Quarantine settings dialog box, unless you choose to Automatically delete message(s) from quarantine after delivery .

6. If you want to add the sender to your list of trusted senders, check the Add sender to allowed list (skip spam scanning for this sender) checkbox.

7. Click OK to save your changes.

10.3 Enabling end-users to access the spam quarantine website

There are two ways to enable end-users access the spam quarantine website.

You can set a task to send all users with quarantined spam mail an email notiﬁcation, so they can

click a link to access the website. See Setting up quarantine digest emails to users (page 22).

Alternatively, if you use Active Directory, users can visit the spam quarantine website directly at any time using a web browser such as Internet Explorer, at the following address: http://servername:port/

Where servername

is the name of the server on which PureMessage for Microsoft Exchange is installed and port

is the port number for the quarantine digest website (port 8081 by default).

When the user accesses the website, Internet Information Services (IIS) will authenticate the user with Windows Authentication. If the user owns multiple email addresses (aliases), the spam quarantine website will show email messages quarantined for all the addresses.

If you want to distribute written instructions to your users that explain how to access the spam quarantine website, see the PureMessage for Microsoft Exchange help .

10.4 Setting up quarantine digest emails to users

PureMessage for Microsoft Exchange can send each user a message informing them that some of their email has been quarantined as spam. The user can follow a link to the web-based spam quarantine where they can delete unwanted mail, or retrieve wanted mail. To do this, set up spam quarantine digest email and schedule times when PureMessage for Microsoft Exchange should send it out.

1. In the console tree, click Conﬁguration > Users and groups and click End user spam digest email .

2. In the End user spam digest email dialog box, enter a subject in the Digest subject text box.

3. In the Digest body text panel, edit the digest as appropriate, or accept the default text. To enter or edit a substitution symbol, right-click and select a substitution symbol from the drop-down menu.

4. In the Send digests on panel, select the days and times you want to send out digests. Click OK to save your changes.

5. In the Manage Changes menu, click Save changes .

PureMessage for Microsoft Exchange 2013 and 2016

PureMessage for Microsoft Exchange now sends quarantine digest emails to users at speciﬁc times.

PureMessage for Microsoft Exchange 2013 and 2016

11 Monitoring system activity

The dashboard shows the system status and displays current statistics that provide the information about the health of all the servers on the system.

In the console tree, click Dashboard .

By default, the servers are listed in alphabetical order on the dashboard, unless one or more registers a system failure. In this case, the System Status trafﬁc light becomes red, the faulty server is marked with a warning icon, and the server is displayed at the top of the list.

For each server, the System console panel displays the following information:

• Whether Transport (SMTP) Scanning is Running, Stopped (by user), or Unavailable. If the status is unavailable, an alert is displayed.

• Whether Exchange Store scanning is Running, Stopped (by user), or Unavailable. If the status is unavailable, an alert is displayed.

• Whether the last update succeeded, and if so, the time and date it took place. If it did not succeed, an alert is displayed.

• Whether there is a virus outbreak, and if so, on which server.

• For the selected server, the Summary statistics for today panel displays scanning and quarantine information for today (that is, since midnight) and shows the trends for each main category of information in the form of a graph. The information includes:

PureMessage for Microsoft Exchange 2013 and 2016

— The current day’s transport (SMTP) scanning statistics (including message volume, spam and viruses).

— The current day’s Exchange store scanning statistics (including attachments processed, and viruses detected).

— The current day’s quarantine statistics.

All information is refreshed every two minutes.

PureMessage for Microsoft Exchange 2013 and 2016

12 Uninstalling PureMessage for

Microsoft Exchange

To uninstall PureMessage for Microsoft Exchange, do as follows:

1. If the PureMessage for Microsoft Exchange Administration console is open on any server, close it.

2. At the taskbar, click Start > Settings > Control Panel .

3. In Control Panel , double-click Add/Remove Programs .

4. In the Add/Remove Programs dialog box, select Sophos PureMessage and click Remove .

5. In the Conﬁrm Uninstall message box, click Yes .

A progress bar is displayed. Wait for uninstallation to complete.

PureMessage for Microsoft Exchange 2013 and 2016

13 Appendix A: Deploying PureMessage for Microsoft Exchange clusters

13.1 How PureMessage for Microsoft Exchange works with Exchange clusters

PureMessage for Microsoft Exchange incorporates a cluster-aware service that can be installed across multiple nodes. This allows PureMessage for Microsoft Exchange to be used with clustered

Microsoft Exchange servers and to take advantage of the increased resilience that a cluster offers.

Clustered systems are inherently more complicated than non-clustered systems and we recommend that you read the whole of this section before starting to install PureMessage for

Microsoft Exchange on a cluster.

If you still have questions about installing PureMessage for Microsoft Exchange on a cluster after reading this section, contact Sophos technical support.

13.2 Before you install

13.2.1 Database requirements

For cluster server installations, PureMessage for Microsoft Exchange cannot use a local MSDE or

SQL Server Express instance.

Alternatively, you may connect to any one of the following:

• A local clustered virtual SQL Server instance

• A remote SQL Server instance

• A remote MSDE or SQL Server Express instance

Note

In cluster scenarios, remote MSDE is not supported due to performance issues.

Note

PureMessage for Microsoft Exchange 4.0.4 and later supports TLS 1.2. Using TLS to connect to a

SQL Server database requires server side changes, see knowledge base article 132092 .

More than one PureMessage for Microsoft Exchange group or cluster can share a remote database.

13.2.2 Installation requirements

When installing PureMessage for Microsoft Exchange on nodes in a cluster, make sure that you meet the following requirements:

PureMessage for Microsoft Exchange 2013 and 2016

• The path to the installation folder must be identical on each node.

• The IIS websites present on each node of the cluster must be identical. In particular, the allocated port numbers of each site must be the same across nodes.

13.3 Installation procedure on DAGs

Database Availability Groups (DAGs) are used for implementing high availability in Exchange.

• For DAGs, PureMessage for Microsoft Exchange uses DFS Replication (DFSR) to copy quarantine ﬁles between nodes. If you are using DAGs with Exchange in a high availability environment with multiple Transport Servers, these servers must be part of a Microsoft cluster. This allows

PureMessage for Microsoft Exchange to replicate quarantine ﬁles using DFSR.

• The PureMessage for Microsoft Exchange service should be installed on each DAG member one after another, but not simultaneously.

• If a DAG member has PureMessage for Microsoft Exchange installed and if it is added or removed from the DAG, then PureMessage for Microsoft Exchange must be reinstalled on that server. This is required so that the replication settings on the server are updated.

To maintain Exchange availability during the reinstallation of PureMessage for Microsoft

Exchange, the mailbox databases hosted on the server should be moved to an alternative server in the DAG.

13.4 Uninstalling PureMessage for Microsoft

Exchange from a cluster

All PureMessage for Microsoft Exchange administration consoles (if running) need to be closed

from all servers before uninstalling. Follow instructions in Uninstalling PureMessage for Microsoft

Exchange (page 26).

13.5 Administering PureMessage for Microsoft

Exchange on a cluster

Several PureMessage for Microsoft Exchange servers may be arranged into a group and administered together from a single PureMessage for Microsoft Exchange console. All

PureMessage for Microsoft Exchange servers in a group have the same policy settings applied to them, that is, when a policy change is made it is automatically applied to all the servers in the group.

13.5.1 Requirements and limitations

• The number of PureMessage for Microsoft Exchange servers in a group is limited by users' network bandwidth, and by SQL Server database resource limits.

• All group members need to also be members of the same domain.

• The ability to administer PureMessage for Microsoft Exchange servers from the remote console is directly dependent on the reliability of user network and database server connections.

PureMessage for Microsoft Exchange 2013 and 2016

13.5.2 Using the PureMessage for Microsoft Exchange administration console

To manage a group of PureMessage for Microsoft Exchange servers, the PureMessage for

Microsoft Exchange console should connect to any server in the group. When policy changes are made, they will be automatically applied to all services in the group. Additionally, the activity monitor and dashboard screens will display status information for all the servers in the group:

To manage a different group of PureMessage for Microsoft Exchange servers from the same console, it is necessary to disconnect from the current group and reconnect to a server from the new group.

To do this, on the PureMessage for Microsoft Exchange toolbar, click on the Select server icon.

PureMessage for Microsoft Exchange 2013 and 2016

14 Appendix B: How to conﬁgure upstream (trusted) relays

You should conﬁgure any upstream (trusted) relays to improve your email scanning speed and spam detection.

By default, PureMessage for Microsoft Exchange will run a reputation check on each email server address speciﬁed in an email. When a server is added to the upstream (trusted) relay list, the reputation check for that server is skipped. Because a lower volume of reputation checks has to be carried out, this improves the email scanning speed.

Upstream (trusted) relays also enable the spam engine to match an email server’s address against the known list of spamming email servers with more precision. A higher spam score can therefore be allocated to the email when a match is found.

14.1 Which upstream relays should be deﬁned as trusted?

You should deﬁne as an upstream (trusted) relay any email relay that sends or forward emails to

PureMessage for Microsoft Exchange and that meets one of the following criteria:

• Your ISP’s SMTP server.

• Any email relays located on your network which are upstream to your PureMessage for Microsoft

Exchange server(s).

• A server which delivers mail to other servers in a cluster.

For more information see, Set up a mail domain and upstream trusted relay (page 12).

PureMessage for Microsoft Exchange 2013 and 2016

Figure 2: Trusted upstream relays

PureMessage for Microsoft Exchange 2013 and 2016

15 Appendix C: How does PureMessage for Microsoft Exchange route mail?

PureMessage for Microsoft Exchange uses the conﬁgured mail domains, trusted upstream relays, and IP address of the connecting host to distinguish between inbound, outbound and internal mail.

1. Is the recipient domain on the conﬁgured mail domain list?

No : the message is outbound.

Yes : go to step 2.

2. Is the sender’s IP address external?

Yes : the message is inbound.

No : go to step 3.

3. Is the sender’s IP address internal or unavailable?

Internal : go to step 4.

Unavailable : the message is internal.

4. Is the internal IP address on the list of trusted relays?

Yes : the message is inbound.

No : the message is internal.

PureMessage for Microsoft Exchange 2013 and 2016

16 Appendix D: AboutPureMessage for

Microsoft Exchange mail scanning

PureMessage for Microsoft Exchange scans all SMTP inbound, outbound, and internal email messages and Exchange store emails and includes threat reduction technology to protect against new or unknown email-borne threats.

16.1 SMTP scanning

16.1.1 SMTP ﬁltering

The SMTP ﬁltering options in PureMessage for Microsoft Exchange perform recipient validation and use custom block lists to block hosts and messages in order to reduce the processing overhead on the server and save bandwidth.

Recipient validation

Organizations receive a lot of spam messages that are addressed to non-existent users. Recipient validation allows you to discard messages addressed to non-existent users.

This option requires a connection to a directory server or custom users and groups to provide the email addresses which are used to validate recipients. Typically this will be an Active Directory server.

Block lists

Block lists allow you to specify hosts and senders from whom PureMessage for Microsoft

Exchange should not accept any messages.

Note

For information on enabling recipient validation and creating block lists, see the PureMessage for

Microsoft Exchange help .

16.1.2 Anti-virus policies

You can deﬁne separate anti-virus policies for inbound, outbound and internal mail.

For information on conﬁguring anti-virus scanning, see Ensuring anti-virus scanning is enabled

(page 15).

16.1.3 Anti-spam policy

If your license permits, you can deﬁne an anti-spam policy.

PureMessage for Microsoft Exchange 2013 and 2016

PureMessage for Microsoft Exchange applies the anti-spam policy only to inbound messages. The anti-spam policy is On by default and applies to all users, but you can conﬁgure exceptions.

For information on deﬁning an anti-spam policy, see

Blocking spam (page 17).

16.1.4 Content ﬁltering policies

PureMessage for Microsoft Exchange scans inbound, outbound and internal mail and filters unwanted content such as administrator-defined phrases and offensive language. You can define policies to filter content in a message header, subject, body, and/or attachment.

Note

For information on deﬁning content ﬁltering policies, see Appendix E: Filtering attachments containing unwanted content

(page 35).

16.1.5 Attachment blocking

PureMessage for Microsoft Exchange can block suspicious or unwanted attachments and PUAs according to user-deﬁned attachment types.

For information on blocking attachments and PUAs, see Blocking ﬁles which may contain threats

(page 16).

16.2 Exchange Store scanning

PureMessage for Microsoft Exchange provides background scanning of Exchange private and public information stores using the Exchange Web Services API (EWS API).

Each time an item is scanned, it is stamped with an ID which indicates the virus signature version number at the time of scanning. An item will be rescanned only if a more up-to-date virus signature has been released by Sophos.

16.2.1 Background scanning

Exchange server background scanning continuously navigates the entire Exchange Store. As items that have not been scanned are encountered, they are submitted to PureMessage for

Microsoft Exchange for scanning.

Background scanning is disabled by default for both private and public information stores.

As background scanning has a performance impact on the Exchange server, we recommend that you schedule it to run during periods of low server activity. Background scanning schedules can be deﬁned in the Exchange store scan settings dialog.

Note

The scanning process will be reset if a virus signature update is received from Sophos. For large message stores, this can mean that background scanning will not complete a full scan of the store.

For information on deﬁning background scanning periods and enabling background scanning, see

Conﬁgure scanning of Exchange stores (page 18).

PureMessage for Microsoft Exchange 2013 and 2016

17 Appendix E: Filtering attachments containing unwanted content

PureMessage for Microsoft Exchange can analyze content within common document types. This enables you to search for phrases within those documents when they are attached to messages as ﬁles and apply policy rules accordingly.

PureMessage for Microsoft Exchange can extract content from the following ﬁle types:

• Plain text (TXT)

• HTML

• Rich text (RTF)

• PDF

• Microsoft Ofﬁce documents (DOC, DOCX, PPT, PPTX, XLS, XLSX, etc)

• Microsoft Project

• Microsoft Visio

17.1 Filtering blocked phrases within attachments

This section contains two examples of how you can deﬁne policies to ﬁlter attachments which contain blocked phrases.

1. Identify attachments containing the word “Conﬁdential”. You do this by deﬁning a string of text as a blocked phrase.

2. Identify attachments containing credit card numbers in the format “1234 1234 1234 1234” or

“1234123412341234”. You do this by deﬁning a regular expression as a blocked phrase.

17.1.1 Filtering blocked phrases - strings of text

To deﬁne a string of text as a blocked phrase:

1. In the console tree, click Conﬁguration > Transport (SMTP) Scanning Policy , and then click

Content .

2. In the Content ﬁltering dialog box, ensure that the status icons for inbound, outbound and internal messages title bars are Green and display ON .

3. Under Outbound messages , select the On blocked phrase check box.

4. Under Outbound messages > On blocked phrase , click Deﬁne .

5. On the String (wildcards supported) tab, click Add .

6. Click in the Phrase box and enter

Confidential

7. Make sure that the Attachment check box is selected.

8. Click OK to save your changes and return to the Content ﬁltering dialog box.

9. Under Outbound messages , click the On blocked phrase drop-down list and select Quarantine message and deliver .

PureMessage for Microsoft Exchange 2013 and 2016

10. In the Manage changes menu, click Save changes .

17.1.2 Filtering blocked phrases - regular expressions

To deﬁne a regular expression as a blocked phrase:

1. In the console tree, click Conﬁguration > Transport (SMTP) Scanning Policy , and then click

Content .

2. In the Content ﬁltering dialog box, ensure that the status icons for inbound, outbound and internal messages title bars are Green and display ON .

3. Under Internal messages , select the On blocked phrase check box.

4. Under Internal messages > On blocked phrase , click Deﬁne .

5. On the Regular expression tab, click Add .

6. Click in the Phrase box and type the following regular expression:

[0-9]{4} ?[0-9]{4} ?[0-9]{4} ?[0-9]{4}

This expression will match credit card numbers in both "1234 1234 1234 1234" and

"1234123412341234" formats.

7. Make sure that the Attachment check box is selected.

8. Click OK to save your changes and return to the Content ﬁltering dialog box.

9. Under Internal messages > On blocked phrase , click Alert .

10. In the Alert conﬁguration dialog box, select one or more check boxes to specify who will be notiﬁed in the event of PureMessage quarantining a suspicious attachment.

11. Click OK to save your changes and return to the Content ﬁltering dialog box.

12. In the Manage changes menu, click Save changes .

You can ﬁnd more information about creating regular expressions at http://www.regularexpressions.info/ .

PureMessage for Microsoft Exchange 2013 and 2016

18 Appendix F: Database Mirroring

Database mirroring is a feature of SQL Server (available only in the Standard and Enterprise editions of SQL Server since SQL Server 2005 SP1) that provides high-availability without the need for a single-copy cluster.

To use mirrored databases with PureMessage for Microsoft Exchange, you must perform the following:

•

Prepare SQL Server instances (page 37)

•

Install PureMessage for Microsoft Exchange with database mirroring

(page 38)

•

Conﬁgure PureMessage for Microsoft Exchange for database mirroring (page 38)

18.1 Prepare SQL Server instances

Before installing PureMessage for Microsoft Exchange, you must prepare the SQL Server instances that will be used. A mirrored SQL database requires two or three SQL Server instances:

1. A principal server instance (data source).

2. A mirror server instance (failover partner).

3. Optionally, a witness server instance.

For information on SQL Server preparation for mirroring, see: http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx

http://msdn.microsoft.com/en-us/library/ms190941.aspx

Note

• Ensure that the SQL Server instances are authenticated to access each other. This means that the accounts under which a SQL Server instances run must be granted access to the other SQL Server instances used in the mirror set, and that remote connections (e.g. over the

TCP/IP protocol) must be enabled.

• The principal and mirror server instances should host the same edition of SQL Server, and it should be an edition that supports mirroring.

• For automatic failover, a witness server is required.

• For high-availability, the SQL Server instances must be installed on different physical servers and use synchronous mode.

• If any ﬁrewalls exist between the SQL Servers, they must be conﬁgured to allow the SQL servers to communicate over the TCP port chosen for mirroring.

• It is recommended that SQL installations use the same SQL instance name and ﬁle paths on all servers.

PureMessage for Microsoft Exchange 2013 and 2016

18.2 Install PureMessage for Microsoft Exchange with database mirroring

Database mirroring is enabled in PureMessage for Microsoft Exchange by selecting the Remote database option and supplying the names of both the principal and mirror server instances during installation. The names should be entered in the PureMessage Database settings dialog box, separated with a semi-colon.

Example:

Server1\Instance1;Server2\Instance1

If PureMessage for Microsoft Exchange has already been installed without mirroring then these changes can be made retrospectively. For information, contact Sophos Technical Support.

18.3 Conﬁgure PureMessage for Microsoft

Exchange for database mirroring

Once the PureMessage for Microsoft Exchange installation is completed, the databases and

PureMessage for Microsoft Exchange login will have been created on the principal server instance.

The PureMessage for Microsoft Exchange login is named

<domain>\SophosPureMessage

, where

<domain> is the domain of the PureMessage for Microsoft Exchange Server (or the machine name for a server that is in a workgroup).

The following steps can all be performed from the SQL Server Management Studio application, or by issuing the SQL commands provided:

For more information on using SQL Server Management Studio see, http:// technet.microsoft.com/en-us/library/ms175134.aspx

1. Create the PureMessage for Microsoft Exchange login on the mirror server instance:

[Mirror]> CREATE LOGIN [<domain name>\SophosPureMessage] FROM WINDOWS

must be replaced with the actual domain of your PureMessage for Microsoft

Exchange server, or with the machine name if in a workgroup.

For more information on setting up login accounts, see http://technet.microsoft.com/en-us/ library/ms366346.aspx

2. Perform a full backup for each of the four PureMessage for Microsoft Exchange databases from the principal server:

[Principal]> BACKUP DATABASE [SavexCnfg] TO DISK = '<path>

\SavexCnfg.bak'

[Principal]> BACKUP DATABASE [SavexDir] TO DISK = '<path>

\SavexDir.bak'

[Principal]> BACKUP DATABASE [SavexQuar] TO DISK = '<path>

\SavexQuar.bak'

[Principal]> BACKUP DATABASE [SavexRprt] TO DISK = '<path>

\SavexRprt.bak'

<path>

must be replaced with a path to a folder where the backup is to be stored.

For more information on preparing a mirror database for mirroring, see http:// technet.microsoft.com/en-us/library/ms189047.aspx

PureMessage for Microsoft Exchange 2013 and 2016

3. Make the database backup available on the mirror server and restore each database to the mirror server instance. This will set the mirrored databases to Mirror, Synchronized/Restoring state.

[Mirror]> RESTORE DATABASE [SavexCnfg] FROM DISK = '<path>

\SavexCnfg.bak' WITH NORECOVERY

[Mirror]> RESTORE DATABASE [SavexDir] FROM DISK = '<path>

\SavexDir.bak' WITH NORECOVERY

[Mirror]> RESTORE DATABASE [SavexQuar] FROM DISK = '<path>

\SavexQuar.bak' WITH NORECOVERY

[Mirror]> RESTORE DATABASE [SavexRprt] FROM DISK ='<path>

\SavexRprt.bak' WITH NORECOVERY

<path>

must be replaced with a path to a folder where the backup is held.

If the path names of the principal and mirror databases differ then it will be necessary to use the MOVE option of the RESTORE command, e.g.

[Mirror]> RESTORE DATABASE [SavexCnfg] FROM DISK =

<path>\SavexCnfg.bak' WITH NORECOVERY,

MOVE 'SavexCnfg' TO 'C:\Program Files\Microsoft SQL

Server\MSSQL.1\MSSQL\DATA\SavexCnfg.mdf',

MOVE 'SavexCnfg_log' TO 'C:\Program Files\Microsoft SQL

Server\MSSQL.1\MSSQL\DATA\SavexCnfg_1.LDF'

For more information on preparing a mirror database for mirroring, see http:// technet.microsoft.com/en-us/library/ms189047.aspx

4. Create a mirroring endpoint on the principal server instance:

[Principal]> CREATE ENDPOINT [Mirroring]

STATE=STARTED

AS TCP (LISTENER_PORT = <port>)

FOR DATA_MIRRORING (ROLE = PARTNER)

<port>

must be replaced with a TCP port number to be used for the endpoint (e.g. 7022).

5. Create an endpoint on the mirror server instance:

[Mirror]> CREATE ENDPOINT [Mirroring]

STATE=STARTED

AS TCP (LISTENER_PORT = <port>)

FOR DATA_MIRRORING (ROLE = ALL)

6. Point the mirror server instance's partner to the principal server instance:

[Mirror]> ALTER DATABASE [SavexCnfg] SET PARTNER = 'TCP://

<hostname>:<port>'

[Mirror]> ALTER DATABASE [SavexDir] SET PARTNER = 'TCP://

<hostname>:<port>'

[Mirror]> ALTER DATABASE [SavexQuar] SET PARTNER = 'TCP://

<hostname>:<port>'

[Mirror]> ALTER DATABASE [SavexRprt] SET PARTNER = 'TCP://

<hostname>:<port>'

must be replaced with the fully-qualiﬁed, DNS hostname of the principal server.

<port>

must be replaced with a TCP port number to be used for the endpoint (e.g. 7022).

7. Point the principal server instance's partner to the mirror server instance:

PureMessage for Microsoft Exchange 2013 and 2016

[Principal]> ALTER DATABASE [SavexCnfg] SET PARTNER = 'TCP://

<hostname>:<port>' [Principal]> ALTER DATABASE [SavexDir] SET PARTNER

= 'TCP://<hostname>:<port>' [Principal]> ALTER DATABASE [SavexQuar]

SET PARTNER = 'TCP://<hostname>:<port>' [Principal]> ALTER DATABASE

[SavexRprt] SET PARTNER = 'TCP://<hostname>:<port>'

must be replaced with the fully-qualiﬁed, DNS hostname of the mirror server.

<port>

must be replaced with a TCP port number to be used for the endpoint (e.g. 7022).

For more information on setting up database mirroring using Windows authentication, see http://technet.microsoft.com/en-us/library/ms179306.aspx

8. If a witness server is required then it can be conﬁgured as follows:

[Witness]> CREATE ENDPOINT [Mirroring]

STATE=STARTED

AS TCP (LISTENER_PORT = <port>)

FOR DATA_MIRRORING (ROLE = WITNESS)

<port>

must be replaced with a TCP port number to be used for the endpoint (e.g. 7022).

9. If a witness server is required on the principal server, set the witness for each database:

[Principal]> ALTER DATABASE [SavexCnfg] SET WITNESS = 'TCP://

<hostname>:<port>'

[Principal]> ALTER DATABASE [SavexDir] SET WITNESS = 'TCP://

<hostname>:<port>'

[Principal]> ALTER DATABASE [SavexQuar] SET WITNESS = 'TCP://

<hostname>:<port>'

[Principal]> ALTER DATABASE [SavexRprt] SET WITNESS = 'TCP://

<hostname>:<port>'

must be replaced with the fully-qualiﬁed, DNS hostname of the witness server.

<port>

must be replaced with a TCP port number to be used for the endpoint (e.g. 7022).

For more information on adding a database mirroring witness using Windows authentication, see http://technet.microsoft.com/en-us/library/ms190430.aspx

10. Depending on the permissions of the accounts running the SQL servers it may be necessary to explicitly grant permissions to the accounts for accessing the endpoints as follows:

[Principal]> GRANT CONNECT ON ENDPOINT::[Mirroring] TO [<user>]

[Mirror]> GRANT CONNECT ON ENDPOINT::[Mirroring] TO [<user>]

[Witness]> GRANT CONNECT ON ENDPOINT::[Mirroring] TO [<user>]

<user>

must be replaced with the SAM name of account running the accessing SQL Server.

11. If necessary, e.g. if the servers are under heavy load, increase the ping timeout for the connections as follows:

[Principal]> ALTER DATABASE [SavexCnfg] SET PARTNER TIMEOUT <integer>

[Principal]> ALTER DATABASE [SavexDir] SET PARTNER TIMEOUT <integer>

[Principal]> ALTER DATABASE [SavexQuar] SET PARTNER TIMEOUT <integer>

[Principal]> ALTER DATABASE [SavexRprt] SET PARTNER TIMEOUT <integer>

must be replaced with the required timeout (in seconds). The default time out used by SQL Server is 10 seconds.

PureMessage for Microsoft Exchange 2013 and 2016

19 PureMessage for Microsoft Exchange

Glossary

Active Directory synchronization

Active/Passive cluster active scanning

Advanced adware anti-spam rules

Auto background scanning blacklist console tree dashboard domain controller demilitarized zone (DMZ) details pane digest downstream

A one-way synchronization of Active Directory users and groups with the PureMessage for

Microsoft Exchange cache.

A two-node cluster where the Active node owns the services and the Passive node remains inoperative.

Scans an item as soon as it is read or saved to the store.

Scans every part of every ﬁle.

A program that displays advertising - such as pop-up messages - which affects user productivity and system efﬁciency.

Rules that are applied to an email to decide whether it should be classiﬁed as spam.

Scans those parts of each ﬁle that are likely to contain a virus.

A form of scanning in which the Exchange

Store is scanned when the Exchange server has periods of low activity.

Email from addresses in a blacklist is always blocked.

The left-hand pane of the PureMessage console.

An at-a-glance view of the status of the

PureMessage for Microsoft Exchange servers.

In an Active Directory forest, a server that contains a writable copy of the Active Directory database, participates in Active Directory replication, and controls access to network resources. Administrators can manage user accounts, network access, shared resources, site topology, and other directory objects from any domain controller in the forest.

A network area protected by ﬁrewalls that sits between an organization’s internal network and an external network, usually the internet.

The right-hand pane of the PureMessage for

Microsoft Exchange console.

A message that warns a user that email intended for them has been quarantined.

A transmission from an information server toward an end user.

PureMessage for Microsoft Exchange 2013 and 2016 email relay email scanning

Exchange Store failover forest

IFilters information store jobs malware node non-delivery report (NDR) on-access scanning outbreak proactive scanning private store public store real-time scanning

A type of server used to pass email from one point of the internet to another. Every email contains a list of the email relays it passes through on the internet, including the relay that was used to send the email.

Real-time scanning of email.

The mailbox and public folders stored on an

Exchange server.

In an Active/Passive cluster, the capability to switch services automatically to the Passive node upon the failure or abnormal termination of the Active node.

One or more Active Directory domains that share the same class and attribute deﬁnitions

(schema), site and replication information

(conﬁguration), and forest-wide search capabilities (global catalog). Domains in the same forest are linked with two-way, transitive trust relationships.

Plugins that allow the Windows Indexing Service and the newer Windows Desktop Search to index different various ﬁle formats. Also used by

PureMessage for Microsoft Exchange to extract content from ﬁles.

See Exchange store.

Types of scanning.

Short for malicious software. Software designed speciﬁcally to damage or disrupt a system, such as a virus, worm, or Trojan.

A server that is part of a cluster.

An automated electronic mail message from a mail system to a sender indicating failed message delivery.

A form of real-time scanning in which new items in the Exchange Store are scanned as soon as they are accessed by an email client.

A situation in which a conﬁgurable number of threats are detected in a conﬁgurable amount of time.

A form of real-time scanning in which new items added to the Exchange Store are added to a queue for scanning.

A database (usually a mailbox) on an Exchange server that is only accessible to a single user.

A database on an Exchange server that is accessible to multiple users.

Automatic interception and scanning of email attachments as they are sent or received.

scheduled scan

Simple Exchange organization

Simple Mail Transfer Protocol (SMTP) spam rating upstream trusted relay upstream whitelist

PureMessage for Microsoft Exchange 2013 and 2016

A scan that is scheduled to take place automatically at a particular time.

A single Exchange 2007 server that provides all

Exchange services and stores all Exchange data for the entire organization.

An internet standard for email transmission across IP networks. Email server software uses

SMTP to send and receive mail messages.

The score assigned to a message by the antispam engine that indicates the relative likelihood that the message is spam.

A known email server that sends or forward emails to the server on which PureMessage for

Microsoft Exchange is installed.

A transmission from an end user toward the server.

Email from addresses in a whitelist is never blocked.

PureMessage for Microsoft Exchange 2013 and 2016

20 Technical support

You can ﬁnd technical support for Sophos products in any of these ways:

• Visit the Sophos Community at community.sophos.com/ and search for other users who are experiencing the same problem.

• Visit the Sophos support knowledge base at www.sophos.com/en-us/support.aspx

• Download the product documentation at www.sophos.com/en-us/support/ documentation.aspx

• Open a ticket with our support team at https://secure2.sophos.com/support/contact-support/ support-query.aspx

PureMessage for Microsoft Exchange 2013 and 2016

21 Legal notices

Copyright © 2018 Sophos Limited. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise unless you are either a valid licensee where the documentation can be reproduced in accordance with the license terms or you otherwise have the prior permission in writing of the copyright owner.

Sophos and Sophos Anti-Virus are registered trademarks of Sophos Limited and Sophos Group. All other product and company names mentioned are trademarks or registered trademarks of their respective owners.

Common Public License

The Sophos software that is referenced in this document includes or may include some software programs that are licensed (or sublicensed) to the user under the Common Public License (CPL), which, among other rights, permits the user to have access to the source code. The CPL requires for any software licensed under the terms of the CPL, which is distributed in object code form, that the source code for such software also be made available to the users of the object code form. For any such software covered under the CPL, the source code is available via mail order by submitting a request to Sophos; via email to [email protected]

or via the web at https:// www.sophos.com/en-us/support/contact-support.aspx

. A copy of the license agreement for any such included software can be found at http://opensource.org/licenses/cpl1.0.php

crt

# $FreeBSD$

# @(#)COPYRIGHT 8.2 (Berkeley) 3/21/94

The compilation of software known as FreeBSD is distributed under the following terms:

Redistribution and use in source and binary forms, with or without modiﬁcation, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the DOCUMENTATION and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS

OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT

SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR

BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER

IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN

ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH

DAMAGE.

PureMessage for Microsoft Exchange 2013 and 2016

The 4.4BSD and 4.4BSD-Lite software is distributed under the following terms:

All of the documentation and software included in the 4.4BSD and 4.4BSD-Lite Releases is copyrighted by The Regents of the University of California.

Redistribution and use in source and binary forms, with or without modiﬁcation, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the University of California,

Berkeley and its contributors.

4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without speciﬁc prior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS

OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT

SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR

BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER

IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN

ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH

DAMAGE.

The Institute of Electrical and Electronics Engineers and the American National Standards

Committee X3, on Information Processing Systems have given us permission to reprint portions of their documentation.

In the following statement, the phrase "this text" refers to portions of the system documentation.

Portions of this text are reprinted and reproduced in electronic form in the second BSD Networking

Software Release, from IEEE Std 1003.1-1988, IEEE Standard Portable Operating System Interface for Computer Environments (POSIX), copyright C 1988 by the Institute of Electrical and Electronics

Engineers, Inc. In the event of any discrepancy between these versions and the original IEEE

Standard, the original IEEE Standard is the referee document.

In the following statement, the phrase "This material" refers to portions of the system documentation. This material is reproduced with permission from American National Standards

Committee X3, on Information Processing Systems. Computer and Business Equipment

Manufacturers Association (CBEMA), 311 First St., NW, Suite 500, Washington, DC 20001-2178.

The developmental work of Programming Language C was completed by the X3J11 Technical

Committee.

The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing ofﬁcial policies, either expressed or implied, of the

Regents of the University of California.

NOTE: The copyright of UC Berkeley's Berkeley Software Distribution ("BSD") source has been updated. The copyright addendum may be found at fttp://ftp.cs.berkeley.edu/pub/4bsd/

README.Impt.License. Change and is included below.

July 22, 1999

PureMessage for Microsoft Exchange 2013 and 2016

To All Licensees, Distributors of Any Version of BSD:

As you know, certain of the Berkeley Software Distribution ("BSD") source code ﬁles require that further distributions of products containing all or portions of the software, acknowledge within their advertising materials that such products contain software developed by UC Berkeley and its contributors.

Speciﬁcally, the provision reads:

"3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the University of California,

Berkeley and its contributors."

Effective immediately, licensees and distributors are no longer required to include the acknowledgement within advertising materials. Accordingly, the foregoing paragraph of those BSD

Unix ﬁles containing it is hereby deleted in its entirety.

William Hoskins

Director, Ofﬁce of Technology Licensing

University of California, Berkeley

dtoa.c

The author of this software is David M. Gay.

Permission to use, copy, modify, and distribute this software for any purpose without fee is hereby granted, provided that this entire notice is included in all copies of any software which is or includes a copy or modiﬁcation of this software and in all copies of the supporting documentation for such software.

THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY. IN

PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY REPRESENTATION OR WARRANTY

OF ANY KIND CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY

PARTICULAR PURPOSE.

IEEE Software Taggant Library

This software was developed by The Institute of Electrical and Electronics Engineers, Incorporated

(IEEE), through the Industry Connections Security Group (ICSG) of its Standards Association.

Portions of it include software developed by the OpenSSL Project for use in the OpenSSL Toolkit

(http://www.openssl.org/), and those portions are governed by the OpenSSL Toolkit License.

IEEE License

Redistribution and use in source and binary forms, with or without modiﬁcation, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment:

PureMessage for Microsoft Exchange 2013 and 2016

"This product includes software developed by the IEEE Industry Connections Security Group

(ICSG)".

4. The name "IEEE" must not be used to endorse or promote products derived from this software without prior written permission from the IEEE Standards Association ([email protected]).

5. Products derived from this software may not contain "IEEE" in their names without prior written permission from the IEEE Standards Association ([email protected]).

6. Redistributions of any form whatsoever must retain the following acknowledgment:

"This product includes software developed by the IEEE Industry Connections Security Group

(ICSG)".

THIS SOFTWARE IS PROVIDED "AS IS" AND "WITH ALL FAULTS." IEEE AND ITS CONTRIBUTORS

EXPRESSLY DISCLAIM ALL WARRANTIES AND REPRESENTATIONS, EXPRESS OR IMPLIED,

INCLUDING, WITHOUT LIMITATION: (A) THE IMPLIED WARRANTIES OF MERCHANTABILITY AND

FITNESS FOR A PARTICULAR PURPOSE; (B) ANY WARRANTY OF NON-INFRINGEMENT; AND (C)

ANY WARRANTY WITH RESPECT TO THE QUALITY, ACCURACY, EFFECTIVENESS, CURRENCY OR

COMPLETENESS OF THE SOFTWARE.

IN NO EVENT SHALL IEEE OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,

INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES, (INCLUDING, BUT NOT

LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR

PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,

WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY

OF SUCH DAMAGE AND REGARDLESS OF WHETHER SUCH DAMAGE WAS FORESEEABLE.

THIS SOFTWARE USES STRONG CRYPTOGRAPHY, WHICH MAY BE SUBJECT TO LAWS AND

REGULATIONS GOVERNING ITS USE, EXPORTATION OR IMPORTATION. YOU ARE SOLELY

RESPONSIBLE FOR COMPLYING WITH ALL APPLICABLE LAWS AND REGULATIONS, INCLUDING,

BUT NOT LIMITED TO, ANY THAT GOVERN YOUR USE, EXPORTATION OR IMPORTATION OF THIS

SOFTWARE. IEEE AND ITS CONTRIBUTORS DISCLAIM ALL LIABILITY ARISING FROM YOUR USE OF

THE SOFTWARE IN VIOLATION OF ANY APPLICABLE LAWS OR REGULATIONS.

Info-ZIP

For the purposes of this copyright and license, “Info-ZIP” is deﬁned as the following set of individuals:

Mark Adler, John Bush, Karl Davis, Harald Denker, Jean-Michel Dubois, Jean-loup Gailly, Hunter

Goatley, Ed Gordon, Ian Gorman, Chris Herborth, Dirk Haase, Greg Hartwig, Robert Heath, Jonathan

Hudson, Paul Kienitz, David Kirschbaum, Johnny Lee, Onno van der Linden, Igor Mandrichenko,

Steve P. Miller, Sergio Monesi, Keith Owens, George Petrov, Greg Roelofs, Kai Uwe Rommel, Steve

Salisbury, Dave Smith, Steven M. Schweda, Christian Spieler, Cosmin Truta, Antoine Verheijen, Paul von Behren, Rich Wales, Mike White

This software is provided “as is,” without warranty of any kind, express or implied. In no event shall Info-ZIP or its contributors be held liable for any direct, indirect, incidental, special or consequential damages arising out of the use of or inability to use this software.

Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. Redistributions of source code must retain the above copyright notice, deﬁnition, disclaimer, and this list of conditions.

PureMessage for Microsoft Exchange 2013 and 2016

2. Redistributions in binary form (compiled executables and libraries) must reproduce the above copyright notice, deﬁnition, disclaimer, and this list of conditions in documentation and/or other materials provided with the distribution. The sole exception to this condition is redistribution of a standard UnZipSFX binary (including SFXWiz) as part of a self-extracting archive; that is permitted without inclusion of this license, as long as the normal SFX banner has not been removed from the binary or disabled.

3. Altered versions—including, but not limited to, ports to new operating systems, existing ports with new graphical interfaces, versions with modiﬁed or added functionality, and dynamic, shared, or static library versions not from Info-ZIP—must be plainly marked as such and must not be misrepresented as being the original source or, if binaries, compiled from the original source. Such altered versions also must not be misrepresented as being Info-ZIP releases-including, but not limited to, labeling of the altered versions with the names "Info-ZIP" (or any variation thereof, including, but not limited to, different capitalizations), "Pocket UnZip," "WiZ" or

"MacZip" without the explicit permission of Info-ZIP. Such altered versions are further prohibited from misrepresentative use of the Zip-Bugs or Info-ZIP e-mail addresses or the Info-ZIP URL(s), such as to imply Info-ZIP will provide support for the altered versions.

4. Info-ZIP retains the right to use the names “Info-ZIP,” “Zip,” “UnZip,” “UnZipSFX,” “WiZ,” “Pocket

UnZip,” “Pocket Zip,” and “MacZip” for its own source and binary releases.

Lua

The Sophos software that is described in this document may include some software programs that are licensed (or sublicensed) to the user under the Lua License. A copy of the license agreement for any such included software can be found at http://www.lua.org/copyright.html

Microsoft software

This Sophos product may include certain Microsoft software, licensed to Sophos for inclusion and use herein.

Mersenne Twister

Redistribution and use in source and binary forms, with or without modiﬁcation, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

The names of its contributors may not be used to endorse or promote products derived from this software without speciﬁc prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS

IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE

DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR

ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES

(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;

LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON

PureMessage for Microsoft Exchange 2013 and 2016

ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING

NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF

ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

OpenSSL

LICENSE ISSUES

===========

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to

OpenSSL please contact [email protected].

OpenSSL license

--------------------------------

=================================================================

Redistribution and use in source and binary forms, with or without modiﬁcation, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment:*

"This product includes software developed by the OpenSSL Project for use in the OpenSSL

Toolkit. (http://www.openssl.org/)"

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL

Toolkit (http://www.openssl.org/)"

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED

OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT

SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,

INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT

LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR

PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,

WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY

OF SUCH DAMAGE.

=================================================================

PureMessage for Microsoft Exchange 2013 and 2016

This product includes cryptographic software written by Eric Young ( [email protected]

). This product includes software written by Tim Hudson ( [email protected]

Original SSLeay license

)

This package is an SSL implementation written by Eric Young ( [email protected]

The implementation was written so as to conform with Netscapes SSL.

This library is free for commercial and non-commercial use as long as the following conditions are aheared to. The following conditions apply to all code found in this distribution, be it the

RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson

( [email protected]

If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used.

This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modiﬁcation

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

"This product includes cryptographic software written by Eric Young ( [email protected]

The word 'cryptographic' can be left out if the rouines from the library being used are not cryptographic related :-).

4. If you include any Windows speciﬁc code (or a derivative thereof) from the apps directory

(application code) you must include an acknowledgement:

"This product includes software written by Tim Hudson ( [email protected]

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED

WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT

SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES INCLUDING, BUT NOT LIMITED TO,

PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR

BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER

IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN

ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH

DAMAGE

The licence and distribution terms for any publically available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence [including the GNU Public Licence.]

PureMessage for Microsoft Exchange 2013 and 2016

protobuf

This license applies to all parts of Protocol Buffers except the following:

- Atomicops support for generic gcc, located in src/google/protobuf/stubs/ atomicops_internals_generic_gcc.h. This ﬁle is copyrighted by Red Hat Inc.

- Atomicops support for AIX/POWER, located in src/google/protobuf/stubs/ atomicops_internals_power.h. This ﬁle is copyrighted by Bloomberg Finance LP.

Redistribution and use in source and binary forms, with or without modiﬁcation, are permitted provided that the following conditions are met:

• Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

• Neither the name of Google Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without speciﬁc prior written permission.