A new version of LISTSERV will be released early next year to take advantage of new LMail functionality. I am enclosing a sample message that illustrates the two main functions, "safe" lists and automatic deletion of old accounts. Since version 1.7e, LISTSERV has been submitting mail to its mailer exclusively via BSMTP. This was done in order to avoid having to duplicate work when converting some mail delivery internals from REXX to PASCAL, but we can now take advantage of this more powerful interface. When running with LMail or with a patched version of release 2.08 of the Crosswell/Wagner mailer, LISTSERV implements the owner-listname and listname-request "list control lists" described in the 1.7b release notes. In the next release it will be possible to code "Safe= Yes" in the mail header to ask LISTSERV to generate a BSMTP origin of owner-listname for all types of headers, while keeping the usual settings for the 'Sender:' field. This will not be the default option at first, because the associated control lists work only if you are running LMail or a modified Crosswell/Wagner mailer. The next version will also include code to automatically process the nondelivery reports generated by LMail and delete users for which a permanent delivery error was reported. This feature will be activated by the "Auto-Delete= Yes" list header keyword, which will be the default for "Validate= Store only" and is not recommended if you use "Validate= All commands". Here is an example: ------------------------------------------------------------------------- Date: Thu, 3 Dec 1992 00:09:17 +0100 From: Revised List Processor (1.7e) <[log in to unmask]> Subject: L202: X@Y auto-deleted To: Eric Thomas <[log in to unmask]> X-LSV-ListID: None The following users have been removed ("auto-deleted", in list owner jargon) from the L202 list as a result of the nondelivery error report enclosed below. No action is required from you; this message is only for your information. List of deleted users: Test entry <[log in to unmask]> ------------------------ Nondelivery report (33 lines) ------------------------ Return-Path: <> Received: from SEARN.BITNET (NJE origin L@SEARN) by SEARN.SUNET.SE (LMail V1.0a/ 1.7e) with BSMTP id 2003; Thu, 3 Dec 1992 00:09:14 +0100 Return-Path: <> Received: from SEARN.SUNET.SE (NJE origin M@SEARN) by SEARN.SUNET.SE (LMail V1.0a/1.7e) with BSMTP id 2001; Thu, 3 Dec 1992 00:09:14 +0100 Date: Thu, 3 Dec 1992 00:09:13 +0100 Reply-To: [log in to unmask] From: RFC822 mailer (LMail release 1.0a/1.7e) <[log in to unmask]> Subject: Undelivered mail To: [log in to unmask] X-Report-Type: Nondelivery; boundary="> Error description:" An error was detected while processing the enclosed message. A list of the affected recipients follows. This list is in a special format that allows software like LISTSERV to automatically take action on incorrect addresses; you can safely ignore the numeric codes. --> Error description: Error-For: [log in to unmask] Error-Code: 1 Error-Text: Node Y is unknown as of VERS9212. Error-End: One error reported. ------------------------- Rejected message (8 lines) -------------------------- Date: Thu, 3 Dec 1992 00:09:07 +0100 Reply-To: SEARN 202 list <[log in to unmask]>, [log in to unmask] Sender: SEARN 202 list <[log in to unmask]> From: [log in to unmask] Subject: Test subject To: Multiple recipients of list L202 <[log in to unmask]> Test mail -------------------------------------------------------------------------