10. Other Options

In this section more specialised features can be set through the Others panel. This is shown below:

'Others' configuration panel

Further options are also available under the settings section following on from the Others panel.

10.1. Subject prefix

Ezmlm can be configured to insert a prefix onto the subject of any new message sent to the mailing list. To use this facility select option 1( Outgoing message subject will have a prefix) in the Others panel. Save your changes by clicking the Make changes button at the foot of the page. The system automatically adds the default [listname] into the Subject Prefix box. Alternatively you can insert your own a short prefix into the Subject Prefix, Save any changes you make.

Settings available - subject prefix,
								message size and moderation time

10.2. Message Size

There is a maximum size of 10MB for all messages passing through the Oxford EZMLM system. This is therefore the maximum value you can set for maillist posts. The default maximum size is 3Mb and minimum size of 2 bytes. To increase or decrease these values select option 3 in the Others panel and type in new maximum or minimum values under the Settings section. Save your changes using the Make Changes button.

10.3. Trailers for messages

You may want to add unsubscription details or other information to the end of each post. In order to achieve this, select option 2 in the Others panel. You must now save your changes by pressing the Make changes button, otherwise the trailer trailer text file will not appear in the text file list. Once the configuration file has been saved, select [Text Files] from the main menu. The text files page will now appear and show Trailer as an link. Click on Trailer to edit the default text. The trailer default text is shown below:

-------------------------------------------------------
						To unsubscribe, e-mail: [list
						name]-unsubscribe@maillist.ox.ac.uk For additional
						commands, e-mail: [list name]-help@maillist.ox.ac.uk
					

10.4. MIME removal and rejection

Ezmlm provides the ability to strip or block unwanted MIME-type parts of emails. For instance if a user sends a html and text only versions, you can specify that the html version is stripped from the email. Your list members will only receive the plain text part of the email which all email software can handle. If there was only a html part and nothing else the message would be blocked (i.e. returned to sender) instead.

This can also be used to ensure people do not send binary attachments, such as large image files or viruses to your mailing list.

To activate this option you need to select Message blocking and stripping from the Others panel. At this point save your changes. Scroll down to the MIME types to strip from all outgoing mail box. This box will now contain the list of default MIME-types to be stripped or blocked from the mailing list. You can then edit this list as appropriate.

MIME-types box showing default
								list

10.5. Headers to add and remove

Ezmlm allows you to add customized headers to all posts and to remove any occurences of specified headers sent through its system. This feature is always in operation, so to make use of it there is no need to turn on any special options. You could, for instance, add a specific Reply-To header to ensure people always reply directly to the list instead of the sender.

Headers box showing default lists

There are a couple of "magic" variables that can be used in the headers to be added. These are:
  • <#l#> - The mailing list name
  • <#h#> - The mailing list server name
  • <#n#> - The current message index number (to aid archive retrieval)
You can add these anywhere in your custom headers and they will be translated by the ezmlm software into the correct entries.

10.6. Using an Alias with the Maillist

In the Settings section of the configuration page, there is an option to allow an alias email address to be used with the maillist:

Shows the Allow alias to be used
							checkbox
Figure 2. Allowing an Alias Address

To use an alias to send email to a list, the checkbox should be ticked. This will disable the checking of whether the list address appears in the To: or Cc: header of messages sent to the list. Most lists will not need this option so it should be left unticked. Please note if you do select this option, you will increase the amount of spam email sent to your list.

To setup or change where a generic alias is routed, contact registration@oucs.ox.ac.uk

10.7. Nested Lists

Nesting enables an EZMLM list (the "child") to be subscribed to another EZMLM list (the "parent") so that an email sent to the parent list is sent to subscribers of the child list as well as subscribers of the parent list.

Nesting is not enabled by default, but you can request this by emailing sysdev@it.ox.ac.uk with the full address(es) of the child lists that you wish to nest.

Please note the following when considering nesting:
  • Posting messages directly to child lists will not be affected by nesting.
  • Posting messages to parent lists will result in the message being sent to subscribers of the parent list and subscribers of any child lists.
    • If an address is subscribed to multiple lists then multiple copies of the message will be received.
    • The message that subscribers of any child lists will receive will show the address of the parent list in most visible headers (e.g. To:), but will have the address of the child list in most of the additional headers (e.g. Reply-To: and the List-*: headers)
  • Configuration of the child list will still apply - it is usually advisable to have consistent configuration (especially for settings such as maximum message size, accepted MIME types), and do remember that if the child list only accepts postings from selected email addresses then you may need to adjust the permitted sender addresses accordingly.
  • Bounces and other administrative responses relating to subscriber addresses on the parent list will be handled normally.
  • Bounces and other administrative responses relating to subscriber addresses on any child lists may not be handled as you would normally expect as the bounce will typically come back to the child list. This means that the owner of the parent list will not receive any delivery failure notifications for failing addresses subscribed to child lists. Further, for subscribers to the child list:
    • Replies will default to the parent list address.
    • Administrative responses (e.g. unsubscribe) will be sent to the child list (despite the parent list address being shown in the To: header).
    • Delivery failures will cause the bounce/probe process to be initiated for the receipients' subscription to the child list, despite the message having been sent through the parent list - this could be highly undesirable if the receipient has whitelisted the child list but not the parent list.

Up: Contents Previous: 9. Filtering Spam