Utilities: Administration: Server: Server Settings: Security: User Limits
Allow segment use
This setting determines what level of segment use is available to the list admins for the entire server. There are three levels of permissions:
- Simple and advanced segments available to all administrators
- Restrict list administrators to simple segments only
- Segments available only to server administrators
Administrators of all levels may type in SQL queries directly in the Query box, and may access the Advanced and Boundaries tabs when creating a segment. List administrators may alter segment boundaries, which permits them to see and download members from other lists.
List and site administrators may create segments using the Insert Clause button, but may not type in a query directly. They also do not have access to the Advanced and Boundaries tabs.
List and site administrators is able to use segments, but not to create them.
Behavior of CreateSegment
- All administrators may create both simple and advanced segments.
- There are no limit/restrictions for creating segments.
- List administrators may create simple segments only. List administrators can only create simple segments for liststo which they have access.
- Only server administrators may create segments.
Behavior of DeleteSegment
- All administrators may create both simple and advanced segments.
- List administrators may create simple segments only.
- All administrators can delete segments to which they have access ( i.e., the list related to that segment )
- Only to server administrators may create segments.
By default, Aurea List Manager is set to "Simple and advanced segments available to all administrators". Note that this setting allows list administrators to change their segments' boundaries so they may see and download members from other lists for which they do not have administrative rights.
Scripting feature level
This setting determines what level of scripting or merge is available for the entire server. There are three levels of permissions:
No Advanced Scripting/Merge
Disables all advanced scripting. Merging based on the standard Aurea List Manager tables is allowed; user-defined fields are not.
Safe Scripting/Merge
Allows only 'safe' advanced scripting. File system, SQL and other potentially harmful access is not allowed.
Full Scripting/Merge
Allows the complete Tcl Interpreter, including file system, SQL, and other access. Important: if you allow full scripting/merge, we recommend that all lists are set up to moderate all incoming messages. Certain Tcl procedures such as "redirect" could be misused. See Aurea List Manager Tcl Procedures for more information about the "redirect" command.
By default, Safe Scripting is allowed if you are using Aurea List Manager Pro or Enterprise, and No Advanced Scripting if you are using standard Aurea List Manager. Safe and Full Scripting/Merge are only available if you are running Aurea List Manager Pro or Enterprise.
The level of scripting you select should be determined by the types of lists you're using, and who is likely to post to it. For example, discussion lists are unlikely to need the advanced scripting features, so scripting should be disabled with this setting if all the lists on your server are discussion lists. Even the 'safe' level would likely be unnecessary for this type of list.
Note that this setting overrides the list level Scripting Level if the setting here is more restrictive than the setting for the list, unless the list's scripting level has been overriden by the server administrator for the list in Utilities: List Settings: For Programmers: Email Scripting.
If you'd like Full Scripting/Merge to be available for admins but not list members, you can set this setting and the list Scripting Level to Full Scripting/Merge, but limit it to admins in the Allow Scripting in Body setting.
Hide menus with disclaimers
Depending on your license, some menu items may be displayed with the disclaimer Contact your salesperson
to enable this feature. By default, this feature is set to
Max message size
Defines the maximum message size that ListManager accepts. The size is defined in bytes.
This number applies to the ListManager mail receiving engine, and means that messages over this size are refused before they are even saved.
This feature is useful if you want to impose a server-wide maximum message size.
Let CSV member imports update non-normal member status
By default, Aurea List Manager does not allow CSV imports change a member's status to normal if the member's status is anything but normal (unsub, confirm, held, etc). By changing this setting to yes, the member status of any member may be changed by selecting the Use type setting in CSV file and Update existing members? options when importing members.
If you don't have the MemberType_ column in your CSV file, and do not choose Use type setting in CSV file as an option, your members is changed to normal, regardless of what it was before.
GUI User Timeout
The length of time a user may be idle before the administrator user web interface times out, forcing the admin to log back in before continuing to work with ListManager. By default, the web interface never times out. Select the length of time a user may be idle before the interface times out here.
This timeout only affects the administrator interface, not the Discussion Forum Interface.