Notable Improvements in v4.0
Option to allow blank message bodies in postings: You can now allow messages with blank message bodies to be distributed to your lists, on a per list basis. This is useful for
mailing lists that distribute messages to wireless pagers, where the subject line is the entire content of the message. See Allow Blank Body.
Delete all members has option to delete admins: There is a checkbox on the members page which must be checked in order to delete the list admins when you use the "Delete All Members" button.
If this checkbox is not checked all members but the list admins will be deleted. This helps prevent the common problem of list administrators accidentally deleting themselves. See
Delete All Members .
Mail merge tag for showing lists you are a member of: These tags allow you to merge in information regarding which lists that member has signed up for. T he 'recip.whatlists' tag will merge
in the lists that member is normally subscribed to and the 'recip.whatlistsunconfirmed' tag will merge in those lists the recipient has signed up for, but has not yet confirmed for. Both these tags
are commonly used in the custom Confirmation document, or the custom Hello document, to help orient the member to the status of their several list subscriptions. See Recipient Fields
.
Mail merge tags for all recipient properties: All 'member' tags are now supported in 'recip' form, providing greater flexibility in merging in recipient info. See
Recipient Fields.
Server admin can receive transaction reports for all mailings on a server: This is known as the "debug mail" option and is useful if the server administrator is trying to determine why some
single piece of email (such as a confirmation request) is not reaching someone. Warning: This generates a great deal of email. See Enable Debug Mail.
Require passwords option now assigns a password when admin adds users: Now, when you are using the "add" email command to add users to a list which requires a password, a password is
generated for the user automatically. See Add.
Delete command now takes a memberid: You can now use the admin "delete" command to delete a subscriber based on that subscriber's member id. See Delete.
Support for ip address email addresses: Lyris List Manager now accepts email addresses of the form: bob@234.4.4.3 and bob@[234.4.4.3]. See Subscribing.
Option to not send held notifications: On a per list basis, you can specify to "never send a hold notification". This option has been around for several versions, however, its behavior is
more intuitive that in previous versions, where a single initial held notification would be sent regardless of setting. See Held Notify Interval.
Automatic signature detection when sending to lyris@: if "--", "**", or "==" is found in the body, then it is assumed to be a signature, and then signals the end of the message (thus,
interpreted as an 'end' command). This feature also correctly detects content-type separators in MIME messages, so they are not confused with signature sections. See Signature Detection
.
Several command-line database repair command line options: There are several database diagnostic/repair utilities built in. These include dbbadcharfix, dblistnamefix, dbmemberidfix, and
dbmemberemailfix. These are all run automatically as part of dbupgrade from v3. Thus, you no longer need to run these by hand, except if you import data right into the database, or if you get index
corruption, which can be repaired by dbmemberidfix. See Database Operations.
Option to use cascading style sheets: You can now specify a cascading style sheet to apply to your Lyris List Manager web interface by using the "css=xxxx" option in the lyris.plc file. See
Web Interface Style Sheet.
Support for more than 16 TCP/IP addresses: Lyris List Manager can now listen to more than 16 TCP/IP addresses, and you can specify a special address (1.0.0.0) which will force Lyris List
Manager to listen to ALL TCP/IP addresses on the machine. This support applies to Windows platforms. See Multiple TCP/IP addresses.
Purge and unsub can now can take an email address or member id: Purge/unsub requests sent as commands can now take either email addresses or member id's. See Unsubscribe.
File contents can now be specified in lyris.plc option file: You can optionally keep configuration information for any lyris.plc parameter in an external file, and access that information
using parameter=file:/path_to_file. See Using the file: option.
Default delivery domain: If someone joins your list and has an email address such as "bob" (such as occurs inside Sendmail servers on a single domain), Lyris List Manager can automatically
append a domain to the name so it is a valid email address. With this feature, you have the ability to select the default domain (e.g. "@company.com") which should be appended to "partial" email
addresses. See Default Delivery Domain.
Clean incoming & clean outgoing mail queue features: Now you can configure your server to clean the incoming and outgoing mail queues of completed messages after a certain number of days.
This allows you to more easily find messages in the Incoming or Outgoing mail queues since they will be removed after xx number of days. You can also prevent your Incoming and Outgoing Mail queues
from bloating by opting to process incoming mail in memory. Please Note: Disk space with FoxPro database files is not really reclaimed until a dbfastpack or
dbupgrade. See Clean Outgoing Mail Queue and Clean Incoming Mail Queue.
|