• Aurea List Manager has a number of TCP and UDP connections it must establish for proper connectivity.
• If Aurea List Manager is going to be running behind a firewall, you need to configure your firewall so Aurea List Manager can send and receive mail properly.
• How are you planning to route SMTP, DNS, and web traffic in-and-out of Aurea List Manager?
• How are you going to have Aurea List Manager connect directly to the Internet or have it relay email through another server?
• For more information, see Your Firewall and ListManager and Ports ListManager Needs Open

• If you have a mail server on the same machine, you plan to install Aurea List Manager. You need to decide how you want to configure your mail server to coexist with ListManager.
• Aurea List Manager uses its mail server and does not need another. If there is no mail server on the machine on which you are installing Aurea List Manager, you need not worry about mail server coexistence.
• For each site, you may wish to set up distinct domain names (example lists.example.com). You need to have an MX record created for each distinct hostname that routes incoming email to Aurea List Manager (example email bounces, unsubscribes, list postings, and so on).
• For more information, see Mail server coexistence

• Aurea List Manager provides its proprietary webserver, and it is required to use and configure Aurea List Manager.
• Apache and IIS (Internet Information Services) are not required and cannot be used instead of the provided webserver.
• If some other webserver is already running on the machine where Aurea List Manager is being installed, the Aurea List Manager web interface should be installed on a different port.
• Aurea List Manager can be set up to have a stripped-down version of the webserver in a DMZ for handling interactions with the public and have a full administrative version of the webserver behind the firewall for internal use.
• Aurea List Manager can be setup to have a distinct URL for the web server that is used for handling opens, clickthroughs, clickstreams and action tags.
• A DNS A record that points to the IP address of the Aurea List Manager web server, provided for recipient interaction would be needed . It may be distinct from the Aurea List Manager webserver you are using for administrative purposes.
• For more information, see The ListManager Web Server

• Aurea List Manager uses the database provided to contain the data it needs to send and receive emails.
• Before installing Aurea List Manager, you need to install the client tools on the system on which Aurea List Manager is going to be installed.
• Aurea List Manager needs to use the libraries provided by the client tools for database connectivity.
• If you are using your SQL database server, you need to determine which database or instance to use for your Aurea List Manager tables or create one specifically for Aurea List Manager.

The following pre-requisites must be met while configuring the user/schema for Oracle database:

• Ensure you can connect from the Aurea List Manager host machine to the database using the client tools (Enterprise Manager, Query Analyzer for MSSQL[Microsoft Structured Query Language] or SQL*PLUS for Oracle).
• Character sets may be an issue (especially for Oracle). Aurea List Manager supports single-byte character sets (such as ISO8859P1 or equivalent Western European encoding).
• If you use UTF-8 (or another multi-byte character set) as your base character set, there is a risk of corruption of messages and other data.

See the following pages for database-specific information and setting up Aurea List Manager as a service.

• MSDE
• MicrosoftSQL
• Oracle
• Windows Services

• Routing mail to your internal mail servers can require some tuning of Aurea List Manager.
• Aurea List Manager typically performs its DNS resolution, starting with the root name servers and TLD (Top-Level Domain) name servers.
• When Aurea List Manager tries to resolve your internal email addresses, it tries to connect to the outside IP address of your corporate mail server, which may be blocked by your firewall. Add an MX entry to the DNS bypass area of Aurea List Manager to route mail to the internal IP address. For more information, see DNS Bypass

The following processes below needs to be identified before the Aurea List Manager installation.

• How are you currently sending mailings and maintaining a database of customers?
• How are you going to integrate Aurea List Manager into this environment?
• How your current mailings map onto Aurea List Manager's list and segmentation capabilities?

This manual contains details at the database level of how data is maintained. For information about the integration of Aurea List Manager, contact your account executive. If you do not know who your account executive is or for other queries, contact us through our website.

It is essential to make sure you download the right installer for your Aurea List Manager server operating system. There are different installers for each operating system/database combination. The installers are available at support.aurea.com.

Please have the following information ready regarding SQL:

Information about your SQL database, (if using your database and not the one included with Aurea List Manager):

• The name of your SQL machine.
• The SQL database server login or username (blanks allowed for MSSQL with integrated security).
• The SQL database password (blanks allowed for MSSQL with integrated security).
• The database name.
• Whether or not you have a mail server running on the ListManager machine. For more information, see MailServer Coexistence.
• The port the web interface on would reside on, if you already have a web server running (Unix only).
• Your Aurea List Manager serial code. If you don't have a serial code, contact your Lyris account representative.
• The email address and password of the server administrator.
• As the database password is saved unencrypted in a file in Aurea List Manager (lmcfg.txt), it is recommended to remove the password saved in this file and then specify that the password be provided on start-up by altering this file.