Description of the changes for release 1.8d of LISTSERV(R) ---------------------------------------------------------- Copyright 1997-1999 L-Soft international, Inc. 1 March 1999 ************************************************************************* ************************** List owner's notes *************************** ************************************************************************* The release notes for version 1.8d of LISTSERV(R) have been split into two documents: list owner's notes and LISTSERV maintainer's notes. The present list owner's notes describe all the changes that list owners need to be aware of, although in some cases list owners may be impacted by changes described in the LISTSERV maintainer's section. For instance, the availability of a new systemwide option may prompt the LISTSERV maintainer to make a change affecting all the lists on the LISTSERV host. Thus, list owners are advised to read the maintainer's notes as well. ************** * Highlights * ************** - [non-VM] Enhanced WWW archive and administration interface - New passive probing feature - New "change-log" feature - New Bulk DELETE - GIVE and file "packages" implemented on non-VM systems - Maximum number of Topics per list has been increased - New CHANGE command to update subscriber addresses - Simpler subscribe/signoff methods with listname-subscribe-request, etc. - "Language=" enhancements (kill MS Exchange, HTML attachments) ************************************************************************** * [non-VM] Enhanced WWW archive interface (support for non-public lists) * ************************************************************************** Under version 1.8d the WWW archive interface introduced in version 1.8c has been expanded to include authenticated web archive access to non-public mailing lists. Non-public lists' archives are password-protected (with LISTSERV personal passwords, which can be obtained via the login screen) and are accessible only to those users who are covered by the Notebook= keyword's access setting. For instance on a list with Private notebooks, only subscribers may view the archives, and on a list with notebooks restricted to Owners, only list owners may view the archives. ************************************************************************ * [non-VM] Enhanced WWW archive interface (support for unlisted lists) * ************************************************************************ Under version 1.8d, a link has been added to the main archive index page (the page constructed by the WWW_ARCHIVE_INDEX template form) to an "unlisted archive" form, where a user can type the name of a known list, click the "Submit" button, and be transferred to the list's index page. Such lists could be accessed under 1.8c but the URL had to be entered manually. ************************************************************************ * [non-VM] Enhanced WWW archive interface (clickable attachment links) * ************************************************************************ Under version 1.8d, the WWW archive interface has also been enhanced to provide point-and-click links for e-mail attachments sent to lists. Assuming that a user's browser has a given MIME-type attributed to a helper application, he or she will be able to open attachments of that type which have been sent to the list in the appropriate application. ************************************************************* * [non-VM] New WWW list and server administration interface * ************************************************************* In addition to the web archive interface enhancements, version 1.8d introduces a fully-featured list and server administration interface. List owners and site managers can perform almost any list-related maintenance task via the (again, password-protected) list owner interface, and in addition, site managers can create lists and manage the overall "look and feel" of the web interface. ***************************************** * [non-VM] New WWW subscriber interface * ***************************************** The addition of the web administration interface and login authentication to LISTSERV 1.8d made it possible to allow general users to subscribe, change personal options, and signoff from a web form. This web form can be accessed from any of the web archive interface pages for a given list by simply clicking on the "Join or leave the list" link. All subscriber operations require a LISTSERV password for login authentication, which can be obtained via a link from the login page in the same manner as with list owner and LISTSERV maintainer logins. ********************************************************* * [non-VM] New WWW interface templates and style-sheets * ********************************************************* LISTSERV 1.8d's new WWW interface pages are highly-configurable. Most of the new pages are found in DEFAULT.WWWTPL, and can be configured on a site-wide basis by placing edited copies of the template forms in the file SITE.WWWTPL in LISTSERV's home or MAIN directory. List owners can individualize the look-and-feel of most elements of their web pages by placing edited template forms in listname.WWWTPL. Individual templates can be edited via the new list and server administration interface described above, making the entire template editing experience seamless. Finally, LISTSERV provides an extensible style-sheet feature that makes it possible to harmonize the look-and-feel of your entire site with a few mouse clicks. ******************* * Passive probing * ******************* Active address probing (via the Renewal= list header keyword) introduced in version 1.8c has been supplemented in version 1.8d by the introduction of "passive" probing. In effect passive probing is very similar to active probing, but it is not tied to subscription renewal. Passive probing is enabled by default for small lists (e.g., <1K subscribers) but not for large ones due to the fact that passive probing does cost additional resources and large lists are often used for one-shot mailings where it is simply not effective to use those resources to probe addresses that will not be used a second time. Since probes do not work with sendmail, the default under unix is to disable passive probing altogether. Passive probing operates by turning a certain percentage of your regular list messages into transparent probes that look like a normal message but also double as a probe, rather than sending out the explicit PROBE1 template as in active probing. You enable (or tune) passive probing by adding a ",Probe(xx)" parameter to the Auto-Delete= keyword setting. For instance, * Auto-Delete= Yes,Full-Auto,Probe(30) where "30" is the number of days to wait between probes for any given user. Subscribers with working mail systems will not see any difference, subscribers with flaky mail systems will occasionally receive a message showing that their mail bounced and saying that they should report the problem to their ISP, and of course plain bad addresses will go away. In order to disable passive probing you set the probe parameter to 0, i.e., * Auto-Delete= Yes,Full-Auto,Probe(0) If you have users who for whatever reason should not be probed, you can deactivate passive probing (and any other renewal you have set for the list) with the SET userid@host NORENEW command. If a given list only has activity once in a while (e.g., a large weekly newsletter), passive probing works like this: If you have Probe(p) set in your Auto-Delete= keyword (where p is some integer value), and you have n subscribers, about ( n / p ) will receive a probe during the mailing. Normally you would want to probe 2-10% of your subscribers in this kind of scenario, so p would range from 10 to 50. You can set site-wide defaults for passive probing with the new DEFAULT_PROBE site configuration variable. This variable controls two aspects of passive probing. The first parameter to this variable is the length of the default passive probing cycle in days. For instance, DEFAULT_PROBE=21 tells LISTSERV to use a passive probing cycle of 21 days instead of the default of 30. Because passive probing is very resource-intensive, above a certain list size it is disabled by default. The second (and optional) parameter to this variable is the list size beyond which passive probing is disabled unless you explicitly enable it in the Auto-Delete= list header keyword. For instance, DEFAULT_PROBE=10 500 tells LISTSERV to use a passive probing cycle of 10 days and to enable passive probing by default only for lists of 500 users or less. Note that the two parameters are space-separated. **************************** * New "change-log" feature * **************************** Starting with version 1.8d, this feature is available to track changes to lists with "Change-Log= Yes" coded into their headers. Setting the keyword to "Yes" for a given list causes LISTSERV to write a file called listname.CHANGELOG (or listname CHANGELG for VM) into LISTSERV's A directory or A disk. CHANGELOG files are automatically available for list owners and site maintainers to GET and PUT (PUT normally being used to delete them) like any other file. It is not necessary to make catalog entries for CHANGELOG files. The operations monitored are ADD, AUTODEL, BOUNCE, CHANGE, DELETE, POST, RESUBSCRIBE, SET, SIGNOFF, and SUBSCRIBE. All abbreviations and synonyms are translated to their "official" forms, i.e., SUB, JOIN, and SIGNON are all translated to SUBSCRIBE for the purposes of the changelog. This makes it easy to write scripts to come up with statistics for a given list - you don't have to take variations of the commands into account. Sample changelog entries are: 19980324100330 ADD xxxxxxx@JPS.NET Lxxxx Pxxxxxxxx 19980329120049 AUTODEL xxxxxxxx@EISA.NET.AU 19980329131221 BOUNCE xxxxxxxx@NONEXIST.COM 19980331214433 CHANGE xxxx@MCS.COM txxx@MCS.NET 19980331214434 DELETE xxxxx@SINGNET.COM.SG 19980331232441 POST xxxxxxxx@M4.SPRYNET.COM Printer Drivers 19980401000400 RESUBSCRIBE xxxx@MAIL.MECHWART.MUMSZKI.HU Mxxxxx Zxxxxx 19980426113947 SET xxxxxx.xxxxxxx@WDC.COM REPRO 19980511082712 SIGNOFF xxxxxxxx@STARNET.NET.AR 19980511085642 SUBSCRIBE xxxxxxxx@LYCOSMAIL.COM Kxx Wxxxxxx As you see, the SET entry tells you what options were set, and the POST entry tells you what the subject of the posting was. RESUBSCRIBE is a SUBSCRIBE operation that takes place when the user is already subscribed to the list, e.g., to change the real name field in the user's subscription. BOUNCE is a special operation that takes place when using the new "no-list" bounce-processing mechanism described above. Otherwise these entries are fairly self-explanatory. ******************* * New Bulk DELETE * ******************* The ability to delete subscribers "in bulk", similar to the existing ability to "bulk add" (available since version 1.8b), has been added to version 1.8d. However please note that there is no "IMPORT"-type option for this feature, and as usual for the DELETE command you specify only the user's address in the data DD. There is, however, a BRIEF option that can be specified, which is useful when you don't want a long list of "userid@host has been deleted from list xxxx" messages, one for each user deleted. Use of the BRIEF option tells LISTSERV to return only a count of the users that were deleted. Once again you construct a LISTSERV JOB framework as follows and then send it to LISTSERV (tokens in square brackets are optional; do not type the square brackets when sending the command!): [QUIET] DELete listname DD=ddname [BRIEF] [PW=yourpassword] //ddname DD * userid1@host1.com userid2@host2.com ... useridn@hostn.com /* You will probably want to use the QUIET modifier when doing a bulk delete, in order to suppress the notification message to the users being deleted. ************************************** * GIVE implemented on non-VM systems * ************************************** Beginning with version 1.8d, the GIVE command has been ported from VM and is available on all ports of the software. *********************************************** * File packages implemented on non-VM systems * *********************************************** Beginning with version 1.8d, file "packages" functionality has been ported from VM and is available on all ports of the software. The major difference between VM and non-VM is that under non-VM there are two ways to format entries in your $PACKAGE file: First, a "compatibility" mode that works on all platforms, and which is identical to the original method used on VM (and which VM servers still must use). In the compatibility mode the basic format for the entries is filename filetype filelist for example, MYLIST $PACKAGE MYLIST The packing list INTEREST FILE MYLIST Interest groups NETIQUET FILE MYLIST How to behave ANOTHER FILE MYLIST No comment In the second (new) mode for non-VM servers only, the entries are formatted like this: filename.extension for example, MYLIST.$PACKAGE The packing list INTEREST.FILE Interest groups NETIQUET.FILE How to behave ANOTHER.FILE No comment For more information please see chapter 8 of the List Owner's or Site Manager's manuals. ******************************************************** * Maximum number of Topics per list has been increased * ******************************************************** Under version 1.8d, a maximum of 23 topics (defined with the Topics= keyword) may be defined per list (increased from 11 in earlier versions). ***************************************************** * New CHANGE command to update subscriber addresses * ***************************************************** A new CHANGE command is available in version 1.8d. There are two syntaxes: A general user syntax and a list owner/LISTSERV maintainer syntax. General user syntax: CHANGE listname|* newaddr List owner/LISTSERV maintainer syntax: [QUIET] CHANGE oldaddr|pattern newaddr|*@newhost The first form can be used by any subscriber and results in a cookie being sent to the new address. This cookie MUST be confirmed by the new address, exactly as it was entered, or the command will fail. This is the only case where a 1.8d cookie must be confirmed by a specific address. Note that this assumes that the user still has login access to both addresses, or at least the ability to send mail from the old address. The list owner form does not use cookies but simply applies the standard "Validate=" rules (as for a DELETE command). You can specify a wildcard pattern for the old address and *@newhost for the new address to rename certain addresses to a new hostname. The CHANGE1 template is sent unless you specify QUIET. Change log entries are made (CHANGE oldaddr newaddr) and there is a new CHG_REQ exit point which allows you to reject the operation. The CHG_REQ exit point is called as follows: Name: CHG_REQ Parameters: Three; originator's e-mail address '15'x target subscriber's e-mail address '15'x new e-mail address Return code: 0=Accept, 1=Reject Description: This exit point is called for the CHANGE command, and allows you to accept or reject the operation. If you return the value 1, LISTSERV rejects the operation. *********************************************************** * Support for listname-subscribe-request, etc., mailboxes * *********************************************************** Version 1.8d now supports the following generic -request mailboxes for lists: listname-subscribe-request listname-signoff-request listname-unsubscribe-request (where "listname" is the name of the list in question). Mail sent to these addresses will be interpreted as explicit SUBSCRIBE, SIGNOFF, or UNSUBSCRIBE commands, respectively, for the list in question, regardless of the text contained in the body of the mail message (which will simply be discarded). Unix and VMS hosts will need to add appropriate aliases (as usual) to sendmail and PMDF, respectively, in order to activate this functionality. Windows installations using either the SMTPL.EXE "listener" or LSMTP have this functionality activated automatically. ************************** * Language= enhancements * ************************** Starting with version 1.8d, the Language= list header keyword was expanded to cover the following functionality: Language= HTML: This setting allows you to specify that LISTSERV's administrative messages (i.e., those specified in the MAILTPL and/or WELCOME and FAREWELL files) be sent out in HTML format. You specify either Language= HTML or Language= idiom,HTML to enable this feature. Language= NOHTML: This setting allows you to specify that LISTSERV strip any HTML attachments from postings (while retaining HTML tags sent in the body of plain text messages). You specify either Language= NOHTML or Language= idiom,NOHTML to enable this feature. The actual function of this setting is to remove the attachment that contains the HTML mail from the message. It does not remove HTML tags from plain text messages. This means that setting this option will not suppress HTML in messages sent from Eudora Pro 3.x (since Eudora Pro 3.x does not send the HTML message as a MIME attachment with a plain text alternative). The setting also does not suppress HTML in messages sent from current versions of Netscape Messenger if the sender chooses the "Send in HTML mail only" option when sending the message (because there is no alternate plain text attachment for LISTSERV to use in that case). Language= EXCHANGE: This setting allows you to specify that LISTSERV keep Microsoft Exchange attachments in postings (the default is to remove them). You specify either Language= EXCHANGE or Language= idiom,EXCHANGE to enable this feature. Note that this affects "application/ms-tnef" attachments only - LISTSERV does not currently strip WINMAIL.DAT attachments. These three formatting options are not mutually exclusive and may be defined in any grouping (in other words, Language= HTML,NOHTML,EXCHANGE is legal although it is unlikely anyone would want to use it). ******************************************** * New .HH list header formatting directive * ******************************************** Starting with LISTSERV 1.8d, it is possible to hide part or all of a list header (except for the list title) from users who send the REVIEW command or who try to view the list's configuration via the CataList. The following syntax is used: * My very own list * * blah blah blah *.HH ON * This line is hidden * This line is also hidden *.HH OFF * This line is not hidden The sequence can be repeated as many times as required. GET will return the unedited header with the .HH sequences, REVIEW will replace hidden lines with a note saying that lines were hidden. You can't hide the fact that some lines were hidden because it would lead to people spending hours trying to figure out problems which only appear to be problems because some of the keywords are not visible. L-Soft will not field support inquiries with hidden headers; you must send the entire raw header (including the .HH lines) when requesting support. ******************************* * Bulk operations via the web * ******************************* Bulk operations can also be accomplished via the list management interface. Bulk operations are not enabled by default. The LISTSERV maintainer must create a directory called "upload" under the directory specified in the WWW_ARCHIVE_DIR= site configuration variable, and give the userid under which the "wa" CGI program is run write permission in that directory. This is the only directory in which "wa" needs write authority, and only for this functionality. If you do not want the functionality, do not create the "upload" directory. Please note carefully that your browser MUST support the RFC1867 file upload extension or you will not be able to use the bulk operations page. Most current browsers do support this extension, including but not limited to Netscape 3.x and later, and Internet Explorer 4.x and later. New SUBSCRIBE ... WITH ... enhancement Version 1.8d introduces the following enhancement to the SUBSCRIBE command: SUBSCRIBE listname full_name WITH option1 option2 ... This syntax allows a subscriber to "preset" subscription options at subscribe time. For instance, a subscriber might want to subscribe to MYLIST-L in order to be able to search its archives, but doesn't want to receive any postings. The subscriber would use the command SUBSCRIBE MYLIST-L Joe User WITH NOMAIL Or a subscriber might want to receive individual postings with the SUBJecthdr option and receive copies of his own postings instead of the standard acknowledgement that his message was distributed to the list: SUBSCRIBE MYLIST-L Joe User WITH SUBJecthdr REPRO NOACK This is particularly useful when the list requires an "OK" confirmation before the subscription is accepted (since it eliminates the need for a SET command after the user is added). Note: The ADD command (as opposed to SUBSCRIBE) does not support "WITH" syntax. ******************************************** * "OK" confirmation mechanism enhancements * ******************************************** Starting with version 1.8d, an "OK" confirmation can be sent from any userid, which helps when the address field of your mail gets changed somewhere along the line. For instance if you are logged into the web administration interface as joe@example.com and issue a command that requires mail confirmation, LISTSERV will send the request to joe@example.com (as expected). If your mail system expands joe@example.com to Joe_Doakes@mail.example.com, responding to the request under 1.8c would result in a failure because the cookie and the address in your From: line wouldn't correspond to what LISTSERV has on file. Under 1.8d the "OK" will succeed and Joe_Doakes@mail.example.com will get a message that says > ok Confirming: > QUIET DELETE * jane@example.com [reply sent to joe@EXAMPLE.COM] while as a protection against "spoofed" commands the actual command response will be sent to joe@example.com like this: jane@EXAMPLE.COM has been removed from the TEST list. No notification has been sent. Global deletion process complete, one entry removed. Three further enhancements were added to the "OK" confirmation mechanism in 1.8d: - An "OK" without an argument (confirmation number) flushes the job stream, so any text following an "OK" on a line by itself will not be seen by the LISTSERV command processor (and thus will not generate errors). - Bracketed "OK" functionality. This feature allows you to send multiple commands for which LISTSERV will request only a single "OK" (where normally you would expect to have to "OK" each individual command). The syntax is as follows: OK BEGIN command1 command2 ... commandn OK END - A command confirmation ("OK") may now be sent by clicking on a web URL provided in the command confirmation request (mailed "OK"s are still perfectly acceptable, of course). ********************** * New PUTALL command * ********************** LISTSERV 1.8d introduces a new PUTALL command. Under 1.8c and earlier versions, a list PUT operation containing new subscriber information following the list header lines (i.e., trying to add new subscribers "on the fly") had the potential to overwrite your existing subscriber list with the new information, particularly if the header had been retrieved with the NOLOCK option. Under 1.8d and following this problem has been alleviated by the new PUTALL command and a modification to PUT. A PUT command containing new subscribers added "on the fly" will now result in only the header of the list being updated and a warning being generated that says if you really wanted to PUT the entire list, subscribers and all, that you should use the PUTALL command instead. The syntax of PUTALL is identical to that of PUT. ***************************************** * New BY DATE sorting option for REVIEW * ***************************************** A new BY DATE sorting option has been added to the REVIEW command for version 1.8d. "REVIEW listname BY DATE" formats subscriber lines as follows, newest subscribers first: jane@UNIX.EXAMPLE.COM [1998-08-05] Jane Doe g.rowe@MAIL.EXAMPLE.NET [1998-07-16] George Rowe doakes@EXAMPLE.ORG [1998-07-02] Joe Doakes For lists running under 1.8d with pre-1.8c subscribers in the list (i.e., who predate the software upgrade that saves the subscription date), such subscribers are listed at the end of the REVIEW output, sorted by hostname/userid, as follows: mary_smith@EXAMPLE.EDU [Unknown] Mary Smith ******************************** * New TOPICS option for REVIEW * ******************************** A new TOPICS option has been added to the REVIEW command for version 1.8d. "REVIEW listname TOPICS" appends a list of topics and the number of subscribers who are set to them at the end of the REVIEW listing. If you are only interested in the topics breakdown you can use the syntax "REVIEW listname TOPICS SHORT". The topics breakdown looks like this: * Topic Subscribers * ----- ----------- * 12 16 * Apps 564 * Backup 559 * Beta 553 * Bugs 562 * Comm 561 * Desktop 564 * General 440 * Hardware 562 * Install 563 * Internet 561 * Network 552 * Wish 552 * * "Other" topic 13 * Digest/index subscribers 251 ******************************************************************** * More enhancements to the anti-spamming and anti-spoofing filters * ******************************************************************** L-Soft acknowledges that these features have been continually upgraded and enhanced throughout the 1.8d development process, but in keeping with previously-announced policy, specifics are proprietary and will not be documented. **************************************************************************** * Some default options (e.g., REVIEW, NOPOST) now apply to non-subscribers * **************************************************************************** Starting with version 1.8d, certain default options coded in the Default-Options= list header keyword will be applied "on the fly" to non-subscribers who post to the list. Specifically the options applied are REVIEW, NOPOST, and NOEDITOR. For instance it is possible to code a "Subscription= By Owner" list with "Default-Options= NOPOST". When the list owner adds a user, he can simply send a "SET listname POST for userid@host" command to allow the new subscriber to post. Postings by any non-subscriber (for instance, a spammer) are rejected out of hand with a message informing him that he is not allowed to post to the list. In the same manner, using "Default-Options= REVIEW" allows the list owner to review any postings from non-subscribers while letting him allow known subscribers to post without moderation. ****************************************** * Enhanced "Filter=" list header keyword * ****************************************** Version 1.8d adds the ability to "exempt" certain addresses (or wildcards) from the default filters. You can combine "Filter= ...,Allow,..." with the existing Filter= directives as long as you put the "allow" information last. That is, the first word of the setting must be ONLY, SAFE or ALSO as before, and you can then have ALLOW anywhere (including as the second word) followed by a list of addresses that should be allowed even if present in the filter. The default for ALLOW is the value in the site-wide FILTER_ALLOW variable (which in turn defaults to the empty string). Examples of ALLOW usage follow: Filter= Also,userid@host1.com,*@host2.edu Filter= Allow,niceguy@host2.edu The first example stops everyone from host2.edu from posting to the list, but since we've determined that niceguy@host2.edu is a considerate human being and should be allowed to post, we've defined him as an exception to the general rule by defining him in the "Allow" part of the filter. Filter= Safe,Allow,root@host1.edu The second example would invoke the "safe" filter, but would allow root@host1.edu to subscribe to and post to the list, instead of bouncing his mail because it matches one of the entries in the "safe" filter. All other "root" users' mail will be caught by the "safe" filter and transferred to the list owner as an error. ********************************************************** * 8-bit administrative messages are encoded "on the fly" * ********************************************************** Starting with Version 1.8d, 8-bit characters (e.g., accented or national language characters) included in mail template forms will cause LISTSERV to encode the templates on-the-fly automatically, using MIME quoted-printable encoding. While there is no guarantee that every mail program will be able to properly display 8-bit characters, those mail programs that do understand MIME quoted-printable encoding should have no trouble doing so. ************************************************************** * New character set formatting directives for mail templates * ************************************************************** Starting with version 1.8d, it is possible to direct LISTSERV to add a "Content-Type:" header to mail templates and WELCOME and FAREWELL files that contain 8-bit characters from a specified character set. In non-linear mail template forms one may code (for example) .CS ISO-8559-7 and, assuming that the template in question contains 8-bit characters, LISTSERV will generate Content-Type: text/plain; charset=ISO-8859-7 Content-Transfer-Encoding: quoted-printable headers in the message when it is sent out. If the template contains all 7-bit characters the headers are not generated even if the .CS directive exists. Note that LISTSERV will not check to see whether or not the 8-bit characters match the character set defined. For WELCOME and FAREWELL files, the same headers may be generated by adding (for instance) Character-Set: ISO-8859-7 at the top of the file in question. Again, the file must contain 8-bit characters in order for these headers to be generated. Please note carefully that the ISO-8559-7 character set is used here strictly as an example. ****************************************** * New =* and ^=* mail template operators * ****************************************** Starting with LISTSERV 1.8d, the mail template operators =* and ^=* are available to perform wildcard matches in conditional blocks (i.e., .BB - .EB conditional blocks). For instance JOHN_DOE@UNIX.EXAMPLE.COM =* J*DOE@*EXAMPLE.COM is a true statement. The wildcard specification is on the right-hand side whereas the actual text (or variable) you are evaluating is on the left. These operators are provided primarily for use in mail-merge operations. ************************************************************************ * [non-VM] File indexes now show byte sizes instead of LRECL and NRECS * ************************************************************************ Starting with LISTSERV 1.8d, the output of the INDEX command issued to non-VM servers shows file sizes in bytes instead of the traditional (but VM-specific) LRECL and NRECS fields. ************************************************ * New serial numbering for digests and indexes * ************************************************ Beginning with version 1.8d, LISTSERV digests and indexes now are numbered serially with the year and issue number for that year in the Subject: line. For instance, Subject: MYLIST-L Digest - 20 Aug 1998 to 21 Aug 1998 (#1998-132) Subject: TEST Index - 23 Jul 1998 to 21 Aug 1998 - Special issue (#1998-28) *********************************** * Miscellaneous changes and fixes * *********************************** - There is a new REP option for the PW command (i.e., PW REP newpassword) which acts like PW CHANGE if a password already exists for the user, and acts like PW ADD otherwise. This was added primarily to streamline the web interface but works via mail as well. - If List-ID= is set for a list with web archives, LISTSERV will create HTML pages for both the long and short list names. - If a message without a Subject: line is sent to a list, LISTSERV will now generate a Subject: line with the subject tag for users who have the SUBJECThdr option set. - If Auto-Delete= is set to Max(0) and/or Delay(0), no daily error monitoring report is generated for the list. - A bug in 1.8c under unix and Windows NT that prevented GET with F=MIME/APPL from working properly for binary files has been fixed. - The date format yyyymmdd is now accepted as input for database functions. ------------------------------------------------------------------------- LISTSERV is a registered trademark licensed to L-Soft international, Inc. L-SOFT and LMail are trademarks of L-Soft international. LSMTP is a trademark of L-Soft international, Inc. EASE and CataList are service marks of L-Soft international, Inc. UNIX is a registered trademark of X/Open Company Limited. VMS and OpenVMS are trademarks of Digital Equipment Corporation. Microsoft is a registered trademark of, and Windows, Windows NT and Windows 95 are trademarks of Microsoft Corporation. All other trademarks, both marked and not marked, are the property of their respective owners. -------------------------------------------------------------------------