MAILTPL Explanation
                           Don Wiss, 5/15/98

Most listowners never get around to putting up a MAILTPL. If they don't do
so the Listserv will use a default one, which you should download with the
GET DEFAULT MAILTPL command. But there are some sections that you really
need to put in (like the INFO section), and others that make things nicer. 

There are now two ways to update this file:

(1) On the web at: http://maelstrom.stjohns.edu/CGI/wa.exe?LMGT1=listname

changing listname to the name of one of the lists you own. You will then
have a menu with all the lists you own.

(2) By e-mail. A mailtpl is stored with: PUT <listname> MAILTPL pw=XXXX

L-Soft recommends that you only store as your mailtpl the sections that you
modify. To see if your list already has one send in a GET <listname>
MAILTPL command. If you receive a message stating that the list has one
registered, but that the physical file is not present on the server, then
the list doesn't. It is registered as it is one of the five special files
that is registered by default, i.e. it doesn't need to exist in the catalog
file.

These are the sections that I have modified for my lists. Few listowners
will modify this many. Select out which ones interest you.

The MAILTPL Sections
--------------------
Each section in the mailtpl starts with three >>>'s, a space, then the
section name. In the example mailtpl below there are eight sections. They are:

>>> INFO Information about the &LISTNAME list
>>> PROBE1 &LISTNAME Operating Instructions
>>> SIGNUP1 You are now subscribed to the &LISTNAME list
>>> $SIGNUP Standard blurb to new subscribers
>>> POST_EDITOR Message sent to user when posting is forwarded to editor
>>> REQACK1 Your message to &LISTNAME-request@&MYHOST
>>> WWW_INDEX HTML for the main list archive access screen
>>> $WWW_ARCHIVE_TRAILER Trailer text for WWW archive interface

Then if you want a list with subscription by owner, it is best if you have
them fill out a short questionnaire first. For such a list you would have
these two additional sections:

>>> SUB_OWNER &LISTNAME: &WHOM requested to join
>>> ADDREQ1 &LISTNAME Membership Survey

Discussed in another document (GET OWNR-FAQ.BANNERS) are top and bottom
banners. Also see owner's manual section 9.7.1. These optional sections
would be:

>>> TOP_BANNER
>>> BOTTOM_BANNER

Typically, the top banner would be used for a copyright or short legal
warning which absolutely has to be seen by each and every reader. The
bottom banner could contain instructions for signing off the list, a
disclaimer, an acknowledgement of a sponsor's contribution, a "tip of the
week", etc.

======================

Explanation of the sections:

>>> INFO 

People can send to a Listserv the INFO <listname> command. If this section
isn't in a list's mailtpl, the Listserv will reply with the header, on the
assumption that there is a description in it. People that search for lists
at places like www.liszt.com will be presented with opportunities to issue
the INFO command. Another advantage of following this example, is you can
issue the command and send the result in, as is, to the New List mailing
list. Add the same description that you use in the header at the beginning
of the example below.

>>> PROBE1 

Our hosts have asked that our lists have the probe command in the header.
With this every six months, or as set, the Listserv will send subscribers
messages to check for address validity. This will clean out dead nomails.
The default probes are in the default mailtpl. Rather techy. The one in
this example was written by some listowner and posted to one of the
listowner mailing lists. It could be made shorter and some newer commands
added. Some lists use this probe to resend the policies/mission statement
for the list. It can even alternate between two or more. See section 4.6.2
in the owner's manual for details on the probe option, and section 9.7.2
for rotating a probe.

>>> SIGNUP1 

This is the short e-mail that is sent when a subscription has been
successful. Here it asks them to save the big e-mail, the Welcome message.

>>> $SIGNUP 

This is the standard blurb to new subscribers of lists that don't have
custom welcome messages. We turn it off with the .qq command as it is
redundant to the custom one. It is possible that removing the .im $SIGNUP
line in the template above will have the same effect.

>>> POST_EDITOR 

This message is sent to users when their postings are forwarded to an
editor. Most often this will be when you have the list default to starting
with the review option turned on, or you have put someone on review. The
one in this example was included here as we changed the word moderator to a
more acceptable listowner. It also has removed the singular/plural logic.
Some lists have turned off any notification being sent by replacing the
text with a .QQ command.

>>> REQACK1 

This is a Listserv message that is sent to a user when they send a message
to the &LISTNAME-request@&MYHOST address. It can confuse the user. I have
turned it off with the .QQ.

>>> WWW_INDEX 

This is HTML for the main list archive access screen. This is where you can
have a description of your list appear at the top of your archive page. In
this example the .IM $WWW_ARCHIVE_HEADER line was replaced with a <body
bgcolor="#FFFFFF"> tag. This removed the host's Technology logo image at
the top of the page. We then added a section in the middle with the same
html code that is used in the list header (just without the leading
asterisks). After that we removed the link that applied only to owners.
Note that L-Soft will change this section in updates. You'll then have to
transfer their enhancements to your mailtpl.

>>> $WWW_ARCHIVE_TRAILER 

This is the code for the material below the links to the log file lists -
at the bottom of the page. Here we have removed the images, removed the
link to L-Soft's CataList, and added links to some other relevant pages.
This could be a place to stick in a copyright disclaimer.


These are the two optional sections when subscription by owner:

>>> SUB_OWNER

This is normally a message telling the prospective subscriber that their
request was sent to the listowner. We replace it here with a message
telling them to fill out the questionnaire that was also sent.

>>> ADDREQ1

This is a list description and the questionnaire, or "Membership Survey."
The default has the message that went to the owner telling of the request.
In this example the listowner does not get notification of the
questionnaire request (with the SUB command). It could be added by adding a
cc to the owner in the questionnaire being sent out.

======================

Here is the example:

PUT <listname> MAILTPL pw=XXXX
>>> INFO Information about the &LISTNAME list
.fo off
&LISTNAME is a support list for ...

The purpose of the list will be to share experiences, offer each 
other support, chat about our daily challenges in the spirit of 
sharing knowledge on ...

Archives are kept in monthly files.  You may obtain a list of files
in the archives by sending the command

  GET &LISTNAME FILELIST

in the BODY of e-mail to &MYNAMES

Archives of the postings can be found at:

  http://maelstrom.stjohns.edu/archives/&LISTNAME.html

To subscribe, send in the body of an email to:
  &MYNAMES

  SUB &LISTNAME YourFirstName YourLastName

A digest version is also available.

List Owner: &OWNER
>>> PROBE1 &LISTNAME Operating Instructions
&WEEKDAY, &DATE &TIME

This message is sent as an automatic, periodic reminder to &LISTNAME
subscribers letting them know how to manipulate their subscriptions for
maximum benefit.

Some common commands (which you should send to &MYNAMES if you wish to
invoke them):

SIGNOFF &LISTNAME

This ends your subscription to the list and stops list mail from being sent
to you.

SET &LISTNAME SUBJecthdr

Some subscribers may desire to have the system automatically identify mail
from the List by adding the Listname to the subject line.

SET &LISTNAME NOMAIL

You would use this if you were going on vacation, for instance, and did not
wish to have messages delivered while you were away.  On your return, when
you wanted &LISTNAME to start sending you mail again, you would issue the
same command except with MAIL replacing NOMAIL at the end of it.

SET &LISTNAME DUALHDR

If your e-mail reading software does not reveal the senders' names on your
incoming e-mail, invoke this command.  It causes Listserv to include
relevant header information in the text body of incoming &LISTNAME messages
sent to you.  Note when replying this information should be deleted.

SET &LISTNAME DIGEST

This causes the &LISTNAME to stop forwarding incoming messages to you as it
processes them.  Instead, it sends you one large message on a
&KWD(DIGEST,3) basis that contains any individual messages of the period
strung together end-to-end.  This is useful for subscribers who do not wish
to be bothered by the arrival of random messages, or who find it
time-consuming to open, read, and close individual messages.  To stop
digest delivery and resume "instant" message delivery, just send the same
command except with the word NODIGEST instead of DIGEST at the end.

Please note that this message is sent to all users not only as a brief
operational FAQ, but also as a &LISTNAME subscription "probe."  If this
message "bounces" on its way to a subscriber, or if a subscriber's mail
gateway generates an error while handling this message (and this can happen
even though this message eventually reaches a subscriber), the Listserv
software takes further steps to verify that the subscriber's e-mail address
is in working order (this can be of great benefit to a subscriber who is
unaware that his e-mail account is malfunctioning and possibly not
delivering his mail to him).  The probing mechanism automates error
processing and saves the &LISTNAME owners from having to deal with errors
by hand; for that reason, the &LISTNAME owners ask you to tolerate the
minor inconvenience of receiving this message on a periodic basis.

If you ever have questions or comments about the &LISTNAME list, please
write to the list owners at the generic address:

&OWNER

Thanks again for your interest in &LISTNAME.
>>> SIGNUP1 You are now subscribed to the &LISTNAME list
.re owners
&WEEKDAY, &DATE &TIME

Your subscription to the &LISTNAME list (&TITLE) has been accepted. Please
save the Usage Guidelines that were also sent.
.im $SIGNUP
>>> $SIGNUP Standard blurb to new subscribers
.qq
>>> POST_EDITOR Message sent to user when posting is forwarded to editor
Your &MESSAGE has been submitted to the
listowner of the &LISTNAME list: &MBX(&MODERATOR).
>>> REQACK1 Your message to &LISTNAME-request@&MYHOST
.qq
>>> WWW_INDEX HTML for the main list archive access screen
.FO OFF
<title>Archives of &LISTADDR</title>
<body bgcolor="#FFFFFF">
<center>
<h2>Archives of &LISTADDR</h2>
<h3><i>&TITLE</i></h3>
</center>

<p>PALEOFOOD is a support list for persons following a paleolithic
style diet such as described by Ray Audette in NEANDERTHIN
"A Caveman's Guide to Nutrition" and all other similar approaches
in the spirit of the Hunter-Gatherer.</p>

<p>The purpose of the list will be to share experiences, offer each 
other support, chat about our daily challenges in the spirit of 
sharing knowledge on dietary and health issues of our chosen
lifestyle.</p>

<ul>
.bb &SEARCH ^= ''
<li>&SEARCH;Search the archives</a><p>
.eb
.bb (&KWD(SEND,1) ^= OWNER) and (&KWD(SEND,1) ^= OWNERS)
<li>&POST;Post to the list</a>
.eb
.bb &KWD(SUBSCRIPTION,1) ^= CLOSED
<li>&SUBA;Join or leave the list</a>
.eb
<p>.DD &DD
</ul>
.IM $WWW_ARCHIVE_TRAILER
>>> $WWW_ARCHIVE_TRAILER Trailer text for WWW archive interface
<p><hr><center>

<h3>Also see Archives of <a
href="http://maelstrom.stjohns.edu/archives/paleodiet.html">PaleoDIET:
Paleolithic Diet Symposium List</a></h3>
<h3>Annotated links to other sites: <a
href="http://www.panix.com/~paleodiet/">The Paleolithic Diet Page</a></h3>

<p>Back to the <a href="/archives/index.html">&MYHOST archive index.</a>
</center>

======================

Then for a questionnaire for subscription by owner lists you would add
these two sections.

>>> 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.
>>> ADDREQ1 &LISTNAME Membership Survey
.RE OWNERS
.TO &WHOM
.CE &LISTNAME Membership Survey

NOTE:  Please make sure when you reply to this msg it goes back to
the address &LISTNAME-Request@&MYHOST. Thanks.

Thank you for your interest in the Paleolithic Diet Symposium listserv. Our
list is an semi-private, semi-moderated symposium for researchers with
interest in and knowledge of primitive diets and their relevance to modern
life. Our primary audience is biologists, paleontologists, anthropologists,
physiologists, and health care professionals. Students or members the lay
public are not necessarily excluded, but any messages submitted to the list
membership will be reviewed before distribution to assure that the
information presented, or the questions posed, reflect an appropriate level
of understanding of the science underlying the subject under discussion.

Note that there is also an unmoderated  SUPPORT oriented list under the 
name of PALEOFOOD. That may be what you are looking for.

This is a standard questionnaire for all prospective subscribers to
&LISTNAME. You are not required to give us more than your name and email
address, although we would appreciate having the other information. Any
information you give on this questionnaire is solely for the list owners'
information, and will NOT be sold or used for any form of business
solicitation.

.fo off
   Name:
   Preferred E-mail Address:
   Title:
   Institution:
   Phone Number:
   Research Areas:
   Other Areas of Interest:
.fo on

.ce --------------
Your list membership will be confirmed by the Listowner. You should
receive a message confirming your membership within a few days. Thank you!