> ## Documentation Index
> Fetch the complete documentation index at: https://docs.levelblue.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Planning Your MailMarshal Installation

> Planning checklist, MailMarshal components, and standalone and array installation scenarios.

When planning to install MailMarshal, you should understand how MailMarshal manages email and the recommended installation scenarios based on your needs. This chapter provides information about these concepts and provides hardware requirements, software requirements, and planning checklists to help you through the planning process.

## Planning Checklist

Plan your MailMarshal installation by reading the following sections and completing the following checklist:

**Table 2: Planning checklist**

| Step | See Section |
| - | - |
| 1. Learn about important MailMarshal concepts. | [Understanding MailMarshal Components](#understanding-mailmarshal-components) |
| 2. Choose a *standalone* or *array* installation. | [Understanding Installation Scenarios](#understanding-installation-scenarios) |
| 3. *If you selected a standalone installation,* choose the appropriate configuration for your environment. | [Standalone Installation](#standalone-installation) |
| 4. *If you selected an array installation,* determine the number and location for the MailMarshal Servers and Array Manager components. | [Array Installation](#array-installation) |
| 5. Ensure the computers meet the hardware and software requirements. | [Standalone Installation Requirements](#standalone-installation-requirements) or [Array Installation Requirements](#array-installation-requirements) |
| 6. Determine whether to use Microsoft SQL Server or SQL Express (or Azure SQL for Azure installations). | [Database Software Considerations](#database-software-considerations) |
| 7. Decide where to install the MailMarshal folders. | [Understanding MailMarshal Folder Locations](#understanding-mailmarshal-folder-locations) |
| 8. Choose the antivirus software to use with MailMarshal. | [Supported Antivirus Software](#supported-antivirus-software) |
| 9. Collect installation information about your email environment. | [Collecting Information for Installation](#collecting-information-for-installation) |

## Understanding MailMarshal Components

MailMarshal consists of several software components, which you can install on different computers in your network. These components can be installed in a variety of configurations to suit any size organization from small businesses to distributed enterprises. Figure 1 shows the components on separate computers for clarity. In lower volume scenarios you can install all components on a single computer.

![MM Components](https://mintcdn.com/levelblue-5324744e/6N3JHLQxs6ryQUu7/images/MM_components.png?fit=max\&auto=format\&n=6N3JHLQxs6ryQUu7\&q=85\&s=84fab66ed2833dc699ff9a5d7201ff3d)

### MailMarshal Components

MailMarshal includes the following components:

**Processing Server**

Accepts incoming email subject to Connection Policy (Receiver), applies Content Analysis Policy in the form of rules (Engine), and forwards email to your email server or to the recipient (Sender). You can use one or more MailMarshal Servers in your installation.

**Array Manager**

Manages an *array* of MailMarshal email processing servers. The Array Manager connects to the email processing servers and to the database, hosted using Microsoft SQL Server or SQL Express. The Array Manager server also hosts the Configuration Service and an instance of Microsoft IIS, used by the Management Console. For more information, see [Other Software and Services](#other-software-and-services).

**Management Console**

Web-based interface allowing Administrator access. Administrators can define policy (rules), configure MailMarshal, and manage and monitor undelivered or filtered email.

**Spam Quarantine Management Website**

Optional Web-based interface for internal email users to view and manage quarantined email.

**Marshal Reporting Console**

Optional Web-based interface used to generate traffic and management reports based on MailMarshal activity.

To operate properly, MailMarshal requires an Array Manager (with Management Console), at least one email processing Server, and a database server (hosting the product database and configuration service database). You can optionally install the Spam Quarantine Management website and the Marshal Reporting Console if you plan to use the additional features these components offer.

### Other Software and Services

In addition, MailMarshal may require the following software and network services:

**Microsoft SQL Server, SQL Express, or Azure SQL Server**

The MailMarshal database stores configuration data and log information. If your email volume permits, you can use the free SQL Express. If your email volume is higher, use Microsoft SQL Server. If possible, install the database software and the MailMarshal Array Manager on the same computer. For more information, see [Array Installation Requirements](#array-installation-requirements) and [Database Software Considerations](#database-software-considerations).

If your MailMarshal installation is hosted on an Azure server, you can use Azure SQL to host the database. Due to latency, you should not attempt to use Azure SQL with a locally hosted MailMarshal installation.

**Microsoft Internet Information Services (Microsoft IIS)**

If you want to offer the end-user Spam Quarantine Management Website, install the MailMarshal Web Components on a server with Microsoft IIS and .NET 4.0 installed.

## Understanding Installation Scenarios

While you can configure MailMarshal to run in many environments, there are two basic configurations to consider, based on the number of users and your typical email volume:

* Standalone, or basic installation (several variations available)
* Array installation

The **standalone installation** scenario is appropriate for small to mid-size organizations with a lower volume of email. This option allows smaller organizations to gain all the benefits of using MailMarshal to reduce email volume and block annoying and costly spam.

The **array installation** is appropriate for larger, distributed organizations where email volume is high, or where use of a Demilitarized Zone (DMZ) is necessary. This option provides all the security and efficiency options larger organizations require.

For more information about determining your configuration needs, see the Technical Reference titled "MailMarshal Sizing Guide" at LevelBlue.com, or contact your Technical Support representative.

### Standalone Installation

For small to medium-sized organizations, a standalone installation provides convenience and value. In a standalone installation, you install all the MailMarshal components as well as the SQL Express or Microsoft SQL Server database on a single computer.

To use the MailMarshal Spam Quarantine Management Website or Marshal Reporting Console, install these components on a Microsoft IIS Server.

You can configure a standalone installation of MailMarshal in the following ways:

* As a POP3/SMTP server *(for very small organizations)*
* As an internal email relay to your email server
* On your existing email server

Each option provides all the required functions of an email gateway. Other variations are also possible.

#### MailMarshal as Email Server

You can install MailMarshal to function as a POP3/SMTP email server, providing all email server functions for a small organization, as shown in Figure 2.

![Mm Standalone](https://mintcdn.com/levelblue-5324744e/x21QTv9fJshn3W3y/images/mm-standalone.png?fit=max\&auto=format\&n=x21QTv9fJshn3W3y\&q=85\&s=90ce9f7a30c1e33485b5b0f9907772aa)

In this scenario, MailMarshal receives and processes all incoming email. MailMarshal receives email on port 25 from within the organization and delivers email to internal POP3 mailboxes on port 110. MailMarshal receives and sends email to and from external addresses over your Internet link.

For this configuration, install the Server and Array Manager components on a single computer. Most organizations that choose this configuration can also install Microsoft SQL Server or SQL Express on the same computer to host the MailMarshal database.

#### MailMarshal as an Internal Email Relay

You can install MailMarshal on a separate computer to act as an email relay within an organization, as shown in Figure 3.

![Mm Sepserver](https://mintcdn.com/levelblue-5324744e/x21QTv9fJshn3W3y/images/mm-sepserver.png?fit=max\&auto=format\&n=x21QTv9fJshn3W3y\&q=85\&s=c0695905f5176ff34922a635fc8a14e5)

This option is suitable for small to medium-sized organizations with a single Internet gateway and email server. In this scenario, the MailMarshal Server receives inbound email on port 25, processes it, and forwards it for delivery to the existing email server. The email server forwards all outbound messages to the MailMarshal Server for processing and delivery.

For this configuration, install the MailMarshal Server and Array Manager components on a separate computer from the existing email server. Set the Domain Name Service Mail Exchange (DNS MX) records or firewall relay settings so the MailMarshal Server receives all inbound email.

Most organizations that choose this configuration can also install Microsoft SQL Server or SQL Express on the same computer to host the MailMarshal database.

#### MailMarshal on Existing Email Server

You can install MailMarshal on your existing email server computer, as shown in Figure 4.

![Mm Sameserver](https://mintcdn.com/levelblue-5324744e/x21QTv9fJshn3W3y/images/mm-sameserver.png?fit=max\&auto=format\&n=x21QTv9fJshn3W3y\&q=85\&s=410a6821349ca2d4a3f441490dd7e237)

MailMarshal receives all inbound email on default SMTP port 25, processes the email, and forwards email to the existing email server using the `localhost` IP address on port 97 for delivery. The existing email server forwards outbound email to MailMarshal on port 25 using the `localhost` IP address.

In this case, your email server must have sufficient resources to support both MailMarshal and another email server application. Install the MailMarshal Server and Array Manager components on your existing email server. Many organizations that choose this configuration can also install Microsoft SQL Server or SQL Express on the same computer to host the MailMarshal database.

When you install MailMarshal on the same physical server as the existing email server software, normally you do not need to change the inbound routing. However, because MailMarshal takes on the role of listening for SMTP traffic on port 25, you must configure your existing email server to listen for SMTP traffic on another port. Many organizations use port 97 for this purpose, but you can configure your existing email server to listen on any free TCP port.

This configuration is not suitable if you have multiple internal email servers (SMTP or Exchange). With multiple internal email servers, install MailMarshal on a separate computer as an email relay. For more information, see [MailMarshal as an Internal Email Relay](#mailmarshal-as-an-internal-email-relay).

### Array Installation

You can install an array of MailMarshal Servers in a variety of configurations to manage email for larger enterprises. MailMarshal provides a broad range of enterprise configurations that can include redundancy and failover support. Figure 5 shows a typical MailMarshal array configuration.

![Mm 60](https://mintcdn.com/levelblue-5324744e/x21QTv9fJshn3W3y/images/mm-60.png?fit=max\&auto=format\&n=x21QTv9fJshn3W3y\&q=85\&s=31b62b56d957cb047f5cdd64cefd4b05)

In this scenario, you can install the MailMarshal Server component on a number of computers to create an array of MailMarshal email processing servers in a Demilitarized Zone (DMZ). The DMZ is a part of a local network that has controlled access both to the Internet and to the internal network of the organization.

To provide load balancing, you can install the email processing servers in a cluster using third-party software, such as a Datacenter Server.

A distributed enterprise with more than one email gateway can install one or more MailMarshal Servers at each gateway. If you use the same email policy at all locations, you can control the MailMarshal configuration and perform logging for all gateways using a single MailMarshal Array Manager. All MailMarshal Servers must be able to communicate with the Array Manager computer over port 19001.

The MailMarshal Servers receive all incoming email on port 25. MailMarshal Servers transfer email to and from local email servers on port 25. The MailMarshal Array Manager requires a single port opening to the DMZ to configure the MailMarshal Servers and receive log data (port 19001 by default).

Install the MailMarshal Array Manager, and the database if possible, on a dedicated computer inside the trusted network. The location of the Array Manager can affect the performance of the administration and configuration tools used in MailMarshal, but does not affect email processing performance.

For best results, install the MailMarshal Array Manager component in one of the following locations, listed from most-preferred to least-preferred:

* On the same server as the Microsoft SQL Server hosting the database. Since the Array Manager is the only MailMarshal component that communicates directly with the database, installing the Array Manager on the computer that hosts Microsoft SQL Server or SQL Express results in the most efficient operation.
* On another computer in the network close to the computer hosting the database over a high-speed network connection.
* On an Active Directory Global Catalog or other Directory Server. The Array Manager communicates regularly to the Global Catalog if you are running Active directory, or through LDAP to another existing Directory Server.
* The MailMarshal Management Console website is installed on the Array Manager server and can be accessed by web browser clients.
* To use the MailMarshal Spam Quarantine Management Website or Marshal Reporting Console, install these components on a Microsoft IIS Server domain member inside the network.

## Hardware and Software Requirements

Depending on the installation scenario you select and your estimated email volume, the specification for computers on which you install MailMarshal components can vary. The following sections specify the recommended hardware and software for various computers where you may be installing MailMarshal components. Consider all the requirements before mapping your MailMarshal installation.

> [!TIP]
>
> **Tip:** Additional information is available in the MailMarshal Sizing Guide.

The MailMarshal installation package includes many prerequisite software updates, including SQL Express and .NET Framework. If you install MailMarshal from a Web download, you may have to download software you need from the vendor sites. To avoid a system restart during product installation, install any prerequisite software on your computers before you start installing MailMarshal.

For more information about the latest requirements and supported environments, see the LevelBlue Knowledgebase.

### Standalone Installation Requirements

In standalone installations, computer requirements for the MailMarshal components may vary depending on whether you use MailMarshal as the POP3 email server or relay, or if you plan to install MailMarshal on an existing email server.

The following table lists system requirements for installing the MailMarshal Server, Array Manager, and selected database on a single computer.

MailMarshal supports use of SQL Express or Microsoft SQL Server as host database.

If you install MailMarshal on an existing email server, the minimum hardware requirements may be greater than those shown in the table, depending on the number of users and typical email volume.

**Table 3: Standalone installation requirements**

| Category | Requirements |
| - | - |
| Processor | **Minimum**: Core i5 or similar performance |
| Disk Space | **Minimum**: 20GB (NTFS) |
| Memory | **Minimum**: 7GB (Includes 1 GB for operating system and 2GB for SQL) • Minimum 5 GB if the database is hosted on another server |
| Supported Operating System | • Windows Server 2025 • Windows Server 2022 • Windows Server 2019 • Essentials Edition or above • Windows 11 (Only for smaller installations and not recommended) |
| Network Access | • TCP/IP protocol • Domain structure • External DNS name resolution: DNS MX record to allow MailMarshal Server to receive inbound email |
| Software | • Microsoft .NET Framework 4.6.2 (or later 4.X)   ◦ .NET 8 is also used but is included in the MailMarshal installer • Microsoft IIS for Management Console.   ◦ Windows Authentication is required. • Database server: *Use of full licensed SQL Server is not recommended for standalone installations due to resource contention issues.* Use SQL 2025 Express, SQL 2022 Express, SQL 2019 Express, or SQL 2017 Express. For cloud installations you can use Azure SQL Server. For more information about database considerations, see [Database Software Considerations](#database-software-considerations). SQL Server versions have additional prerequisites, including minimum Operating System versions. • Antivirus scanning software supported by MailMarshal. For more information, see [Supported Antivirus Software](#supported-antivirus-software). • Web browser (for Management Console connection): Chrome, Edge, Firefox, or Safari. |
| Port Access | • Port 25: Inbound SMTP and to email servers • Port 53: for DNS external email server name resolution (TCP and UDP) • Port 80 (HTTP) and Port 443 (HTTPS) outbound: for SpamCensor and SpamProfiler updates, and CRL checking for TLS if TLS is in use (Proxy usage is supported) • Port 443 (HTTPS) inbound: for client connections to the MailMarshal Management Console • Port 1433: for connection to SQL Server database and Marshal Reporting Console computers • If installed on an existing email server: Port 97 or another available port, for email transfer between MailMarshal and the other software • If serving as a POP3 email server: Port 110, for email transfer to POP3 mailboxes |

When processing large volumes of email, disk I/O can become a limitation. To provide optimal throughput in this case, plan to include dual drives so you can install the MailMarshal Server components on one drive and the database and Unpacking folder on a separate physical drive. For more information about choosing folder locations, see [Understanding MailMarshal Folder Locations](#understanding-mailmarshal-folder-locations).

To provide redundancy, plan for quad drives configured as two mirrored pairs. For more information to determine your configuration needs, see the Technical Reference titled "MailMarshal Sizing Guide" at LevelBlue.com.

### Array Installation Requirements

In an array installation scenario, you may plan for several MailMarshal Servers and one Array Manager computer. The following sections provide hardware and software requirements for MailMarshal Server and Array Manager computers.

For more information to determine your specific requirements, see the "MailMarshal Sizing Guide" Technical Reference, at LevelBlue.com.

#### Server Requirements

The following table lists system requirements for a MailMarshal email processing server computer in an array configuration.

**Table 4: Array Server installation requirements**

| Category | Requirements |
| - | - |
| Processor | **Minimum**: Core i5 or similar performance |
| Disk Space | **Minimum**: 20GB (NTFS) |
| Memory | **Minimum**: 10GB (includes 2GB for operating system) |
| Supported Operating System | • Windows Server 2025 • Windows Server 2022 • Windows Server 2019 • Essentials Edition or above • Windows 11 (Only for smaller installations and not recommended) |
| Network Access | • TCP/IP protocol • Domain structure • DNS service available |
| Software | • Microsoft .NET Framework 4.6.2 (or later 4.X) • Antivirus scanning software supported by MailMarshal. For more information, see [Supported Antivirus Software](#supported-antivirus-software). • Web browser (for Management Console connection): Chrome, Edge, Firefox, or Safari. |
| Port Access | • Port 25: Inbound SMTP and email forwarding to email servers in trusted network • Port 53: DNS external email server name resolution (TCP and UDP) • Port 80 (HTTP) and Port 443 (HTTPS): for SpamProfiler updates, and CRL checking for TLS if TLS is in use (Proxy usage is supported) • Port 19001: Communication with MailMarshal Array Manager in the trusted network |

When processing large volumes of email, disk I/O can become a limitation. To provide optimal throughput in this case, you may want to plan for dual drives in the MailMarshal Server computer so you and install Server components on one drive and the Unpacking folder on a separate physical drive. For more information about choosing folder locations, see [Understanding MailMarshal Folder Locations](#understanding-mailmarshal-folder-locations).

To provide redundancy, you may want to plan for quad drives configured as two mirrored pairs. For more information about determining your configuration needs, see the "MailMarshal Sizing Guide" Technical Reference at LevelBlue.com

#### Array Manager Requirements

The following table lists system requirements for a MailMarshal Array Manager computer also hosting the Management Console website and SQL Express or Microsoft SQL Server database.

**Table 5: Array Manager Server requirements**

| Category | Requirements |
| - | - |
| Processor | **Minimum**: Core i5 or similar performance |
| Disk Space | **Minimum**: 20GB (NTFS) and additional space depending on database retention |
| Memory | **Minimum**: 10GB (includes 2GB for operating system and 2GB for SQL) |
| Supported Operating System | • Windows Server 2025 • Windows Server 2022 • Windows Server 2019 • Essentials Edition or above • Windows 11 (Only for smaller installations and not recommended) |
| Network Access | • TCP/IP protocol • Domain structure • DNS service available |
| Software | • Microsoft .NET Framework 4.6.2 (or later 4.X)   ◦ .NET 8 is also used but is included in the MailMarshal installer • Microsoft IIS for Management Console   ◦ Windows Authentication is required • Database server: SQL 2025, SQL 2022, SQL 2019, SQL 2017; SQL 2025 Express, SQL 2022 Express, SQL 2019 Express, SQL 2017 Express. Azure SQL Server can be used where MailMarshal is installed on Azure. For more information about database considerations, see [Database Software Considerations](#database-software-considerations). SQL Server versions have additional prerequisites, including minimum Operating System versions. • Antivirus scanning software supported by MailMarshal. For more information, see [Supported Antivirus Software](#supported-antivirus-software). |
| Port Access | • Port 80 (HTTP) and Port 443 (HTTPS) outbound: SpamCensor updates (Proxy usage is supported) • Port 443 (HTTPS) inbound: Client access to the MailMarshal Management Console website • Port 1433: Connection from Marshal Reporting Console computers • Port 19001: Communication with MailMarshal Servers in DMZ • Port 19006 (HTTPS): Communication from any applications using the REST API • Port 19007 (HTTPS): Communication from the MailMarshal Management Console or other applications using the MailMarshal Config Service |

### Web Components Requirements

To use the MailMarshal Spam Quarantine Management Website, install the MailMarshal Web Components on a computer running Microsoft Internet Information Services (Microsoft IIS). The following table lists system requirements and recommendations for the computer running Microsoft IIS.

**Table 6: Web Components Server requirements**

| Category | Requirements |
| - | - |
| Processor | **Minimum**: Core i5 or similar performance |
| Disk Space | **Minimum**: 100MB **Recommended**: 500MB |
| Memory | **Minimum**: 512MB **Recommended**: 1024MB |
| Supported Operating System | • Windows Server 2025 • Windows Server 2022 • Windows Server 2019 • Essentials Edition or above • Windows 11 (Only for smaller installations and not recommended) |
| Network Access | • TCP/IP protocol • Domain structure • DNS service available |
| Software | • Microsoft .NET Framework 4 • IIS Features (in addition to features installed by default):   ◦ ASP.NET   ◦ Basic Authentication   ◦ Windows Authentication |
| Web Browsers *(Tested and supported)* | • Internet Explorer, Mozilla Firefox, Google Chrome, and Safari (current versions) |
| Port Access | • Port 19001: Communication with MailMarshal Array Manager |

Use a secure (HTTPS) website to protect user data and authentication information.

> [!WARNING]
>
> **Caution:** As best practice for security, do not install the Spam Quarantine Management website on a server exposed to the Internet.

There are additional requirements to install Web components on a computer running a Windows Domain Controller. For more information, see the LevelBlue Knowledgebase.

## Database Software Considerations

MailMarshal supports use of SQL Express or Microsoft SQL Server. To estimate the size of your MailMarshal database and determine whether to use SQL Express or Microsoft SQL Server, review the following sample worksheet, and then complete My Worksheet (Table 8) with appropriate estimates.

**Table 7: Sample database worksheet**

| Sample Worksheet | | |
| - | - | - |
| Number of users | = | 100 |
| Average number of valid and quarantined email messages per user per day | x | 70 |
| Kilobytes per message or classification logged (1KB = 1000 Bytes) | x | 2 |
| Number of days in log data retention period | x | 100 |
| Safety margin | x | 1.25 |
| Total database size in Kilobytes for retention period | = | 1,750,000 KB |
| Total database size in Gigabytes for retention period (divide by 1,000,000) | = | 1.75 GB |

> [!NOTE]
>
> **Note:** Each record in the Message table (quarantine, classification or delivery record) adds approximately 1.1KB to the database (depending on the size of data) Indexing on the Message table adds a smaller but significant amount. The Content table (logging of attachments) can also consume significant space, depending on the average number of attachments per message.

**Table 8: Database worksheet for your environment**

| My Worksheet | | |
| - | - | - |
| Number of users | = | |
| Average number of valid and quarantined email messages per user per day | x | |
| Kilobytes per message logged (1KB = 1000 Bytes) | x | 3 |
| Number of days in log data retention period | x | |
| Safety margin | x | |
| Total database size in Kilobytes for retention period | = | |
| Total database size in Gigabytes for retention period (divide by 1,000,000) | = | |

The following table shows calculations with example data you can use as a guideline if the assumptions for email volume, log retention duration, and safety margin are appropriate for you.

**Table 9: Database sizing calculations**

| Users | Email/Day/User | Days to Keep Logs | Safety Margin | GB (Rounded) | Database Version |
| - | - | - | - | - | - |
| 100 | 70 | 100 | 1.25 | 2 | Express |
| 200 | 70 | 100 | 1.25 | 3.5 | Express |
| 250 | 70 | 100 | 1.25 | 4.5 | Express |
| 500 | 70 | 100 | 1.25 | 9 | Express |
| 1000 | 70 | 100 | 1.25 | 20 | SQL |
| 2000 | 70 | 100 | 1.25 | 35 | SQL |
| 5000 | 70 | 100 | 1.25 | 90 | SQL |

For small installations, when the MailMarshal email processing server is on a computer other than the Array Manager and database server, the database server will have a light load on the database. However, using the Consoles and Reports user interfaces places additional load on the database.

If you have more than 500 email users, the Microsoft SQL Server memory footprint can become quite high. In this case, you can add memory to the Microsoft SQL Server computer (3GB or more) so Microsoft SQL Server can use its maximum available memory and still reserve memory for the Array Manager, operating system, and other system demand. Other environment factors may also affect performance and throughput rates. For large installations, consider using multiple disk drives for the various database files to optimize SQL Server performance.

> [!NOTE]
>
> **Note:** SQL Server, in particular 64 bit versions, will consume all available system memory by default. You may need to limit SQL memory usage. See Knowledgebase article Q14902.

## Understanding MailMarshal Folder Locations

By default, the installation process creates several folders in the MailMarshal program installation folder. For many cases, the default folder locations work well.

In some cases, you can enhance product performance by creating these folders on another local physical hard drive. You can choose different locations on each email processing server. The folders are defined as follows:

**Logging**

MailMarshal uses this folder to store text logs that provide details of each action taken by each MailMarshal service. By default, MailMarshal retains logs for five days. The files can be large when email volume is high

> [!NOTE]
>
> **Note:** Compressing this folder with Windows file system compression reduces the disk space required and does not affect performance in most cases. Do not use compression for any other MailMarshal folders.

**Queues**

MailMarshal uses this folder and sub folders to hold messages for processing or sending. In most cases, these folders do not grow large. However, if MailMarshal cannot connect to upstream or downstream servers, the data in the folders can grow quickly.

**Unpacking**

MailMarshal uses this folder to unpack messages and extract their content, including attachments such as archive files. The size of this folder is relatively small. Because the Server creates and deletes files repeatedly, this area of the disk can become fragmented, which can have an adverse effect on other applications running on the server. You can improve performance by placing this folder on a separate physical disk drive from other MailMarshal components.

**Quarantine**

MailMarshal uses this folder as the default location for all quarantine folders. MailMarshal stores all quarantined messages in sub folders of this folder, including any archived messages, dead-lettered messages that could not be processed fully, and messages in the Mail Recycle Bin. Ensure the disk drive where this folder resides has enough free space to accommodate the messages. The space required varies depending on your retention policies for quarantined messages. You can move individual folders to physically separate places on the server. For more information, see [Working with Folders](/documentation/mailmarshal/user-guide/email-policy-elements.md#working-with-folders).

> [!NOTE]
>
> **Note:** MailMarshal does not accept new messages if there is less than 512MB of free disk space available for the Queues, Unpacking, Quarantine, or Logging folders. MailMarshal slows down mail acceptance if there is less than 1GB of free space available for these folders. This is a significant increase in required space from earlier versions.
>
> For more information, see Knowledgebase article Q11669.

## Supported Antivirus Software

MailMarshal supports a number of third-party antivirus scanners to scan for virus or malware laden email. The scanners offering a MailMarshal specific DLL file offer much higher throughput and enhanced features. Command line scanners are suitable for basic scanning in relatively small organizations.

LevelBlue licenses the Marshal antivirus solutions separately from the MailMarshal product. Trial versions of the Marshal antivirus solutions are available from the installation package or as downloads from LevelBlue.com.

MailMarshal actively supports the antivirus software brands listed in the following table. For more information about currently supported versions, see Knowledgebase article Q10923.

**Table 10: Supported Antivirus scanners**

| Antivirus Application | Features |
| - | - |
| Bitdefender for Marshal | DLL |
| McAfee for Marshal | DLL |
| Sophos for Marshal | DLL |
| Computer Associates AntiVirus (formerly eTrust EZAntiVirus or InoculateIT) | Command line scanner |
| McAfee Command Line | Command line scanner |
| NOD32 Command Line | Command line scanner |

> [!NOTE]
>
> **Notes:**
>
> * The Sophos (SAVI interface) and Symantec scanners that were previously supported are not supported in this release, as the required 64-bit integration is not currently available.
> * Kaspersky for Marshal is no longer sold.

## Collecting Information for Installation

Before you install MailMarshal, you may want to collect the following information about your environment. When you run the Configuration Wizard after you install the product, having the following details handy can help you quickly configure MailMarshal.

**Table 11: Information required for installation**

| Information required | My information |
| - | - |
| Names of computers where you plan to install MailMarshal components including: Servers, Array Manager/Management Console, database, and optionally, SQM and Marshal Reporting Console. | |
| Prerequisite software for each computer where you will install software and the best time to restart each system, if necessary. | |
| DNS server administrator of domains for which MailMarshal will process email and best time to make and propagate DNS changes. | |
| Firewall administrator contact information, and best time to make and propagate firewall settings changes. | |
| Antivirus software to use with MailMarshal. | |
| Company name for MailMarshal license. | |
| Names of local domains for which MailMarshal will process email (for example, `mycompany.com` or `pop.mycompany.com`) | |
| IP address and access port for your existing Microsoft SQL server computer. | |
| IP address and access port for your existing local email server. | |
| If using POP3 mailboxes, decide how to route email for undefined accounts. | |
| Logon credentials for your directory server (Azure Entra, Active Directory or LDAP). IP address of the LDAP server. | |
| Email address where MailMarshal will send administrator notification emails (existing or new account). | |
| Email address email notifications to recipients will be from (reply to address) (existing or new account). | |
| IP addresses of primary and optional secondary DNS servers MailMarshal will use for internal and external domain name resolution. | |
| Server name, fully qualified domain name, or IP address of host and optional alternate to forward external email. | |
| Existing outbound delivery details and required routing changes. | |
| Existing inbound delivery details and required routing changes. | |