1 March 1999
Initial Release

The reference number of this document is 9903-UD-02.

Table of Contents

Preface: LISTSERV Command Syntax Conventions

1. About Mailing Lists and LISTSERV

2. Starting a Mailing List -- The Basics

3. Advertising Your Public Mailing Lists

4. Managing Subscriptions

5. Setting Subscription Options For Subscribers

6. Moderating and Editing Lists

7. Overview of List Archives

8. Overview of File Archives

9. Customizing LISTSERV's Default Mail Templates

10. Solving Problems

11. Using the Web Adminstration Interface

Appendix A: LISTSERV Command Reference for LISTSERV® version 1.8d

Appendix B: List Keyword Alphabetical Reference for LISTSERV® version 1.8d

Appendix C: Sample Boilerplate Files

Appendix D: Related Documentation and Support

Appendix E: Acknowledgments

1 March 1999
Initial Release

All Rights Reserved Worldwide

The reference number of this document is 9903-UD-02.

Preface: LISTSERV Command Syntax Conventions

fformat	Netdata, Card, Disk, Punch, LPunch, UUencode, XXencode, VMSdump, MIME/text, MIME/Appl, Mail
full_name	first_name [middle_initial] surname (not your e-mail address)
listname	name of an existing list
node	Either: the fully-qualified domain name (FQDN) of an Internet host; or the BITNET nodeid or Internet hostname of a BITNET machine which has taken care of supplying an ':internet' tag in its BITEARN NODES entry;
host	Generally the same as node, but normally refers specificallly to the fully-qualified domain name (FQDN) of an Internet host rather than to a BITNET nodeid.
pw	a password containing characters from the set: A-Z 0-9 $#@_-?!|%
userid	Any valid RFC822 network address not longer than 80 characters; if omitted, the 'hostname' part defaults to that of the command originator

italic type	always indicates required parameter names that must be replaced by appropriate data when sending commands to LISTSERV
< >	Angle brackets may sometimes enclose required parameter names that must be replaced by appropriate data when sending commands to LISTSERV. Sometimes used for clarity when italic type is inappropriate
[ ]	Square brackets enclose optional parameters which, if used, must be replaced by appropriate data when sending commands to LISTSERV

1. About Mailing Lists and LISTSERV

2. Starting a Mailing List -- The Basics

2.1. Avoid duplication of effort ¹

LISTS GLOBAL search_string

 Excerpt from the LISTSERV lists known to LISTSERV@PEACH.EASE.LSOFT.COM
 ----------------------------------------------------------------------
                            30 Aug 1996 12:50

                          (search string: IBM)

                Copyright 1996 L-Soft international, Inc.

L-Soft international, Inc. owns the copyright to this compilation of
Internet mailing lists (the "Compilation") and hereby grants you the
right to copy the enclosed information for the sole purpose of
identifying, locating and subscribing to mailing lists of interest. Any
other usages of the Compilation, including, without limitation,
solicitation, tele-marketing, "spamming", "mail-bombing" and "spoofing"
are strictly prohibited.

***********************************************************************
* To subscribe, send mail to LISTSERV@LISTSERV.NET with the following *
* command in the text (not the subject) of your message:              *
*                                                                     *
*                         SUBSCRIBE listname                          *
*                                                                     *
* Replace 'listname' with the name in the first column of the table.  *
***********************************************************************

Network-wide ID  Full address and list description
---------------  ---------------------------------
9370-L           9370-L@NIC.SURFNET.NL
                 IBM 9370 and VM/IS specific topics list

• Check the NEW-LIST archive on SCOUT.CS.WISC.EDU, where the NEW-LIST project (originally at North Dakota State University, now hosted by the Internet Scout Project) stores list announcements starting with July 1998². The NEW-LIST archive contains information about LISTSERV lists as well as about lists running on other types of servers. This information is accessible either via LISTSERV database searches or on the web at

  http://SCOUT.CS.WISC.EDU/scout/new-list/

• Get a copy of the Interest Groups List of Lists maintained by SRI on its server at sri.com. Note that this is a 500KB (or larger) file. As of 6 March 1998 this file had not been updated for two years.
  ftp sri.com
  user: anonymous
  password: your_user_id
  cd netinfo
  get interest-groups

• Check the Usenet newsgroups news.announce.newusers and news.lists , if they are available to you via your local news feed.

• Use one of the World Wide Web search engines such as Alta Vista or Yahoo! to search for matches to the name you want to use.

2.2. What skills do I need to start and maintain a LISTSERV mailing list?

2.3. Creating a mailing list -- Where can it be done, and Who can do it?

• First, find out if your computing center maintains a LISTSERV host.

• If not, you might consider a commercial LISTSERV site. There are a number of such sites, including L-Soft's own EASE^SM service. You can get more information on EASE^SM by pointing a WWW browser at

  http://www.lsoft.com/ease-head.html

!	which can be confused for "bang-path" addressing, e.g., UUCP
@	which is a reserved character
#	which can cause problems with some mail software which uses it for addressing
$	which may have a special meaning to the unix shell
%	another addressing character that could cause problems
&	is sometimes reserved by non-unix systems (specifically on NT it has a special meaning to the shell). However, please note that use of this character in the name of a list or in a sendmail alias for a list will cause LISTSERV on unix to choke. Note that it is possible under unix to create a list with a "&" character in the name quite easily, and it is also possible to create a sendmail alias with a "&" character in the alias. That does not mean it will work.
*	is, of course, the wildcard character.
()	Parenthesis are generally reserved and can't be used in file names.
+	The plus character should be avoided because recent versions of sendmail deliver mail addressed to "user+whatever@somedomain" to "user@somedomain." Whether or not this is an intelligent thing to do on sendmail's part is left as an exercise for the user, but it can affect mail being sent to a list with a "+" character in the listname.
/	The slash character is reserved and can't be used in file names.
.	Although on some systems it is physically possible to create lists with a dot character in the name, in general LISTSERV will not accept this nomenclature. The only place a dot can or should be used is before the word "LIST" in the PUT command; e.g., PUT MYLIST-L.LIST is equivalent to PUT MYLIST-L LIST.
"	Double-quote characters are not allowed.

VM:	8 characters
Non-VM:	unlimited (starting with 1.8c)

2.4. List Header Keywords and what they do

2.5. Sending commands to LISTSERV

2.6. Defining Personal Passwords

• Personal Passwords. LISTSERV can store a personal password in its signup files corresponding to your userid. This password not only can be used for list maintenance operations, but also protects your FUI (file update information) and AFD (automatic file distribution) subscriptions (if available on your server) and must be used to store your archive files, if any, on the server.

• List Passwords. Beginning with 1.8c, list passwords are obsolete (we are mentioning them here only because users upgrading from earlier versions will be aware of their existence). You should define and use a personal password for all protected operations.

PW ADD newpassword

PW RESET

PW CHANGE newpassword [PW=oldpassword]

2.7. Retrieving the list -- some considerations

GET listname (HEADER

• Issue the UNLOCK listname command (if you decide no changes are needed)

• Send the list back to the server with the PUT command.

GET listname (HEADER NOLOCK

• Don't use the (NOLOCK switch if you are not the sole owner of the list. This prevents conflicting GETs and PUTs by different list owners. For instance, Owner(A) GETs the list without locking it. Owner(B) then also GETs the list. The owners make differing changes to the list header. Owner(B) PUTs his changes back first. Owner(A) then PUTs his changes back, erasing every change Owner(B) made. If Owner(A) had not used the (NOLOCK switch, Owner(B) would not have been able to GET a copy of the list until Owner(A) either unlocked the list or PUT his copy back. (Owner(B) could also unlock the list himself, but it would be advisable to ask Owner(A) if he was finished editing the list header before doing so.)

• Don't use the (NOLOCK switch if you get the entire list rather than just the header. You will erase all subscriptions for users who subscribed between the time you GET the list and PUT the list back. It is easier to deal with questions as to why they got the "listname has been locked since time by list-owner" message than to explain why they got a subscription confirmation and now aren't getting list mail.

DELETE XYZ-L "/ADMD=ABC/PRMD=DEF/...../@X400.SOMEHOST.COM"

GET listname (options PW=password

GET MYLIST-L (HEADER NOLOCK PW=MYPASSWORD

2.8. Editing the list header

GET MYLIST (HEADER PW=MYPASSWD

PUT MYLIST.LIST PW=XXXXXXXX
* The Descriptive Title of My List
*
* Owner= NATHAN@LSOFT.COM (Nathan Brindle)
* Notebook= Yes,E:\LISTS\MYLIST-L,Monthly,Public
* Errors-To= Owner                  Send= Public
* Subscription= Open,Confirm        Ack= Yes             Confidential= No
* Validate= No                      Notify= No           Reply-to= List,Respect
* Review= Public                    Default-Options= NoFiles,NoRepro
*
* This list installed on 96/11/02, running under L-Soft's LISTSERV
* for Windows NT.
*
* Comment lines...
*

• Cut and paste the header from your mail program into an ASCII text editor such as vi, emacs, or Notepad. Edit the various keyword values and set the password in the PUT command appropriately. Finally, cut and paste from your editor into a new mail message addressed to LISTSERV and send the message.

• Cut and paste from your mail program into the body of a new mail message addressed to LISTSERV and do your editing in the mail program.

• If you use the 'mail' or 'mailx' programs under unix, you can save the header into a text file (for instance, named myheader.txt) and mail it back to LISTSERV with the command line syntax

  mail listserv@myhost.com < myheader.txt

PUT MYLIST.LIST PW=MYPASSWD
* The Descriptive Title of My List
*
* Owner= NATHAN@LSOFT.COM (Nathan Brindle)
* Owner= Quiet:,nathan@linus.dc.lsoft.com,ncbnet@linus.dc.lsoft.com
* Notebook= Yes,A,Monthly,Public          Auto-Delete= Yes,Full-Auto
* Errors-To= ncbnet@linus.dc.lsoft.com    Subscription= Open,Confirm
* Ack= Yes                 Confidential= No              Notify= No
* Validate= Yes,Confirm
* Reply-to= List,Respect   Review= Public                Send= Public
* Default-Options= NoFiles,NoRepro
*
* This list installed on 96/11/02, running under L-Soft's LISTSERV
* for Windows NT.
*
* Comment lines...
*

• You sent the header back from an account which is not defined as a list owner

• You used the wrong password or didn't specify a password in the PUT command

• Your mail program indents paragraphs by default, such that each header line does not start in column 1 and LISTSERV does not recognize your message as a list header

• You sent the header file back as an attachment rather than as plain text in the body of the message.

• Your mail client wrapped the lines of the header so that LISTSERV received header lines that did not begin with "*" and attempted to treat them as subscriber addresses. In this case you can probably solve the problem by increasing the right margin setting in your mail client so that messages at least 80 columns wide do not get wrapped.

2.9. Defining list owners

• Non-Quiet list owners receive mail sent to the listname-request address, and will receive error messages if Errors-To= Owners.

• Quiet list owners will never receive delivery errors or other administrative mail from LISTSERV.

* Owner= NATHAN@LSOFT.COM (Nathan Brindle)
* Owner= nathan@linus.dc.lsoft.com
* Owner= Quiet:
* Owner= ncbnet@linus.dc.lsoft.com,cheng@linus.dc.lsoft.com

2.10. Storing the list on the host machine

2.11. Fixing mistakes

2.12. Security Options

* Service= bitnode1,bitnode2,some.host.edu
* Confidential= SERVICE

* Local= bitnode1,bitnode2,some.host.edu,another.host.com
* Service= Local
* Confidential= Service

• Send= Editor forwards all postings to the list editor (see the Editor= and Moderator= keywords). This setting allows the editor to make changes before forwarding the message back to the list. Note that your mail program must be capable of inserting "Resent-" header lines in your forwarded mail--if it is not capable of this, all such posts forwarded to the list will appear to be coming from the editor. Check with your system administrator if you are not sure whether or not your mail program inserts the "Resent-" headers.

• Send= Editor,Hold forwards a copy of the posting to the editor but differs from Send= Editor in that LISTSERV holds the posting for a period of time (usually 7 days) until the editor confirms the message with the "OK" mechanism (see below). Unconfirmed messages simply expire and are flushed by LISTSERV, so there is no need to formally disapprove a posting. This method of message confirmation is well-suited to lists where it is not often necessary to modify the text of a posting, and also is an excellent workaround if the editor's mail program does not generate "Resent-" headers in forwarded mail.
  Below is a sample of the editor-header for a list set to Send= Editor,Hold:

  Date: Tue, 4 Aug 1998 10:47:21 -0500 From: "L-Soft list server at PEACH.EASE.LSOFT.COM (1.8d)" <LISTSERV@PEACH.EASE.LSOFT.COM> Subject: B5-L: approval required (9723A0DD) To: Joe ListOwner <joe@PRUNE.EXAMPLE.COM> This message was originally submitted by jack@UNIX.FOO.COM to the B5-L list at PEACH.EASE.LSOFT.COM. You can approve it using the "OK" mechanism, ignore it, or repost an edited copy. The message will expire automatically and you do not need to do anything if you just want to discard it. Please refer to the list owner's guide if you are not familiar with the "OK" mechanism; these instructions are being kept purposefully short for your convenience in processing large numbers of messages. ----------------- Original message (ID=9723A0DD) (13 lines) -------------------

  Figure 2.5. The editor-header for a list set to Send= Editor,Hold

• Send= Editor,Hold,Confirm is identical to Send= Editor,Hold except that postings coming directly from an editor must be confirmed (with the "OK" mechanism) by the editor who sent the message. This is the recommended setting for any moderated list or announce-only list as it protects the list from hackers who might try to forge mail from a legitimate editor address.

* Send= Editor
* Editor= userid@host,(listname)

Date:         Wed, 5 Aug 1998 09:50:06 -0400
From:         "L-Soft list server at LISTSERV.EXAMPLE.COM (1.8d)"
              <LISTSERV@LISTSERV.EXAMPLE.COM>
Subject:      Command confirmation request (5C019D91)
To:           joe_user@EXAMPLE.COM

Your command:

                             PW REP XXXXXXXX

requires confirmation. To  confirm the execution of  your command, simply
point your browser to the following URL:

         http://listserv.example.com/scripts/wa.exe?OK=5C019D91

Alternatively, if  you have no WWW  access, you can reply  to the present
message and type  "ok" (without the quotes) as the  text of your message.
Just the word "ok" - do not  retype the command. This procedure will work
with any mail  program that fully conforms to the  Internet standards for
electronic  mail. If  you receive  an error  message, try  sending a  new
message  to  LISTSERV@LISTSERV.EXAMPLE.COM  (without  using  the  "reply"
function - this is very important) and  type "ok 5C019D91" as the text of
your message.

Finally, your  command will be  cancelled automatically if  LISTSERV does
not receive your confirmation within 48h. After that time, you must start
over and resend the command to get a new confirmation code. If you change
your mind and decide that you do  NOT want to confirm the command, simply
discard the present message and let the request expire on its own.

• Under 1.8d and following, the suggested method is to use the web browser confirmation method outlined in the confirmation request.

• REPLY to the command confirmation request with the text "ok" in the body of the reply. (Non-case-sensitive) LISTSERV reads the "cookie" from the subject line and if it corresponds to a held job, the job is released and processed.

SEND a new message to LISTSERV with the text "ok xxxxxx" (where xxxxxx is the command confirmation number from the original confirmation request) in the body of the reply.

> ok
Confirming:
> QUIET DELETE * jane@example.com
[reply sent to joe@EXAMPLE.COM]

jane@EXAMPLE.COM has been removed from the TEST list. No notification has
been sent.

Global deletion process complete, one entry removed.

• 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.

• 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
  [more commands, one per line]
  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).

1. The REVIEW personal option setting. By issuing a SET listname REVIEW FOR userid@host command to LISTSERV, you can moderate postings at the individual subscriber level. Postings from subscribers set to REVIEW are passed on to the Editor(s) or Moderator(s) of the list, or, if neither of these keywords are defined for your list, the postings are passed on to the primary list owner. At this point, the person who receives the postings can determine whether or not to approve them. Note that the subscriber always receives notification that his or her posting has been forwarded to a moderator for approval. This is to avoid the impression that the subscriber's posting has been lost before reaching LISTSERV.

2. The NOPOST personal option setting. By issuing a SET listname NOPOST FOR userid@host command to LISTSERV, you can prevent a subscriber from posting to the list entirely. LISTSERV will reject postings from these subscribers and will not pass them on to a moderator. As with the REVIEW setting, note that the subscriber always receives notification that his or her posting has been rejected.

3. The FILTER= list header keyword. You can filter individual users from subscribing and/or posting to your list by adding them to the Filter= list header keyword. For instance, if you have a list called MACTALK-L and you want to discourage redistribution lists from using the same name as your list, you can add
   * Filter= Also,MACTALK-L@*

2.13. How to set up lists for specific purposes

* My public discussion list (MYLIST-L)
* Subscription= Open,Confirm
* Ack= Yes
* Confidential= No
* Validate= No
* Reply-to= List,Respect
* Review= Owners        Send= Public      Errors-To= Owner
* Owner= joe@example.com
* Notebook= Yes,E:\LISTS\MYLIST-L,Weekly,Public

* My private discussion list (PRIVATE-L)
* Subscription= By Owner
* Ack= Yes
* Confidential= Service
* Validate= No
* Reply-to= List,Respect
* Review= Owners
* Send= Private
* Errors-To= Owner
* Owner= joe@example.com
* Notebook= Yes,E:\LISTS\PRIVATE-L,Weekly,Public

* Send= Editor
* Editor= someuser@somehost.com

* Editor= someuser@somehost.com,anotheruser@anotherhost.com
* Editor= yetanotheruser@his.host.com

* Send= Editor,Hold

* Send= Editor,Confirm

* Send= Editor,Hold,Confirm

* Send= Editor,Confirm
* Editor= someuser@somehost.com
* Moderator= someuser@somehost.com,anotheruser@anotherhost.com
* Moderator= yetanotheruser@his.host.com

* Send= Editor,Confirm
* Editor= someuser@somehost.com
* Moderator= someuser@somehost.com,anotheruser@anotherhost.com
* Moderator= someuser@somehost.com,yetanotheruser@his.host.com

* Moderator= All,kent@net.police.net,joe@bar.edu

* Moderator= kent@net.police.net,All,joe@bar.edu,alex@reges.com

* Send= Editor,Confirm
* Editor= someone@someplace.com,(listname)

* Auto-responder for service messages
* Owner= someone@someplace.com
* Send= Public     Notebook= No     Subscription= Closed

>>> POSTACK1 Service Message for &MYNAMES
&MYNAMES will be down Sunday from 0200 EST until 0500 EST for backups 
and upgrades. For more information contact LSTMAINT@&MYHOST.

* The FOO Product Announcment List
*
* Owner= foo@myhost.com
* Owner= Quiet:
* Owner= anotheruser@myhost.com,yetanotheruser@myhost.com
* Editor= foo@myhost.com
* Editor= anotheruser@myhost.com,yetanotheruser@myhost.com
* Notebook= No
* Errors-To= Owner
* Subscription= Open,Confirm
* Validate= No
* Review= Owners
* Send= Editor,Confirm
* Reply-To= foo@myhost.com,Ignore
* Sender= None

>>> SUB_OWNER &LISTNAME: &WHOM requested to join
.TO &WHOM
A copy of the &LISTNAME membership questionnaire has been sent
to you.  Please read it carefully and follow the instructions
to complete it and return it to the list owners.

.TO &WHOM CC: &OWNERS

.TO &WHOM CC: joe@unix1.example.com

>>> ADDREQ1 &LISTNAME Membership Survey
.RE OWNERS
.TO &WHOM
.CE &LISTNAME Membership Survey
NOTE:  Please make sure when you send this back that it goes to
the address &LISTNAME-Request@&MYHOST.  Thanks.

This is a standard questionnaire required for all prospective
subscribers to &LISTNAME. Blah blah blah...

.fo off
----------------------------------------------------------------
For List Owner's Use Only --  Be sure to include with your Reply
----------------------------------------------------------------
// JOB
  ADD &LISTNAME &WHOM &USERNAME
// EOJ
----------------------------------------------------------------
.fo on

The approval request code received together  with your posting for the MYLIST-L
list is  incorrect. For  a peered  list, this  may be  a normal  condition. The
approval protocol  is not  guaranteed to  work among  peer chains with pre-1.8b
servers, and  will also  fail if  the peers  have a  different password.  For a
non-peered list, the only likely explanation is a failure in the mail system or
a recent change in mail  system version or  configuration. At any  rate, please
resubmit your message and go through  the approval procedure a second time, and
contact the LISTSERV administrator if the problem persists.

------------------------ Rejected message (73 lines) --------------------------

1. NOMAIL subscriptions are ignored. You will get the super-message if you have an active (not NOMAIL) subscription to at least one sub-list. The idea is that the super-message must be equivalent to posting to all the sub-lists, without the duplicates. Since all it takes to get a message posted to all the sub-lists is a single non-NOMAIL subscription, this is how the super-list works. The only way not to get the super-messages is to subscribe to the super-list directly and set yourself to NOMAIL.

2. The DIGEST and INDEX options are ignored and internally converted to MAIL. The first reason is that, since in most cases the user will be on multiple sub-lists (otherwise you don't need a super-list in the first place), the only safe method to set subscription options for super-messages is by subscribing to the super-list so that there is no ambiguity. The second reason is that, in most cases, super-lists will be used for out of band administrative messages rather than for large volume discussions, so it is actually preferable to have the message sent directly. The third reason is that the super-list and sub-lists may not necessarily offer the same options (DIGEST and INDEX). In particular it is expected that many super-lists will not have archives. If you want a DIGEST or INDEX for the super-messages, you must subscribe to the super-list directly.

* Notebook= Yes,C:\LISTS\SUPER,Monthly,Private,(SUB-A),(SUB-B)
* Notebook= (SUB-C),(SUB-D),(SUB-E),(SUB-F)

PUT M101 KEYWORDS PW=createpw
* Owner= mathwhiz@someuni.edu (Professor J. Random User)
* Owner= Quiet:
* Owner= gradasst@someuni.edu (Joe Doakes, Graduate Assistant)
* Notebook= Yes,/home/listserv/archives/m101,Monthly,Private
* Auto-Delete= No
* Errors-To= gradasst@someuni.edu
* Subscription= Closed
* Notify= Yes               Confidential= Yes        Validate= Yes,Confirm,NoPW
* Reply-to= List,Ignore     Review= Owners           Send= Private
* Default-Options= Repro

PUT M101-001 LIST PW=createpw
* Math 101 Section 001 Mailing List
* .IK M101

2.14. List passwords are now obsolete

2.15. Allowing/Blocking MIME Attachments

• Allow all MIME attachments, no filtering or blocking
• Reject MIME attachments with notice to the poster
• Filter MIME attachments out of messages transparently

For information on the various settings, please see the section on the Attachments= keyword in Appendix B of this manual.

3. Advertising Your Public Mailing Lists

3.1. Lists of Lists maintained by LISTSERV

L-Soft's CataList service at http://www.lsoft.com/CataList.html
The LISTS GLOBAL searchtext command. This list of lists is made up of one-line entries containing the short listname and the descriptive title of the list (up to about 60 characters in length). A sample of the List of Lists format was shown in Chapter 2.

3.2. Adding HTML to a list header for the CataList

* The coffee lovers' list
*
* Review= Public    Subscription= Open         Send= Public
* Notify= Yes       Reply-to= List,Respect
* Notebook= Yes,L,Monthly,Public
*
* Owner=  claudia@espresso.xyz.it (Claudia Serafino)
*
* <HTML>
* COFFEE-LOVERS is an open list for, well, coffee lovers! Our
* motto is: <cite>"Instant -- just say no!"</cite>
* That's pretty much our whole charter, although there are a
* few other <a href="http://www.coffee.org/charter.html">
* rules</a> that you may want to read before joining. For
* instance, we don't allow flame wars about decaf: if you like it,
* well, it's your body after all.
*
* <p>The list is maintained by
* <a href="http://www.coffee.org/claudia.html">Claudia
* Serafino</a> (that's me!) and you will find all sorts of
* useful info about coffee on my home page.
* </HTML>
*

1. The <HTML> and </HTML> tags must appear on a separate line, as shown in the example above. You cannot have anything else on that line and, in particular, you cannot mix keyword definitions with HTML data.

2. The HTML data you are providing is embedded into the document shown by the web interface when users query your list. Because you are given some space between two horizontal rules on an existing page, rather than a whole new page. you should not include tags that affect the whole document, like for instance <TITLE>.

3. While this procedure is compatible with all versions of LISTSERV, there are a few restrictions on the placement of equal signs within your HTML text with versions that do not have any specific support for the <HTML> and </HTML> markers. In practice, you can ignore this rule unless you get an error message while storing your list.