Section 5 Prepare LISTSERV Maestro for First Use

The following subsections discuss steps that you need to perform in order to prepare a fresh installation of LISTSERV Maestro for first use. If you have already provided default values for certain Administration Hub settings during the installation process, or if you have upgraded an existing installation, some of these steps may not be necessary. Read through the sections anyway, because some steps may deal with new features that were not previously available and therefore must be performed even after an upgrade of an existing installation.

5.1 First Steps with the LISTSERV Maestro Sample Account

LISTSERV Maestro is installed with a pre-defined example account. You can access this account by opening the Maestro User Interface and logging in with the user name “sample”, and the password “sample” (no group name). The sample account contains two example jobs in the list of delivered jobs, one plain text and one HTML mail job, along with the collected tracking data from these jobs, viewable with three pre-defined tracking reports. Feel free to browse through these jobs and their tracking data and to create some “test-jobs” of your own by using the sample jobs as starting points (making copies of the sample jobs).

The sample account also contains one example dataset with an example newsletter recipient list, which you may browse through and experiment with to try out the recipient warehouse features. (Note, that the recipients on the sample list are dummy recipients with addresses that will all bounce back to the sender, should you actually try to deliver a mail job to these recipients.)

Important Security Note: Since the existence of this example account is well known to most users of LISTSERV Maestro, change the password of this account before making your Maestro User Interface accessible to the public. Alternatively, you may delete the account. After deleting the account, you may then log in as an Administrator to assign the sample jobs and the sample dataset to a different account that you create yourself (see the LISTSERV Maestro Administrator’s Manual for more details).

5.2 Configuring LISTSERV Maestro for First Use

After installation (or after upgrading) you may still have to execute a few initial configuration steps in the Administration Hub before you can fully use LISTSERV Maestro. Access the Administration Hub with a browser, using its access URL (see above), and log in with the administrator password. The default password after a fresh installation is “admin”.

Note: The following sub-sections describe only a small subset of the available configuration settings in the Administration Hub. Please see the LISTSERV Maestro Administrator’s Manual for a complete description and for more details.

If you have already supplied defaults for some of the Administration Hub settings during the installation process itself, then some of the configuration steps below are no longer necessary.

5.2.1 Administrator Password

It is recommended that you change the administrator password to something other than the default “admin” immediately after installation. Do not forget the new password, it is not recoverable!

5.2.2 Maestro User Interface Runtime Settings

Before you can fully use all features of the Maestro User Interface, you need to configure some basic settings, which you can do either on account/group level or as application wide defaults:

· For application wide defaults, go to the Maestro User Interface default settings menu by clicking on Global Component Settings, then on Maestro User Interface.

· For account-specific settings of a non-group account, go to the Maestro User Interface settings menu by clicking on Administer User Accounts. Select the name of the account for which you want to define the settings, then click on Maestro User Interface.

· For group-specific settings, go to the Maestro User Interface settings menu by clicking on Administer User Accounts, then on the name of the group for which you want to define the settings.

· For account-specific settings of a group account, go to the Maestro User Interface settings menu by clicking on Administer User Accounts. Select the name of the account for which you want to define the settings, then click on Maestro User Interface. Note that for group accounts, only a few selected settings are definable on an account level. Most settings are only definable on the group level for the associated group (see below) and therefore apply to all accounts in that group.

Account-specific settings apply only to the account for which they are defined. Group-specific settings apply to all accounts in the group that are not overridden by settings on the account level. Application wide default settings apply to all accounts that are not overridden by settings on the group or account level.

The following sub-sections describe the most important settings that you need to define in order for the Maestro User Interface to work properly. You can define all of these settings on the account/group level or as application-wide defaults.

5.2.2.1 LISTSERV Connection

The LISTSERV connection settings are necessary to make the Maestro User Interface aware of the LISTSERV instance with which it is supposed to collaborate.

Since this setting can be defined individually for accounts/groups, you can connect the Maestro User Interface to separate LISTSERV instances (even in parallel), depending on which account is currently logged in and using the Maestro User Interface. You do so by defining each account’s/group’s individual LISTSERV connection settings.

If, on the other hand, you have only a single LISTSERV instance that you want to share among all accounts, then it is easiest to configure this LISTSERV instance as the application-wide default and leave the settings of the individual accounts and groups empty.

To configure the LISTSERV connection, either go to the Maestro User Interface settings menu of the desired account/group, or go to the Maestro User Interface default settings menu (see above). Then, click on LISTSERV Connection /Default LISTSERV Connection.

Enter information for the following parameters:

· LISTSERV Host: The host name of the server running the LISTSERV component. This LISTSERV host will be used for the following purposes:

· Delivery of all mail jobs sent with the account(s) to which this setting applies.

· Bounce reporting for all jobs sent with the account(s) to which this setting applies (unless a dedicated bounce handling server is defined – see the LISTSERV Maestro Administrator’s Manual for more details).

· Creation and maintenance of all Hosted LISTSERV Lists created with the account(s) to which this setting applies (in case the Hosted LISTSERV Lists feature is used – see Section 5.3 Preparing LISTSERV Maestro for Hosted Lists for more details).

· External Host Name: If the LISTSERV host is known externally with a different host name than the one above, enter this external host name here (see the LISTSERV Maestro Administrator’s Manual for more details).

· LISTSERV TCPGUI Port: The port number on the LISTSERV host on which the LISTSERV component accepts TCPGUI connections (the standard port is 2306).

· Client Address for Mail Delivery and Bounce Reporting: The address you configure here is used by the Maestro User Interface when transferring a mail job to the LISTSERV host configured above and when retrieving bounce information from that LISTSERV host.

· Address: An e-mail address that is known to the LISTSERV host configured above either as a postmaster address or as an address that is listed under the LISTSERV configuration parameter “DIST_ALLOWED_USERS”, meaning an address that has the DISTRIBUTE right.

· Password: The address’ password, associated with it at the LISTSERV component. Please see the LISTSERV documentation about how to set a personal password for an e-mail address. (In short: Send a plain-text mail to “listserv@LISTSERV_HOST”, with “PW ADD your_password” in the mail body, and the e-mail address to which you want to assign the password as the sender address of the message.)

Note: This address and password are used internally for the communication between the Maestro User Interface and LISTSERV in order to transfer mail jobs to LISTSERV for sending or to read bounce information from LISTSERV. This transfer includes an authentication of the client accessing LISTSERV using the given e-mail address and password.

· Client Address for LISTSERV Server Administration: The address configured here is used by the Maestro User Interface to communicate with the LISTSERV host to perform server administrative tasks.

· Address: An email address that is known to the LISTSERV configured above as a postmaster address.

· Password: The address’ password, associated with it at the LISTSERV component. (See above for details about how to set a password for an address.)

Note: This address is only used internally for the communication between the Maestro User Interface and LISTSERV for server administrative tasks. These tasks include an authentication of the client accessing LISTSERV using the given e-mail address and password.

5.2.2.2 Tracking URL

The tracking URL is necessary to enable the mail tracking functionality of LISTSERV Maestro. Without a tracking URL, you can still create and send mail jobs, but you cannot enable tracking for them.

Since this setting can be defined individually for accounts/groups, you can make LISTSERV Maestro use different tracking URLs (even in parallel) depending on which account is currently logged in to the Maestro User Interface. You do so by defining each account’s/group’s individual tracking URL settings.

If, on the other hand, you have no reason to use different tracking URLs for different accounts or groups, then it is easiest to configure the tracking URL as an application wide default and leave the settings of the individual accounts and groups empty.

To configure the tracking URL, go to the Maestro User Interface settings menu of the desired account/group, or go to the Maestro User Interface default settings menu (see above). Then, click on Tracking URL/Default Tracking URL.

Enter information for the following parameters:

· Tracker Host: Enter the host name of the server running the Maestro Tracker component. This must be a DNS-registered host name that can be used by external clients to access the server from the Internet.

· HTTP Port: Enter the HTTP port used by the server running the Maestro Tracker component. This must be the port that external clients from the Internet must use for HTTP connections to the server.

Note: In a proxy environment, the Tracker Host and HTTP Port as seen by external clients may be different from what the actual Maestro Tracker component server uses internally. Please see the LISTSERV Maestro Administrator’s Manual for details about a proxy environment or when using host name aliases.

5.2.2.3 User Accounts

This step is usually only executed after you are done testing the system with the predefined sample account (see above) and are ready to use the system with your own accounts. Create at least one user account that you can then use to access the Maestro User Interface. Click on Administer User Accounts, and then on Add User Account. Next, enter the account name (and, optionally, group) and the password. Click on [OK].

If you do not want the account to use the default LISTSERV connection settings and/or default tracking URL settings, (or if you have not configured such defaults) you need to configure individual connection and tracking URL settings for the account. See the previous sub-sections on how to configure these settings on the account/group level.

5.3 Preparing LISTSERV Maestro for Hosted Lists

The recipient warehouse of LISTSERV Maestro allows you to store and maintain your recipient lists (and all recipient profile values) directly inside of LISTSERV Maestro, without the need for additional software.

The recipient warehouse allows you to created hosted lists of two types:

· Hosted Recipient Lists

· Hosted LISTSERV Lists

Each of these recipient list types has its own set of special features. Please see the documentation for LISTSERV Maestro for more details.

To use hosted lists in general, you will have to perform the following steps (or confirm that they have been performed earlier). For each of the steps below, see the following sub-sections for details:

1. Enable Usage of Hosted Lists
In a freshly installed LISTSERV Maestro, usage of Hosted Lists is already enabled by default. However, after an upgrade from an older version, where this feature may have been disabled or was not yet available, it may be necessary to enable their usage in the Administration Hub.

2. Grant “Data Administrator” Right
Even after usage of hosted lists has been enabled in general, only accounts that are granted the right to administer hosted recipient datasets are actually allowed to use the feature.

If you want to use hosted lists of the type Hosted Listserv List, you will also have to perform these additional steps (or confirm that they have been performed earlier). Again, see the following sub-sections for details about each step:

3. Define Database Server in LISTSERV
If Hosted LISTSERV Lists are to be used, then the LISTSERV host configured in the LISTSERV connection settings of the corresponding account/group needs to be connected to the system database of LISTSERV Maestro.

5.3.1 Enable Usage of Hosted Lists

If you want to use hosted lists, confirm that their usage has been enabled in the Administration Hub (this is by default the case in a freshly installed LISTSERV Maestro):

Log into the Administration Hub and go to the Maestro User Interface settings menu of the desired account/group, or go to the Maestro User Interface default settings menu (see above). Next, click on Hosted Data Settings/Default Hosted Data Settings.

The Hosted Data Settings screen allows you to selectively enable or disable creation of Hosted Recipient Lists and/or Hosted LISTSERV Lists. Only accounts to which one of the enabled creation rights apply will be allowed to create the corresponding type of hosted list. (Note that the applicable right may also be inherited from the default level, if not overridden on the individual account/group level.)

5.3.2 Grant Right to Administer Recipient Datasets

Once usage of hosted lists has been enabled for a group (specifically in the group settings or as an inherited default setting), it is still necessary to define which accounts from the group are actually granted the right to use this feature.

To define the right, go into the Administration Hub, and click on Administer User Accounts. Select the account to which you want to grant the right, click Maestro User Interface, and then User Right Settings.

The User Right Settings screen allows you to grant or revoke the right to administer hosted recipient datasets for the selected account.

Note: If this user right is granted, then the right to administer target groups is also always granted by default. Any user who is allowed to administer datasets will always also be allowed to administer target groups.

Note: If this user right is granted but usage of hosted lists is still disabled (see the previous sub-section), then the account will still not be able to administrate hosted lists until hosted lists are enabled as described above.

Note: Non-group accounts are handled in the same manner. If you grant only this right but do not enable usage of hosted lists, the account will not be able to use hosted lists. To actually allow usage of hosted lists, you also need to enable that feature as described in the previous sub-section. (Enabling usage of hosted lists, but not granting the administer hosted recipient datasets right, will not have any effect and the account will not be able to used hosted lists.)

5.3.3 Define Database Server in LISTSERV

Hosted lists of the Hosted LISTSERV List type are based on classic LISTSERV lists, as described in the previous sub-section.

The LISTSERV list created by LISTSERV Maestro will be an actual LISTSERV list, but one that is “database backed” by a table in the LISTSERV Maestro system database (also called “DBMS-backed list” or simply “DBMS list”). This means that the subscribers on the list are not stored in LISTSERV itself, but in a table in the database backing the list (in this case, the LISTSERV Maestro system database). With such a DBMS list, LISTSERV must have access to the backing database in order to be able to retrieve the subscribers during delivery.

To enable LISTSERV to access the LISTSERV Maestro system database, you need to configure a specific database server name in the LISTSERV instance.

You need to do so for every LISTSERV instance that is configured in the LISTSERV connection settings of any account/group for which the feature to create Hosted LISTSERV Lists is enabled.

In other words, if for an account/group you have enabled the feature to create Hosted LISTSERV Lists, then you must configure the LISTSERV instance that this account/group has defined in its LISTSERV connection settings (or inherited from the default settings) to be able to connect to the LISTSERV Maestro system database. (If the only hosted list type you have enabled is Hosted Recipient List, then you do not have to do this.)

The following instructions describe how to configure a LISTSERV instance on a Windows 2000 host so that it is correctly enabled to connect to the LISTSERV Maestro system database. For other Windows operating systems, the procedure is very similar. For LISTSERV on a non-Windows host, please refer to the LISTSERV documentation on how to create a database server name. Use the description below as a guideline and modify it to apply to your operating system.

On Windows, LISTSERV’s database connection happens by way of ODBC. You must first create a system-wide ODBC data source on the host where the LISTSERV instance is installed. This may or may not be the same host where LISTSERV Maestro or its system database is installed.

For example on Windows XP: Open the Control Panel. Next, open Administrative Tools, then open Data Sources (ODBC). Select the System DSN tab, and then click [Add…]. Select the appropriate driver and fill out the driver-specific form with the database specific values, using the same values as you supplied for the system database connection in the Administration Hub of LISTSERV Maestro (the same database host name, port and any additional settings required by the driver). L-Soft does not recommend supplying a user name and password in a system-wide DSN (if offered by the driver at all). Instead of supplying these values in the DSN, you will supply them in the LISTSERV configuration (see below). Give the DSN a meaningful name.

Now you need to configure this DSN as a database server name in LISTSERV. You can do so by using the LISTSERV Configuration tool or by editing the SITE.CFG file directly:

· Using the LISTSERV Configuration tool:

Start the tool. Click on Advanced Configuration and then DBMS…, then on More Servers. Fill out the Server field with the specific server name (see below for details) and the DSN, User ID, and Password fields with the name of your DSN and the same database user name and password that you have also supplied for the system database connection in the Administration Hub of LISTSERV Maestro. Then click [Add/Replace] and then [OK].

· Editing SITE.CFG:

Add the following lines to the SITE.CFG file of the LISTSERV instance:

      ODBC_DSN_SERVERNAME=DSN_NAME
   ODBC_UID_SERVERNAME=USERNAME
   ODBC_AUTH_SERVERNAME=PASSWORD

where you replace “SERVERNAME” with the specific server name (see below for details), “DSN_NAME” with the name of your DSN and “USERNAME” and “PASSWORD” with the same database user name and password that you have also supplied for the system database connection in the Administration Hub of LISTSERV Maestro.

The “SERVERNAME”: The value for the specific server name to be used in the above configuration is a special value that you can find on the LISTSERV Connection screen in the Maestro Administration Hub (Global Component Settings à Maestro User Interface à Default LISTSERV Connection.) The server name is given as the value labeled Database Server Name in the Connection Settings for Hosted LISTSERV Lists section. This name always starts with “MAESTRODB_”, followed by a unique string of characters. For example, “MAESTRODB_dtn7nzn3”. So the entry in the SITE.CFG might look like this:

            ODBC_DSN_MAESTRODB_dtn7nzn3=DSN_NAME
      ODBC_UID_MAESTRODB_dtn7nzn3=USERNAME
      ODBC_AUTH_MAESTRODB_dtn7nzn3=PASSWORD

(On your own server, you would replace “dtn7nzn3” with the correct value for your SERVERNAME.)

It is important to use exactly the same server name as given on the LISTSERV Connection screen of the Administration Hub, using the exact spelling (all letters must be in lowercase, which is also useful to discern between the letter “O” and the digit “zero”: The letter is shown in lowercase as “o” while the digit is shown as “0”).

Important: LISTSERV requires that if you are using a database server name, the “default database interface” must also always be defined, even if it is not used. If you do not already have the default database interface defined, you need to do this now. Otherwise, the above configuration of the database server name for Maestro will be ignored by LISTSERV. However, for the default database interface, you may supply dummy values as shown below. (Note that the following step is not necessary if the default database interface is already defined in your LISTSERV configuration.)

Again, you can edit your LISTSERV configuration either by using the LISTSERV Configuration tool or by editing the SITE.CFG file directly:

· Using the LISTSERV Configuration tool:

Start the tool. Click on Advanced Configuration and then DBMS…. Enter “Dummy” into the DSN, User ID, and Password fields in the Default Interface to Database section, and then click [OK].

· Editing SITE.CFG:

Add the following lines to the SITE.CFG file of the LISTSERV instance:

      ODBC_DSN=DUMMY
   ODBC_UID=DUMMY
   ODBC_AUTH=DUMMY

Note for Users of the Internal System Database: LISTSERV Maestro comes with an out-of-the-box version of MySQL as the internal system database. If you use this internal database as the system database and need to connect LISTSERV to it as described above, do this as follows:

· If LISTSERV is installed on the same host as the internal database – that is the host where the Maestro User Interface (LUI) component is installed – then you need an ODBC-driver for MySQL on that host, and when creating the DSN you need to supply the host name “localhost”, the port “3306” and the database name “LUI”. In the LISTSERV Configuration tool (or the SITE.CFG, see above), supply “luiuser” as the user name and “lui” as the password.

− OR −

· If LISTSERV is installed on a different host than the internal database, then you need an ODBC-driver for MySQL on that host, and when creating the DSN you need to supply the host name where the internal database is installed (the host where the Maestro User Interface component is installed), the port “3306” and the database name “LUI”. Then in the LISTSERV Configuration tool (or the SITE.CFG, see above), supply a database user name and password of your choice (and of course remember which ones you chose).

As a second step, you need to grant the right to access the internal database to this user that you have defined. Do so here:
On the server where the Maestro User Interface component is installed, start the MySQL client program

[Maestro installation folder]/lui/database/bin/mysql –u root

Then enter the following command:

grant all on lui.* to USERNAME@LISTSERVHOST identified by 'PASSWORD';

where you replace “USERNAME” with the database user name you have defined (this is your self defined user name, see above), “LISTSERVHOST” with the name of the host where LISTSERV is running and “PASSWORD” with the database password you have defined (again, your self defined password, see above).

Take care to use the same upper/lowercase spelling of the username and password as you have defined them in the LISTSERV Configuration tool (or the SITE.CFG). Also take care to type “lui.*” in lowercase.

5.4 Page Compilation

To display the pages of the user interface, LISTSERV Maestro uses a technology that compiles each page “just-in-time” – that is, at the moment a user accesses a page for the first time. This means that when LISTSERV Maestro is freshly installed, all pages are still un-compiled, existing in their raw state. The moment a page is accessed for the first time, it is compiled automatically behind the scenes and the result is displayed to the user.

Because of this, the first access to a page is usually noticeably slower (it takes longer for the page to appear) because the page is compiled first. Any subsequent access to the same page will happen with normal speed because it is now pre-compiled (even after a restart of the server).

5.4.1 Pre-Compiling All Pages

The slower page loading during first access after an installation can be avoided by executing the “CompileAll” command after the installation. This will pre-compile all pages of the application so that page loading will happen with normal speed even during the first access of a page.

The command can be found in the “commands” subfolder of the LISTSERV Maestro installation folder. The command is named “CompileAll.sh”. Simply execute the command.

LISTSERV Maestro must be running on the server while the command is being executed.

Note: Compilation is a lengthy and processor-intensive task that may take a considerable amount of time during which the server will be working to capacity. Please be patient and wait until the “Compilation complete” message appears in the console (see below). You may safely interrupt the command at any time, which will then leave all the remaining pages in the un-compiled state. You can then re-execute the command at a later time to compile the remaining pages.

Executing the command is completely optional. If you do not execute the command, or if you interrupt its execution, all pages that are not pre-compiled will be compiled in the background when they are accessed by a user for the first time. This command needs to be executed only once, since running it again when all pages are already pre-compiled has no additional benefit.

When executed, the command displays its output in a console, similar to the following:

Compilation started at Thu Aug 08 09:56:14 CEST 2002

http://yourhost/hub/index.jsp: success
http://yourhost/hub/JSP/applicationList.jsp: success
...etc...
http://yourhost/lui/JSP/userSettings/preferences/report/collaboration.jsp: success
http://yourhost/lui/JSP/userSettings/preferences/report/report.jsp: success

Compilation complete
All pages compiled successfully

The last line of the output must read “All pages compiled successfully”. If that line instead reads “There were compilation errors on ... pages”, then there was a problem. If all pages failed to compile, then LISTSERV Maestro was probably not running on the server on which you executed the command. If LISTSERV Maestro actually was running, or if only a few pages failed to compile, then you most likely have a corrupted installation. Try to re-install or, when in doubt, contact L-Soft support.

The “CompileAll” command only pre-compiles the pages of the local server. If both the Maestro User Interface and the Administration Hub components are installed on the same server, then “CompileAll” will pre-compile the pages of both these components. If only one of the components is installed, then the command will pre-compile only the pages of that component. In this case the command should also be run on the server(s) where other components are installed.

Appendix C: Special Mac OS^® X Installation Issues

Configuring LISTSERV Maestro for Automatic Startup

To enable LISTSERV Maestro to be started automatically during each system startup (as a background process), a Startup Item for the background process must be installed. This is done as follows:

(For the below procedure to work, you must be logged in with an administrator account or as the root user.)

During the installation, setup has already prepared a startup item for the LISTSERV Maestro server which needs to be copied to the correct location to “install” it. The prepared startup item is initially located in the following folder:

[Maestro installation folder]/commands/StartupItem

The startup item itself is a folder with the name “LISTSERVMaestro” which contains two files (one called “LISTSERVMaestro”, i.e. the same name as the folder itself, and one called “StartupParameters.plist”).

Copy this “LISTSERVMaestro” startup item folder with the two files in it to the following location:

/Library/StartupItems

so that you have the following folder and file structure:

/Library/StartupItems/LISTSERVMaestro/LISTSERVMaestro
/Library/StartupItems/LISTSERVMaestro/StartupParameters.plist

After you have copied the folder, you need to set the correct folder and file ownership for these items: Both the folder and the files in it must be owned by “root” in group “wheel”.

You can change the ownership manually as follows: Open a terminal, change to the folder “/Library/StartupItems” and execute the following command:

sudo chown –R root:wheel LISTSERVMaestro

(enter your administrator password if queried – if you are already logged in as the root user, you can leave out the “sudo” part in the above command).

Note: If you do not want to set the ownership manually, you can let Mac OS X do this for you: Restart the computer and log in again with the same account as before. A short moment after the login, a security warning for the startup item will be displayed, caused by the still incorrect ownership of the files. One of the options in the security warning window is the Fix option. Select this option to let Mac OS X set the correct ownership on the startup item files for you.

Terminal Based Installation (“Headless”)

The normal LISTSERV Maestro Setup wizard which is started via the “LISTSERV Maestro 3.0-2 Setup” icon is a GUI based application which requires the Mac OS X Aqua user interface to run. If the graphical user interface is not available (for example if you are installing remotely via telnet), you may also execute the Setup wizard in a purely text based terminal mode.

To start the Setup wizard in this terminal mode, open a terminal and change into the folder into which you have unzipped the distribution ZIP archive. This is the folder which contains the “LISTSERV Maestro 3.0-2 Setup.app” folder. From there, execute the following command:

"LISTSERV Maestro 3.0-2 Setup.app"/Contents/MacOS/LISTSERVMaestroSetup.sh -headless

Understanding the LISTSERV Maestro “Run-User”

The run-user is the account under which the LISTSERV Maestro server is actually run (no matter if started as a terminal application or as a background process).

After a fresh installation, the initially configured run-user is always the root user.

Security Note: For security reasons it is usually considered good practice not to run a server under the root user account, if possible. Therefore, you might want to change the run-user to a different account after the initial installation (however, you have to keep the run-user constraint in mind).

The currently configured run-user can be found in the file

[Maestro installation folder]/commands/UserConfig.sh

In this file, look for an entry similar to “export RUN_USER=username”, where “username” defines the current run-user.

LISTSERV Maestro “Run-User” Constraint

For security reasons imposed by the operating system, non-root users are not allowed to open servers on the so called “privileged ports”, which are ports in the range of “1023” and below.

Therefore, the choice for the run-user is constrained by the following:

· If the HTTP-port is a privileged port (“1023” and below, including the defaults of “80” for HTTP and “443” for HTTPS), you must specify the root user as the run-user.

· If the HTTP-port is a non-privileged port (“1024” and above), you can specify any user account as the run-user (preferably not the root user).

How to Change the LISTSERV Maestro “Run-User”

To change the LISTSERV Maestro run-user, do the following:

· Shut down LISTSERV Maestro.

· Edit the following file:

[Maestro installation folder]/commands/UserConfig.sh

The file contains an entry similar to:

export RUN_USER=username

where username is the name of the current run-user. Replace this name with the user account name you want to define as the new run-user instead.

· If the new run-user is not the root user, then you also need to do the following:

· Make sure that you do not violate the run-user constraint, i.e. it might be necessary that you also change the HTTP-port to a non-privileged port if the new run-user is not the root user.

· Set file ownership of the LISTSERV Maestro installation folder and all files in it to the new run-user (this is not necessary if the root user is used as the new run-user), by executing a recursive chown command on the installation folder:
(For this to work, you must be logged in with an administrator account or as the root user.)

sudo chown –R username:groupname installfolder

where username is the name of the new run-user, groupname is the name of group the files shall belong to (the group is optional and can be left out, in which case you would leave out the colon “:” too) and installfolder is the name of the folder where LISTSERV Maestro is installed.

(Enter your administrator password if queried – if you are already logged in as the root user, you can leave out the “sudo” part in the above command.)

Section 1 Quick Installation Guide

1.1 Install LISTSERV

1.2 Install External Database (optional)

1.3 Install LISTSERV Maestro 3.0-2

Section 2 Upgrading an Existing Installation

Section 3 Modifying or Uninstalling an Existing Installation

Section 4 Running LISTSERV Maestro

4.1 Starting LISTSERV Maestro

4.1.1 Start as Background Process

4.1.2 Start as Terminal Application

4.1.3 Checking if LISTSERV Maestro is Running

4.2 Stopping LISTSERV Maestro

4.3 Accessing LISTSERV Maestro

4.3.1 Supported Browsers and Client Operating Systems

Section 5 Prepare LISTSERV Maestro for First Use

5.1 First Steps with the LISTSERV Maestro Sample Account

5.2 Configuring LISTSERV Maestro for First Use

5.2.1 Administrator Password

5.2.2 Maestro User Interface Runtime Settings

5.2.2.1 LISTSERV Connection

5.2.2.2 Tracking URL

5.2.2.3 User Accounts

5.3 Preparing LISTSERV Maestro for Hosted Lists

5.3.1 Enable Usage of Hosted Lists

5.3.2 Grant Right to Administer Recipient Datasets

5.3.3 Define Database Server in LISTSERV

5.4 Page Compilation

5.4.1 Pre-Compiling All Pages

Appendix A: Required Resources

Appendix B: The Internal MySQL Database

Appendix C: Special Mac OS^® X Installation Issues

Configuring LISTSERV Maestro for Automatic Startup

Terminal Based Installation (“Headless”)

Understanding the LISTSERV Maestro “Run-User”

LISTSERV Maestro “Run-User” Constraint

How to Change the LISTSERV Maestro “Run-User”

1.3 Install LISTSERV Maestro 3.0-2

4.3 Accessing LISTSERV Maestro

4.3.1 Supported Browsers and Client Operating Systems

Section 5 Prepare LISTSERV Maestro for First Use

5.2.2.1 LISTSERV Connection

5.3 Preparing LISTSERV Maestro for Hosted Lists

Appendix B: The Internal MySQL Database

Appendix C: Special Mac OS® X Installation Issues

LISTSERV Maestro “Run-User” Constraint

Appendix C: Special Mac OS^® X Installation Issues