Section 1
Introduction
Section 2
Configuring for First Use
Section 3
Changing Admin Password
Section 4
Creating Accounts
Section 5
Global Component Settings
Section 6
Backups
Section 7
Log Files
Section 8
User Interface Settings
Section 9
Database Connections
Section 10
Non-Standard Ports
Section 11
Firewalls
Section 12
SSL
Section 13
Tracking and Recipient Profiles
Section 14
Editing INI Files
14.1 Maestro User INterface INI Files
14.2 Administration Hub INI Files
14.3 Tracker INI Files
Section 15
Distributed Components
Section 16
User Interface Branding
Section 17
Evaluation Mode
Section 18
International Character Sets
Appendix A
Standard Default Ports
|
Section 14
Editing LISTSERV® Maestro INI Files
The following rules apply to the INI-files "lui.ini",
"hub.ini", and "tracker.ini" which are the
configuration files for the Maestro User Interface, Administration
Hub, and Maestro Tracker components, respectively (the "my.ini"
configuration file of the internal MySQL database follows
different rules, as it is a third party product; see the MySQL
documentation for details):
- All INI-files are
text files and assumed to be encoded in the default encoding for the
platform being used. For most English/European installations that would
be ISO-8859-1 [Latin 1 - Western European].
- In the files, every
parameter occupies one line. Each line must be terminated by a line
terminator (LF, CR,
or CRLF). All lines in
the file are processed.
- A line that contains only white space or whose
first non-white space character is an ASCII "#"
or "!" is regarded as a comment, and its content
is ignored.
- Every line other
than a blank line or a comment line describes one parameter (except
if a line ends with a backslash "\",
then the following line, if it exists, is treated as a continuation
line, as described below).
- A parameter always
consists of a key and a value. Keys and values are separated by white
space or "=" or ":".
Any white space around the separation character is also ignored.
- All remaining characters
on the line become part of the associated value. Some characters which
otherwise have special meanings, need to be escaped with a backslash.
The ASCII escape sequences "\t"(TAB),
"\n"(LF), "\r"(CR),
"\\"(backslash), "\""(quotation
mark), "\'"(apostrophe),
"\ "(space), and "\uxxxx"
(where "xxxx" is the
Unicode-value of the required character, expressed in hexadecimal format)
are recognized and converted to single characters.
- In the case that the last character on a line
is a "\", then the next line is treated as a
continuation of the current line; the "\" and
line terminator is simply discarded, and any leading
white space characters on the continuation line are also
discarded and are not part of the parameter value.
Examples:
Each of the following four lines specifies the key "Truth"
and the associated value "Beauty":
Truth = Beauty
Truth:Beauty
Truth :Beauty
Truth Beauty |
The following three
lines specify a single parameter:
fruits
apple, banana, pear, \ cantaloupe,
watermelon, \
kiwi,
mango
|
The key is "fruits" and the associated value
is:
"apple, banana, pear, cantaloupe,
watermelon, kiwi, mango".
Note that a space appears before each "\" so that
a space will appear after each comma in the final result;
the "\", the line terminator and leading white space
on the continuation line are discarded and are not replaced
by one or more other characters.
As a last example,
the line:
specifies that the
key is "cheeses" and
the associated value is the empty string.
|