#$Id: ezmlmrc,v 1.35 1998/03/08 03:56:34 lindberg Exp $
#Name:$
#
# ezmlmrc 
# #######
# Controls the actions of ezmlm-make as patched with ezmlm-idx-0.20 or later.
#
# The base directory 'DIR' is always created by ezmlm-make, as is DIR/key.
# Everything else is done from here.
#
# ezmlm-make looks for this file, first as .ezmlmrc in the directory that the
# lists .qmail files will be placed in (if you've used the -c command line
# switch), then /etc/ezmlmrc, then ezmlmrc in the ezmlm-make binary directory.
# Thus, you can customize ezmlm-make on a global level by placing a customized
# copy of ezmlmrc in /etc and on a user level by copying it to .ezmlmrc in
# the user's home directory AND use the ezmlm-make -x switch.
#
# Tags are:
#	</filename/>       : put succeeding text lines in DIR/filename
#	</-filename/>      : erase DIR/filename.
#	</+dirname/>       : create directory DIR/dirname
#	</:lname/dirname>  : symlink DIR/.qmail-list-lname -> DIR/dirname
#
# The name in the tag can be suffixed with '#' and any number of flags,
# corresponding to command line switches. The item will be created/extended
# only if all the flags listed are set. Files can be extended as long as they
# were the last one created, but not if another file has been started since
# then. Flags that are not recognized are silently ignored.
# 
# Thus, </filename#aP/> creates the file if and only if the list is archived
# (-a) and not public (-P). If the next tag is </filename#m/>, the file is
# extended with the lines up to the next tag if the list is message moderated
# (-m). If the next tag is </another/>, 'filename' is closed. Any further
# tags leading to the reopenining of 'filename' will overwrite the file, not
# extend it.
#
# A set of user-defined command line switches (xX, yY, zZ) are available for
# customization.
#
# Within the text, certain tags are substituted. Other tags are copied as
# is. <#A#> and <#R#> are substituted by ezmlm-manage and -store (see man pages)
# and <#l#> (lower case L) is replaced dynamically by the list name for
# programs handling both 'list' and 'list-digest'.
#
# Substitutions are:
# <#B#> ezmlm binaries path   <#C#> digest code         <#D#> dir
# <#H#> host                  <#L#> local               <#F#> flags
# <#T#> dot                   <#0#> arg for -0. <#3#>...<#9#> arg for -3..9
# <#1#> ext1                  <#2#> ext2 [if dot is /path/.qmail-ext1-ext2-name]
# The latter useful when a single user is controlling several virtual domains.
#
# -0 is used for the main list address when setting up sublists
# -4 for specifying the ezmlm-tstdig switches used in dir/editor. Default
#    -k64 -m30 -t24. Only used if -g is used.
# -5 for list-owner address. Mail to list-owner will be forwarded to this addr.
# -7 for contents of DIR/modpost
# -8 for contents of DIR/modsub
# -9 for contents of DIR/remote
#
# For demonstration purposes, the '-x' switch results in the following
# non-standard actions:
# - A few references to the list owner are added to the texts.
# - DIR/headeradd is set up to add a reply-to: list@host header.
# - DIR/headerremove removes reply-to headers.
# - reply addresses for (un)sub, reject/accept have mailto:prefixes.
#
# Attempts to create links or directories that already exist, will result
# in a FATAL error. Attempts to open files that have already been closed
# or already exits, will cause the old file to be overwritten.
#
# One of the major problems with ezmlm-lists is DIR/inlocal. For normal
# users, it is set up to the list name (user-list or so), which is correct.
# However, for user 'ezmlm' in control of virtual domain 'host.dom.com'
# the list name is 'list@host.dom.com', but inlocal should be 'ezmlm-list',
# not 'list'. Similarly, if ezmlm-domain1 is in control of 'host.dom.com,
# list@host.dom.com, should yield an inlocal of 'ezmlm-domain1-list'. To
# always get the lists correct, place this file as '.ezmlmrc' in the 
# users home directory (~ezmlm/.ezmlmrc) and change the inlocal text below
# to 'ezmlm-<#L#>' or 'ezmlm-<#1#>-<#L#>, respectively.
# config to support future editing withour giving ezmlm-make command line
# arguments other than dir. Useful for GUI/WWW editing tools
</config/>
F:<#F#>
D:<#D#>
T:<#T#>
L:<#L#>
H:<#H#>
C:<#C#>
0:<#0#>
3:<#3#>
4:<#4#>
5:<#5#>
6:<#6#>
7:<#7#>
8:<#8#>
9:<#9#>
</inlocal/>
<#L#>
</sublist#0/>
<#0#>
</+archive/>
</+subscribers/>
</+bounce/>
</+text/>
# dirs for digests
</+digest/>
</+digest/subscribers/>
</+digest/bounce/>
# for extra address db
</+extra/>
</+extra/subscribers/>
# for blacklist
</+blacklist#k/>
</+blacklist/subscribers#k/>
# moderator db & mod queue dirs
</+mod/>
</+mod/subscribers/>
</+mod/pending/>
</+mod/accepted/>
</+mod/rejected/>
# links: dot -> dir/editor
</:/editor/>
</:-owner/owner/>
</:-digest-owner/owner/>
</:-return-default/bouncer/>
</:-digest-return-default/bouncer/>
</:-default/manager/>
# for message moderation only
</:-accept-default/moderator#m/>
</:-reject-default/moderator#m/>
# Get rid of configuration flags for editing mode so we can start with a
# clean slate.
</-modpost#eM/>
</-modsub#eS/>
</-remote#eR/>
</-public#eP/>
</-indexed#eI/>
</-archived#eA/>
</-prefix#eF/>
</-text/trailer#eT/>
</-sublist#e^0/>
</-mimeremove#eX/>
# subscription moderation
</modsub#s/>
<#8#>
# remote admin
</remote#r/>
<#9#>
# message moderation
</modpost#m/>
<#7#>
# List owner mail
</owner#5/>
<#5#>
</owner#^5/>
<#D#>/Mailbox
<//>
|<#B#>/ezmlm-warn '<#D#>' || exit 0
# Handles subscription. Add flags if you want a non-default digest format.
# Service subject commands to the # request address if the -q switch is given.
# Also -l and -d enable subscriber listing/text file editing, for remote adms.
# -u gives subscriber only archive access
</manager#iG/>
|<#B#>/ezmlm-get '<#D#>' <#C#>
</manager#ig/>
|<#B#>/ezmlm-get -s '<#D#>' <#C#>
</manager#q/>
|<#B#>/ezmlm-request '<#D#>'
# Ok to add -l/-d even for non-mod lists, since ezmlm-manage
# won't allow it unless there are remote admins.
</manager#LN/>
|<#B#>/ezmlm-manage '<#D#>'
</manager#lN/>
|<#B#>/ezmlm-manage -l '<#D#>'
</manager#Ln/>
|<#B#>/ezmlm-manage -e '<#D#>'
</manager#ln/>
|<#B#>/ezmlm-manage -le '<#D#>'
</manager/>
|<#B#>/ezmlm-warn '<#D#>' || exit 0
</#d/>
|<#B#>/ezmlm-warn -d '<#D#>' || exit 0
</editor#X/>
|<#B#>/ezmlm-reject
</editor#x/>
|<#B#>/ezmlm-reject '<#D#>'
# -k => silently ignore posts from blacklisted addresses. Done for moderated
# lists as well - allows removal of unwanted noise.
</#k/>
|<#B#>/ezmlm-issubn -n '<#D#>/blacklist' || { echo "Sorry, I've been told to reject your posts. Contact <#L#>-owner@<#H#> if you have questions about this."; exit 100 }
# switch -u=> restrict to subs of list & digest. If not m
# do it with ezmlm-issubn, if 'm' do it with ezmlm-gate
</#uM/>
|<#B#>/ezmlm-issubn '<#D#>' '<#D#>/digest' '<#D#>/extra' || { echo "Sorry, only subscribers may post. If you are a subscriber, please forward this message to <#L#>-owner@<#H#> to get your new address included."; exit 100 }
</#um/>
|<#B#>/ezmlm-gate '<#D#>' '<#D#>' '<#D#>/digest' '<#D#>/extra'
# For message moderation, editor has store/clean
</#mU/>
|<#B#>/ezmlm-store '<#D#>'
|<#B#>/ezmlm-clean '<#D#>' || exit 0
</#mu/>
|<#B#>/ezmlm-clean -R '<#D#>' || exit 0
# for non-message moderated lists, it has send
</#M/>
|<#B#>/ezmlm-send '<#D#>'
# all lists have warn.
<//>
|<#B#>/ezmlm-warn '<#D#>' || exit 0
# for digest bounces
</#d/>
|<#B#>/ezmlm-warn -d '<#D#>' || exit 0
</#d^4/>
|<#B#>/ezmlm-tstdig -m30 -k64 -t48 '<#D#>' || exit 99
</#d4/>
|<#B#>/ezmlm-tstdig <#4#> '<#D#>' || exit 99
</#d/>
|<#B#>/ezmlm-get '<#D#>' || exit 0
</bouncer/>
|<#B#>/ezmlm-weed
|<#B#>/ezmlm-return '<#D#>'
# moderator is set up only for message moderated lists. However, '-e' does
# not remove it since we can't remove the symlinks to it (they're outside
# of the list dir.
</moderator#m/>
|<#B#>/ezmlm-moderate '<#D#>'
</#mU/>
|<#B#>/ezmlm-clean '<#D#>' || exit 0
</#mu/>
|<#B#>/ezmlm-clean -R '<#D#>' || exit 0
</headerremove/>
return-path
return-receipt-to
content-length
</#x/>
reply-to
</lock/>
</lockbounce/>
</digest/lockbounce/>
</digest/lock/>
</public#p/>
</archived#a/>
</indexed#i/>
</inhost/>
<#H#>
</outhost/>
<#H#>
</outlocal/>
<#L#>
</mailinglist/>
contact <#L#>-help@<#H#>; run by ezmlm
# Headeradd needs to always exist
</headeradd/>
# Good for mailing list stuff (and vacation program)
Precedence: bulk
# Add the rest if -x:
</#x/>
Reply-To: <#L#>@<#H#>
# remove mime parts if -x
</mimeremove#x/>
application/excel
application/rtf
application/msword
application/ms-tnef
text/html
text/rtf
text/enriched
text/x-vcard
</prefix#f/>
[<#L#>]
</text/trailer#t/>
---------------------------------------------------------------------
To unsubscribe, e-mail: <#L#>-unsubscribe@<#H#>
For additional commands, e-mail: <#L#>-help@<#H#>
</text/bottom/>

--- Here are the ezmlm command addresses.

I can handle administrative requests automatically.
Just send an empty note to any of these addresses:

   <<#L#>-subscribe@<#H#>>:
   Receive future messages sent to the <#L#> mailing list.

   <<#L#>-unsubscribe@<#H#>>:
   Stop receiving messages for the <#L#> mailing list.

# ezmlm-make -i needed to add ezmlm-get line. If not, we can't do
# multi-get!
</text/bottom#ai/>
   <<#L#>-get.12_45@<#H#>>:
   Retrieve a copy of messages 12 to 45 from the archive.
   A maximum of 100 messages are returned per request.

</text/bottom#aI/>
   <<#L#>-get.12@<#H#>>:
   Retrieve a copy of message 12 from the archive.

</text/bottom#i/>
   <<#L#>-index.123_456@<#H#>>:
   Retrieve subjects of messages, including 123 though 456
   from the archive. Subjects are returned in sets of 100.
   A maximum of 2000 subjects are returned per request.

# Lists need to be both archived and indexed for -thread to work
</text/bottom#ai/>
   <<#L#>-thread.12345@<#H#>>:
   Retrieve a copy of all messages with the same subject
   as message 12345.

# The '#' in the tag below is optional, since no flags follow.
# The name is optional as well, since the file will always be open
# at this point.
</text/bottom#/>
DO NOT SEND ADMINISTRATIVE REQUESTS TO THE MAILING LIST!
If you do, I won't see them, and subscribers will yell at you.

To specify God@heaven.af.mil as your subscription address, send mail
to <<#L#>-subscribe-God=heaven.af.mil@<#H#>>.
I'll send a confirmation message to that address; when you receive that
message, simply reply to it to complete your subscription.

</text/bottom#x/>
If these instructions are too complicated or you do not get the
results you expect, please contact my owner at
<#L#>-owner@<#H#>. Please be patient, my owner is a
lot slower than I am ;-)
</text/bottom/>

--- Enclosed is a copy of the request I received.

</text/bounce-bottom/>

--- Enclosed is line is a copy of the bounce message I received.

</text/bounce-num/>

I've kept a list of which messages from the <#L#> mailing list have 
bounced from your address. Copies of these messages may be in the 
archive. To get message 12345 from the archive, send an empty note 
to <#L#>-get.12345@<#H#>.

</#ia/>
To get a subject and author list for the last 100 or so messages, send
an empty note to <#L#>-index@<#H#>.

To retrieve a set of messages 123-145 (a maximum of 10 per request),
send an empty note to <#L#>-get.123_145@<#H#>.

<//>
Here are the message numbers:

</text/dig-bounce-num/>

I've kept a list of which messages from the <#L#>-digest mailing list
have bounced from your address. For each digest you missed, I have
noted the number of the first message in the digest. You may be able
to get can get messages from the main list archive.

To get message 12345 from the archive, send an empty note 
to <#L#>-get.12345@<#H#>.

</#ia/>
To get a subject and author list for the last 100 or so messages, send
an empty note to <#L#>-index@<#H#>.

To retrieve a set of messages 123-145 (a maximum of 100 per request),
send an empty note to <#L#>-get.123_145@<#H#>.

<//>
Here are the digest message numbers:

</text/bounce-probe/>

Messages to you from the <#l#> mailing list seem to
have been bouncing. I sent you a warning message, but it bounced.
I've attached a copy of the bounce message.

This is a probe to check whether your address is reachable. If this
probe bounces, I will remove your address from the
<#l#>@<#H#> mailing list, without further notice.

</text/bounce-warn/>

Messages to you from the <#l#> mailing list seem to
have been bouncing. I've attached a copy of the first bounce
message I received.

If this message bounces too, I will send you a probe. If the probe bounces,
I will remove your address from the <#l#> mailing list,
without further notice.

</text/digest#ia/>
To subscribe to the digest, e-mail:
	<#L#>-digest-subscribe@<#H#>

To unsubscribe from the digest, e-mail:
	<#L#>-digest-unsubscribe@<#H#>

To post to the list, e-mail:
	<#L#>@<#H#>

</#iax/>
	<#L#> List Owner - <<#L#>-owner@<#H#>>

</text/get-bad/>
Sorry, that message is not in the archive.

</text/help/>
This is a generic help message. The message I received wasn't sent to
any of my command addresses.

</text/mod-help/>
Thank you for agreeing to moderate the <#L#>@<#H#>
mailing list.

My commands are a little different from many other mailing lists.
They may at first seem unusual, but as you get used to them,
you will appreciate the simplicity of the system and the speed
with which I deal with your requests.

Here are some notes about how moderation works:

Remote subscription
-------------------
As a moderator, you can subscribe and unsubscribe
john@johnhost.domain by sending mail to:

<#L#>-subscribe-john=johnhost.johndomain@<#H#>
<#L#>-unsubscribe-john=johnhost.johndomain@<#H#>

</#g/>
For the digest list:

<#L#>-digest-subscribe-john=johnhost.johndomain@<#H#>
<#L#>-digest-unsubscribe-john=johnhost.johndomain@<#H#>

<//>
That's all. No subject and no message body needed!

</#r/>
I will send you a confirmation request, to make sure
that you really sent the request. Simply reply to the
message, and the transaction is complete.
</#R/>
I will send a confirmation request to the user address.
All the user has to do is to reply to the message.
<//>

I will notify the user when his/her subscriber status
has changed.

Subscription
------------

Any user can subscribe or unsubscribe by sending mail to:

<#L#>-subscribe@<#H#>
<#L#>-unsubscribe@<#H#>

</#g/>
For the digest list:

<#L#>-digest-subscribe@<#H#>
<#L#>-digest-unsubscribe@<#H#>

The user will receive a confirmation request to make
sure s/he controls the subscription address. Once this
is verified the user is unsubscribed.

</#s/>
For subscriptions,
a second confirmation request is sent to the moderator(s).
A simple reply from the moderator will complete the transaction.
</#S/>
Subscriptions work the same way.
<//>

The user can also use:

<#L#>-subscribe-john=johnhost.johndomain@<#H#>
<#L#>-unsubscribe-john=johnhost.johndomain@<#H#>

to have mail sent to another address s/he controls.
Only if s/he receives mail at john@johnhost.johndomain
will s/he be able to reply to the confirmation request.

All this ensures that there are no fake subscriptions
and that you as a moderator can be confident that the
subscriber address is real.

Your address and identity will not be revealed to the subscriber.

</#m/>
Moderated posts
---------------
When posts are moderated, I will put posted messages into
a queue, and then send a moderation request to the moderator(s).

Just reply to the 'Reply-To:' address (this should be automatic)
if you want to accept the post.

If you want to reject it, send mail to the 'From:' address
(can usually be done be 'reply-to-all' and then deleting
your address and the accept address). You can add an
optional comment to the sender between two lines
starting with three '%'.

I will process the message according to the first reply I receive.
If you send me a request to accept a message that has already been
rejected or vice versa, I will let you know.

If I receive no moderator replies within a certain period of
time (normally 5 days), I will return the message to the sender
with an explanation of what happened.
<//>

Vacations
---------
If you are temporarily at a different address, just forward all messages
that have the correct 'Mailing-List:' header (or all that have subjects
starting with 'MODERATE for <#L#>@<#H#>'
or 'CONFIRM subscribe to <#L#>@<#H#>') to the
new address. You can then moderate from the new address. Alternatively,
you can forward the messages to a friend so that s/he can moderate
for you. Please OK this with the list owner first.

If you would like to automatically approve all requests while you
are gone, set up you mail client to auto-reply to messages that
have subjects meeting the above criteria.

</#r/>
If you try to do remote administration from an address that is not
your own, the subscriber, not you, will be asked to confirm. After
that, a moderator confirm request is sent to all moderators.
I'm doing this because I have no way of knowing that it is you that
sent the original request.

Please note that your original request (and your address) are sent to
the subscriber in this case!
<//>

Good luck!

PS: Please contact the list owner (<#L#>-owner@<#H#>) if you
have any questions or problems.

</text/mod-reject/>
I'm sorry, your message (enclosed) was not accepted by the moderator.
If the moderator has made any comments, they are shown below.
</text/mod-request/>
Please decide if you as moderator approve the enclosed message
for distribution to the <#L#> mailing list.

To approve the message and cause it to be immediately sent
to all list subscribers, please send a message to:

# This does the default !A for normal setups, but puts in a 'mailto:address'
# for lists created with the -x switch.
</#X/>
!A
</#x/>
mailto:<#A#>
# Below is a minimalist tag. It just means that succeeding lines should be
# added to the currently open file in all cases.
<//>

To reject the post and cause it to be returned to the
sender, please send a message to:

</#X/>
!R
</#x/>
mailto:<#R#>
<//>

You do not need to copy the post in your response to accept or 
reject it. If you wish to send a comment to the sender of a rejected
post, please include it between two marker lines starting with three
percent signs ('%').

%%% Start comment
%%% End comment

Thank you for your help!

--- Enclosed, please find the posted message.

</text/mod-sub/>
--- I have subscribed or unsubscribed you at the request of
a moderator of the <#l#>@<#H#> mailing list.

If this is not an action you desire, please send a complaint 
or other comments to the list owner (<#l#>-owner@<#H#>) as soon 
as possible.

If you would like some information on how to access the archive
of the <#L#> mailing list, just send an empty
message to <#L#>-help@<#H#>.

</text/mod-timeout/>
I'm sorry, the list moderators have failed to act on your post.
Thus, I'm returning it to you. If you feel that this is in error,
please repost the message or contact a list moderator directly.

--- Enclosed, please find the message you sent.

</text/mod-sub-confirm/>
I respectfully request your permission to add

<#A#>

to the subscribers of the <#l#> mailing list. Unless
this request came from you (the request is included at
the end of this message), I have already confirmed that
<#A#> really would like to be a subscriber.

To confirm, please send an empty reply to this address:

</#X/>
!R
</#x/>
mailto:<#R#>
<//>

Your mailer should have a Reply feature that uses this address automatically.

If you don't approve, simply ignore this message.

Thank you for your help!

</text/mod-unsub-confirm/>
I respectfully request your permission to remove

!A

from the <#l#> mailing list. If you agree, please send
an empty reply to this address:

</#X/>
!R
</#x/>
mailto:<#R#>
<//>

Your mailer should have a Reply feature that uses this address automatically.

Thank you for your help!

</text/sub-bad/>
Oops, that confirmation number appears to be invalid.

The most common reason for invalid numbers is expiration. I have to
receive confirmation of each request within ten days. Also, make sure
the entire confirmation number was in the reply you sent me. Some 
e-mail programs have a habit of cutting off some of the reply address,
which can be quite long.

I've set up a new confirmation number. To confirm that you would like

!A

added to the <#l#> mailing list, please send an empty reply to this address:

</#X/>
!R
</#x/>
mailto:<#R#>
<//>

Again, check the reply address carefully to make sure it is all included 
before you confirm your subscription.

Sorry for the trouble.
</#x/>
	<#L#>-Owner <<#l#>-owner@<#H#>>
<//>

</text/sub-confirm/>
To confirm that you would like

!A

added to the <#l#> mailing list, please send an empty reply to this address:

</#X/>
!R
</#x/>
mailto:<#R#>
<//>

Your mailer should have a Reply feature that uses this address automatically.

This confirmation serves two purposes. First, it verifies that I am able
to get mail through to you. Second, it protects you in case someone
forges a subscription request in your name.

</text/sub-confirm#s/>
This list is moderated. Once you have sent this confirmation, the
request will be sent to the moderator(s) of this list. I will notify
you when your subscription has been activated.

</text/sub-nop/>
Acknowledgment: The address

!A

is on the <#l#> mailing list. This address was
already a subscriber before your request was received.

</text/sub-ok/>
Acknowledgment: I have added the address

!A

to the <#l#> mailing list.

Welcome to <#l#>@<#H#>!

Please save this message so that you know the address you are
subscribed under, in case you later want to unsubscribe or change your
subscription address.

</text/top/>
Hi! This is the ezmlm program. I'm managing the
<#l#>@<#H#> mailing list.

</#x/>
I'm working for my owner, who can be reached
at <#l#>-owner@<#H#>.

</text/unsub-bad/>
Oops, that confirmation number appears to be invalid.

The most common reason for invalid numbers is expiration. I have to
receive confirmation of each request within ten days. Also, make sure
the entire confirmation number was in the reply you sent me. Some 
e-mail programs have a habit of cutting off some of the reply address,
which can be quite long.

I've set up a new confirmation number. To confirm that you would like

!A

removed from the <#l#> mailing list, please send an empty reply 
to this address:

</#X/>
!R
</#x/>
mailto:<#R#>
<//>

Again, check the reply address carefully to make sure it is all included 
before you confirm this action.

Sorry for the trouble.

	<#l#>-Owner <<#l#>-owner@<#H#>>

</text/unsub-confirm/>
To confirm that you would like

!A

removed from the <#l#> mailing list, please send an empty reply 
to this address:

</#X/>
!R
</#x/>
mailto:<#R#>
<//>

Your mailer should have a Reply feature that uses this address automatically.

I haven't checked whether your address is currently on the mailing list.
To see what address you used to subscribe, look at the messages you are
receiving from the mailing list. Each message has your address hidden
inside its return path; for example, God@heaven.af.mil receives messages
with return path: <<#l#>-return-<number>-God=heaven.af.mil@<#H#>.

</text/unsub-nop/>
Acknowledgment: The address

!A

is not on the <#l#> mailing list. It was not there when
your request was received.

If you unsubscribe, but continue to receive mail, you're subscribed
under a different address than you currently use. Please look at the
header for:

'Return-Path: <<#l#>-return-1234-user=host.dom@<#H#>>'

The unsubscribe address for this user would be:
'<#l#>-unsubscribe-user=host.dom@<#H#>'.
Just mail to that address, substituting user=host.dom for the real
values, reply to the confirmation request, and you should receive a message
that you're off the list.

If this still doesn't work, I'm sorry to say that I can't help you.
Please FORWARD a list message together with a note about what you're
trying to achieve to my owner:

</#x/>
mailto:<#L#>-owner@<#H#>
</#X/>
    <#l#>-owner@<#H#>
<//>

who will take care of it. My owner is a little bit slower than I am, 
so please be patient.

</text/unsub-ok/>
Acknowledgment: I have removed the address

!A

from the <#l#> mailing list. This address
is no longer a subscriber

</text/edit-do#n/>
Please edit the following text file and send it to this address:

!R

Your mailer should have a Reply feature that uses this address automatically.

I can remove the quote marks that your mailer adds to the text,
as long as you do not edit the marker lines themselves.

The marker lines are the lines starting with '%%%'. They must not
be modified (extra characters added by your mailer at the beginning
of the line are acceptable).


</text/edit-list#d/>
The <#L#>-edit.file command can be used by a remote
administrator to edit the text files than make up the bulk
of the responses from the <#L#>@<#H#> list.

What follows is a list of the response file name and a short
description of when their contents are used.  To edit a file,
simply send mail to <#L#>-edit.file, substituting the file name
for 'file'. Editing instructions are mailed with the text file.

File                Use

bottom              bottom of all responses. General command info.
digest              'administrivia' section of digests.
get_bad             in place of messages not found in the archive.
help                general help (between 'top' and 'bottom').
mod_help            specific help for list moderators.
mod_reject          to sender of rejected post.
mod_request         to message moderators together with post.
mod_sub             to subscriber after moderator confirmed subscribe.
mod_sub_confirm     to subscription mod to request subscribe confirm.
mod_timeout         to sender of timed-out post.
mod_unsub_confirm   to remote admin to request unsubscribe confirm.
sub_bad             to subscriber if confirm was bad.
sub_confirm         to subscriber to request subscribe confirm.
sub_nop             to subscriber after re-subscription.
sub_ok              to subscriber after successful subscription.
</#td/>
trailer             added to all posts sent out from the list.
</#d/>
unsub_bad           to subscriber if unsubscribe confirm was bad.
unsub_confirm       to subscriber to request unsubscbribe confirm.
unsub_nop           to non-subscriber after unsubscribe.
unsub_ok            to ex-subscriber after successful unsubscribe.

</text/edit-done#d/>
The text file was successfully updated.

