Section 30 LISTSERV Maestro Lite

LISTSERV Maestro supports a special “lite-mode”. In this context, "lite" means that certain features are restricted (not available). The restricted features can be grouped into two categories:

•	User-feature: Features that apply to the actual LUI users, i.e. such a restriction means that the LUI user has less options/features than in the full version. For example "No drop-ins" or "No personal tracking" are restrictions that fall into this category.

•

Admin-feature: Features that apply to the actual LISTSERV Maestro installation and the LISTSERV Maestro administration, i.e. such a restriction means that the LISTSERV Maestro admin has less options/features than in the full version. For example "No external system database" or "No dedicated bounce server" are restrictions that fall into this category.

The lite-mode itself can be activated in two different ways:

•

LISTSERV Maestro in lite-mode: This means that the whole LISTSERV Maestro installation is running in lite-mode. In this case, both the user-feature and admin-feature restrictions apply, and they apply for all users, as well as the admin. To activate this mode, add the following entry to the hub.ini file:

LiteMode=true

Note: Configuring LISTSERV Maestro to run in lite-mode as described above is a pre-condition for lite-LAKs to be accepted during LUI login. If LISTSERV Maestro is in lite-mode, then for a LUI login either a full-LAK or a lite-LAK will be accepted. However, in full-mode, only a full-LAK will be accepted. If only a lite-LAK is found while running in full-mode, then the user will be logged in with evaluation mode just as if no LAK was present at all.

•

Specific users in lite-mode: This means that LISTSERV Maestro is running in full-mode, but that for certain users the lite-restrictions do still apply. In this case, only the user-feature restrictions apply, and only to specific users (not necessarily all users). The admin-feature restrictions do not apply. To activate this mode, do not add the "LiteMode=true" setting in the hub.ini (so that Maestro by itself is running in full-mode), but instead add the following entry to the hub.ini file:

LiteModeConfigurableForScopes=true

With this setting, a new configuration section becomes available in the Administration Hub (under the Maestro User Interface settings), which is normally hidden. It is called “Lite-Mode Restrictions” (on group or user level) or “Default Lite-Mode Restrictions” (on application default level).

In this section, you can define if the account (or group) to which the setting applies will have the lite-mode restrictions enforced or not. If you enforce the restrictions on default application level, then this applies to all groups and accounts that do not specify a different setting on the individual level.

All accounts for which the lite-mode restrictions are enforced in this manner will have all the user-feature restrictions enforced. All other accounts/groups will be able to use the full feature set and the admin-feature restrictions will also not be enforced.

Note: As described above, LISTSERV Maestro must run in full-mode when using user specific lite-mode enforcement. This means, that even for users where lite-mode enforcement is switched on, a full-LAK must be available during LUI login, because in full-mode, only full-LAKs are accepted.

30.1 Current Lite-Mode Restrictions

The following sub-sections list the feature restrictions that are currently enforced by lite-mode, in their respective “user-feature” or “admin-feature” categories.

30.1.1 User-Feature Restrictions

User feature restrictions are restrictions that apply to users who log in at LUI. These restrictions apply both to normal LUI users, as well as to the admin if he logs in at LUI, unless noted otherwise:

•	No job statistics reports

•	No recipients statistics reports

•	No job categories

•	No job-list filters

•	No personal or anonymous tracking

•	No drop-ins (drop-in administration by admin not restricted)

•	No auto-repeat jobs

•	No tracking reports (only quick reports)

•	No team collaboration settings on jobs or datasets

•	No more than one single dataset

•	No categories in datasets

•	No X-headers in sender definition

•	No conditional content parts

•	No job-archiving by user (archiving by admin not restricted)

•	No auto-job-archiving settings by user (auto-job-archiving settings by admin not restricted)

•	No multi-job-actions for user (multi-job-actions for admin not restricted)

•	No authorization-due-by date

•	No specific link tracking (only "track all links" or "track no links")

•	No link aliases when tracking

•	No CSV upload recipients (and no matching target groups)

•	No "Select from database" recipients (and no matching target groups)

•	No "Let LISTSERV select from database" recipients (and no matching target groups)

•	No conditions and parameters in HRL and LISTSERV list target groups

30.1.2 Admin-Feature Restrictions

Admin feature restrictions are restrictions that apply to the administration and the installation of LISTSERV Maestro as a whole:

•	Only one user scope (only one single user or one group, with any number of group members)

•	No user identities

•	No option to revoke "create job" right from users

•	No option to define alternative "designated job owner" for users

•	No distributed LMA install (LUI, HUB, TRK must be on same server)

•	No external system database

•	No dedicated bounce server