Other Improvements in v4.0
Incoming mail processing now runs fully parallel: Previously each batch of inmail had to finish before the next batch was launched, causing a single time consuming message
(such as "review") to clog things up.
Added "lyris mailreceive xxx" command line: This command line option allows you to specify the mail receive rules for your Lyris List Manager. Thus, this option may now be edited on the
command line or on the Server Config page. See Setting Server Options.
SetConcurrency("string") optional LCP call for Solaris: For LCP programmers on Solaris who want to tinker with the concurrency level (i.e., number of light weight processes) to try to
improve multi-cpu performance. You can view the current concurrency level on the stats page. Note: The setting is automatically set to what is believed to be the optimal setting, but some Solaris
performance tuning references recommend hand-tuning of this value.
Moderated message auto-approve scheduling and resubmit email commands: You can now resubmit moderated messages and schedule them for later delivery using email commands. See
Moderate.
Multiple negatives in "BAN" supported (but using "approve" feature instead is recommended): You can specify multiple negative domains in the "Banned" setting (e.g., ~yourcompany.com,
~mycompany.com), however this functionality is more intuitively accomplished using the new "Approved" feature.
Index mailing supports "get listname date": Index mailings that go out from Lyris provide command to get the messages in this new format, rather than the old message id technique. See
Get Documents.
Removed obsolete feature for [xxx@ccc.com] rewriting: Before Lyris v3, Lyris List Manager used to put a "You are now subscribed as [xxx@ccc.com]. To unsubscribe, forward this message to
unsubscribe@ccc.com" at the bottom of each message. This email address served the function of the failsafe email address in those older versions. This technique of unsubscribing is now 2 versions
obsolete, and so we have removed the [xxx@ccc.com] rewriting feature, which was present in those old versions, and was needed to prevent an obscure problem that occurred when people quoted their
own message in replies.
Importing (or creating) many members is now faster: Various speed improvements were made.
Unsub/purge now include copy of email message in response: All unsub/purge requests received (not including failsafe unsub requests) now trigger the goodbye document to the member being
unsubbed/purged, as a security precaution. If you use the default goodbye document, the original message body will be appended, however, if you use a custom goodbye document, you can append the
original message text with the merge tag $subst('inmail.body'). See Unsubscribe.
List administrators receive a warning email at 95% capacity: Now when your member list grows to within 5% of the maximum allowable size, a notification indicating this information will be
sent to the list admin. This works for typical 'subscribe' and 'add' requests, however it is not triggered when adding members via the web interface. See Near Full Feature.
Database files reduced in size: The memo files native to the FoxPro database format (*.fpt) use less disk space than in previous versions. On average, the *.fpt files use only 10% of what
they used to. For sites with very large words.ftp and messages.fpt files, the savings can be in the hundreds of megabytes.
New "lcptrace" command line option: This option is useful for programmers who are writing directly to the LCP protocol. This option displays all incoming and outgoing tcpip communications
on the LCP port, so they are more easily debugged. See Starting Lyris List Manager.
Header/footer features are now HTML-mail and MIME-mail aware: Html and mime messages that are sent to a list correctly get their header or footer wrapped inside the original encoding of the
message. Thus, your list headers and footers don't get added as attachments. See Headers and Footers.
|