4. List Settings

4.1 List Details
4.1.1 List Name
4.1.2 Description
4.1.3 Email Address
4.1.4 Friendly Name
4.1.5 Charset
4.2 Database
4.3 Incoming Messages Settings
4.3.1 Subscribe Keyword
4.3.2 Remove Keyword
4.3.3 Webform Submissions
4.3.4 Non-List Messages
4.4 Incoming Messages (POP3/IMAP)
4.4.1 Mail Account Options
4.5 Outgoing Messages (SMTP)
4.5.1 SMTP Server and Authentication
4.5.2 Port
4.5.3 Username and Password
4.5.4 Limit
4.5.5 Break / Pause
4.6 Autoresponder
4.7 Opt-in



Select the List in the section "Member Lists" and click on "List Settings".


4.1 List Details

The section "List Details" contain basic settings for your list, like "Name" and "Email Address".


4.1.1 List Name

The list name identifies your list. The list name is used inside the default autoresponder message and as xmailer mail header field (by default).


4.1.2 Description

Here you can enter a private description for the list.


4.1.3 Email Address

Please enter the list email-address. The list email-address is the address, which is used to send out messages and to which requests should be sent. If you want to process incoming messages or email requests, please make sure you enter the email address for the email account used for incoming and outgoing messages.


4.1.4 Friendly Name

In the second field you can enter a name, which appears in the outgoing message as sender name.


4.1.5 Charset

The program chooses the correct charset during the installation, so in most cases you don't need to change anything as long as you are sending messages in the same language (and charset) as your system language (and charset).

The charset setting is obsolete! MailList Controller Version 9 (or newer) is written in Unicode and sends out all messages in utf-8 format.
Utf-8 contains all characters, so you don't need to care about the charset any longer.


What Charset should I use?
See: International Character Sets (charsets) for Email Newsletter Messages


4.2 Database

"Database" shows information about the database and the database fields, which could be used to personalize a message.

Using the option "Add Field" you can add a field to your "Regular List". Click on "Rename" to change the name of a field. Please note, that it might be required to change your subscribe froms if you change/add database fields.  Please note, that fields cannot be removed and its also not possible to use empty fieldnames. Please create a new list if you want to remove exisiting fields!

If the list is linked to an external database, you cannot change the fields here!


4.3 Incoming Messages Settings

If the program should be able to process subscribe/remove requests (e.g. webform subscribe requests) or returned messages, make sure you enable "Enable incoming messages". Please note, that it can only works if you have entered a valid POP3/IMAP server before!


4.3.1 Subscribe Keyword

The subscribe keyword can be freely defined and is required for subscribe requests via email or webform. The subscribe keyword should be placed in the subject of the subscribe or webform message.


4.3.2 Remove Keyword

The remove keyword can also be customized. It is required for remove requests.


4.3.3 Webform Submissions

Click on "Webform Submissions" for a sample of how the subscribe message should look like.

MailList Controller contains a built-in HTML Webform Generator, which will build the HTML Webform and the required php-Script for you. 
There is no manual coding required!

The MailList Controller HTML Webform Generator is an easy to use tool to integrate a html subscribe/remove form in your existing webpage. The tool will add the form code to your webpage and will also create the required php-script. The webform is based on HTML and PHP, which is widely spread and available on most webservers.

The usage is very simple, just add the text "AMLC-WEBFORM" at the desired position in your HTML page and select the HTML file on your hard-drive. The program will replace the text "AMLC-WEBFORM" with the form code.


4.3.4 Non-List Messages

Here you can setup, what should happen with non-list messages. 
A non-list message can be e.g. spam, additional questions, reply to your message or other messages.

The following options are available when using a POP3 account:

  • "Remove all messages and forward non-list messages to the foward-address." (POP3 only!)
    All non-list messages are removed from the mailserver and forwarded to the email-address you specified as "Forward-address". Don't enter the lists email address here, or you would generate a mail-loop! Please make sure, that you use a seperate email account, which is not setup in any other mailclient when using this option. It will remove all messages from the inbox! This option is the first choice if the list should run without user intervention.

  • "Remove all messages from POP3 account" (POP3 only!)
    Any non-list message is deleted from the server.
    Warning: This option will delete all messages from the specified POP3 mailaccount!

  • "Leave non-list messages on POP3 account" (POP3 only!)
    Any non-list message is not deleted from the server. You should check the account from time to time
    with your normal mail-client and check those messages. This is the default option.

IMAP Account: 

  • The program will process all List Messages in the "Inbox" folder.
    Processed Messages will be copied to the folder "MailList Controller" and expunged from the "Inbox".

  • Please clean your IMAP folders from time to time to free up space on the IMAP account.


4.4 Incoming Messages (POP3/IMAP)

Please enter the account details (POP3/IMAP) for the email-account you specified as list-email address.

Server Type:

MailList Controller supports POP3 and IMAP accounts. Please select the "Server Type" required for your mailserver.

During a "Synchronize" the program connects to the lists inbox (POP3 account) and checks for the new messages. This can be a subscribe or remove request, an external client message or a reply from a list member to one of your mailings.

Each list needs an unique email address or POP3 account – this means you cannot use the same email-address for multiple lists with enabled incoming messages. The software will disable incoming messages for lists using the same email account to make sure, that the messages will not be processed by a second list using the same email address.


4.4.1 Mail Account Options

Some users only have one POP3/IMAP account. In this case you need to setup different email addresses (aliases) for the POP3/IMAP account, so that each list has an unique email address.

  • Disabled
    If you just want to send out messages and don't care about incoming messages you should leave POP3/IMAP server, POP3/IMAP username and POP3/IMAP Password empty.

  • Seperate mail account:
    The program uses all messages from the specified mail (POP) account for the current list.

    Sample:

    List One: Address: emailone@arclab.com
    POP3 Server: mail.arclab.com
    POP3 User: listone

    List Two: Address: emailtwo@arclab.com
    POP3 Server: mail.arclab.com
    POP3 User: listtwo

    List Three: Address: emailthree@arclab.com
    POP3 Server: mail.arclab.com
    POP3 User: listthree

    Each list has an unique inbox ( POP3/IMAP account – Server, User, Password). The program will process all messages on the pop account for the list, it does not check the email address. The software will disable incoming messages for lists using the same email account to make sure, that the messages will not be processed by a second list using the same email address.

  • Shared mail account (POP3 Account has multiple Emailaddresses):
    If you use use the same POP3/IMAP account for multiple lists with enabled incoming messages, then the program identifies the list based on the email (alias) address and the email address in the To-line of the message header. Each list with enabled incoming messages requires at least an unique email address – you cannot use the same email address for multiple lists!

    Sample:

    List One: Address: emailone@arclab.com
    POP3 Server: mail.arclab.com
    POP3 User: demolist

    List Two: Address: emailtwo@arclab.com
    POP3 Server: mail.arclab.com
    POP3 User: demolist

    List Three: Address: emailthree@arclab.com
    POP3 Server: mail.arclab.com
    POP3 User: demolist

    You can see, that all lists have the same inbox (POP3 account), but different email addresses. The program identifies the list based on the recipient. For "List One" it only accepts messages with the lists email address (in this case emailone@arclab.com). It ignores all other messages.

    Incoming Message Sample (Shared mail account):

    From: ….
    To: emailthree@arclab.com
    Subject: Remove
    → List Three : Remove request

    From: ….
    To: emailone@arclab.com
    Subject: Subscribe
    → List One: Subscribe request

    From: ….
    To: emailthree@arclab.com
    Subject: Re: Company Newsletter
    → List Three: Reply to a Newsletter

    From: ….
    To: emailother@arclab.com
    Subject: hello
    → Message not for List One, List Two or List Three → Message will be ignored!


4.5 Outgoing Messages (SMTP)

Please enter the account details (SMTP) for the email-account you specified as list-email address.


4.5.1 SMTP Server and Authentication

Please refer to the mail account information provided by your ISP or mailprovider.

Authentication:

  • The default authentication method is "SMTP Standard AUTH". 
    Please use this option if you use the option "My account requires authentication" (non-SSL) in MS Outlook.

  • Please use "SSL" if your server requires a secure connection (Implicit SSL).

  • The program also supports "StartTLS" (Explicit SSL).

  • Some older mailserver require "POP before SMTP" authentication, which is also supported.

  • Mailserver Pickup Directory
    Please select "Mailserver Pickup Directory" as "Authentication" and select the pickup folder of your mailserver. The default directory is Mailroot\Pickup when using MS IIS SMTP Service.

    This option can be used if you are running a local mailserver, which has a pickup directory. In this mode, the program does not send using SMTP. It creates a .eml file in the pickup directory for each message, which will be used directly by your mailserver. The mailserver picks up the .eml file and sends it.

    MailList Controller will create the messages in the pickup directory very fast: up to 100.000 messages in less than 5 minutes, so it might be required to slow down or limit the number of messages per hour, if your server runs out of resources.

    This option is the fastest way to send out messages if you are running a local mailserver, which has a pickup directory. Please note, that the program does not receive any confirmation from your mailserver and your mailserver is responsible for sending out the messages an error processing. Please refer to the user manual of your mailserver for further details.


4.5.2 Port

The program automatically selects the most common port, but its also possible that you have to adjust the "Port".


4.5.3 Username and Password

Please enter the username and password required to authenticate.
In most cases the Username and Password is identical to the POP3 Username and Password. 
Please check the option "Same user and password as POP3 user and password", in this case.


4.5.4 Limit

Since some mailprovider have limited the mail traffic, the "Limit" option might be important for you. You can use this option to slow down the send process. The program sends out the number of messages specified as "Limit". If the limit is reached the program stops the send process and continues sending after the specified amout of hours.

Sample: Use 300 Messages in 1 hour if your mailserver is limited to max. 300 message/hour.


4.5.5 Break / Pause

Some mailserver require to wait some time after sending out a specific number of messages.

Sample: Use 60 seconds after 50 messages if your mailserver require a pause of 60 seconds after you have sent out 50 messages.


4.6 Autoresponder

Enable or disable autoesponders for this list. Its possible to use either the default autoresponders, which could be modified from the "Program Options" or use custom, list specific autoresonders.

The "Error" responder is disabled by default, because such an error message could confuse the List Member.
The error responder is for diagnostics and should not be used in live-mode.

You can use the following placeholders inside an autoresponder message:
##LISTEMAIL##, ##LISTNAME##, ##LIST##, ##ADDTAG##, ##SUBSCRIBETAG##, ##REMOVETAG## and [EMAIL].
Other fields are not available inside the autoresponder messages.


4.7 Opt-in

MailList Controller supports single and double opt-in ...

  • Single Opt-In:
    With a single opt-in process, an address is automatically added to the relevant mailing list as soon as it's
    submitted, e.g. through a sign-up form at a website. After adding the new member the program sends
    an autoresponder - welcome message.
    You can setup individual autoresponder messages for each list in the "List Settings" or use the default
    messages. You can also edit the default messages.

  • Double Opt-In:
    Double opt-in means the submitted address is not immediatley added to the mailing list. Instead an
    email is first sent to the email address, requesting confirmation. The recipient can confirm the request
    by replying to the confirmation message.
    The email address is only added to the mailing list, if the recipient responds to the confirmation email.
    After adding the new member the program sends an autoresponder - welcome message.
    The confirmation process is failsafe and very simple. All the new member has to do is to click "Reply"
    and "Send".