Members: Synchronization Settings: Rules

ListManager can synchronize its data with other data sources using ODBC. These settings determine how ListManager will create, edit and delete members, and according to what schedule.

Connection

Specifies the connection ListManager should use when synchronizing data for this list. The connections may be specified by a server administrator in Utilities: Administration: Server: Database: External Database Connections.

How Will Members Be Created?

Specifies how new addresses will be added to this list. The options are:

Normal Status, No Notification

Add the addresses with a Membership Status of Normal, but do not send a hello or confirmation message. These members will receive normal list mailings.

Normal Status, Send Hello Notification

Add the addresses with a Membership Status of Normal, and send them the hello message as specified for your list in Utilities: Document Associations. If no document is specified here, new members will receive a generic message from ListManager.

Confirm Status, Send Confirmation Request

Add the addresses with a Membership Status of Confirm, and send them the confirmation message as specified for your list in Utilities: Document Associations. If no document is specified here, new members will receive a generic message from ListManager. These members will not receive normal list mailings until they confirm their memberships.

Use Status as Specified (query must include MemberType_ field)

Import the addresses using the setting specified in the MemberType_ column. The MemberType_ column specifies whether the Membership Status is normal (that is, may receive mail), or is inactive, due to being unsubscribed, held, etc. See Members: Add Members: Add Member: Settings: Membership Status.

How Will Members Be Updated?

Determines how ListManager will handle duplicate email addresses. ListManager cannot add the same email address twice to the same list. These settings specify whether ListManager skips any duplicates it finds or updates its data with the data in the external data source. The options are:

Do Not Update (Leave Unchanged)

ListManager will skip duplicate email addresses, and leave the data for the address in its database unchanged.

Update All Available Fields Except Membership Status

ListManager will update all data for duplicate email addresses except for the Membership Status (MemberType_), so members who have unsubscribed or been held will not be reset to normal.

Update All Data Including Membership Status (if MemberType_ Available)

ListManager will update all data for duplicate email addresses including the Membership Status (MemberType_), so members who have unsubscribed or been held may be reset to normal. IMPORTANT WARNING: This setting can result in mail being sent to members who have unsubscribed, and should notbe used if ListManager is used to manage unsubscribed members and other inactive members.

How Will Members Be Removed?

Specifies how ListManager should handle addresses that are not included in the external database. The options are:

Do Not Change Membership Status of Members Not in External Data Source

ListManager ignores members that are currently in its database but not in the external database. These members will receive mail according to their Membership Status (MemberType_).

Quietly Unsubscribe

ListManager quietly unsubscribes members that are in its database but not in the external database, so these addresses do not receive mail. If the member is included in subsequent synchronizations, its Membership Status will be reset to normal unless the member unsubscribed directly.

Terminate Synchronization

Sets the number of consecutive invalid email addresses to end the synchronization process. For instance, you may want to terminate synchronization after 10 invalid email addresses, and check your formatting to see why so many addresses are failing. You can also set it to "Do not terminate import due to malformed addresses" if you'd like to ignore any bad addresses and process the import as-is.