head	1.3;
access;
symbols
	NEWHELM:1.1.1.1
	TIGRIS_NOV_12_2000:1.1.1
	OLDHELM:1.1.0.4
	TIGRIS_NOV_11_2000:1.1
	TIGRIS_SEP_13_2000:1.1.0.2
	TIGRIS_BASELINE:1.1;
locks; strict;
comment	@# @;


1.3
date	2000.11.22.22.00.15;	author edk;	state dead;
branches;
next	1.2;

1.2
date	2000.11.12.22.57.30;	author dlr;	state Exp;
branches;
next	1.1;

1.1
date	2000.07.11.21.31.23;	author dlr;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	2000.11.12.21.14.25;	author dlr;	state Exp;
branches;
next	;


desc
@@


1.3
log
@these files are now part of anzu ...
@
text
@#$Id: ezmlmrc,v 1.2 2000/11/12 22:57:30 dlr Exp $
#Name:$
#
# ezmlmrc 
# #######
# Controls the actions of ezmlm-make as patched with ezmlm-idx-0.31 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 -c 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.
# -6 for sql connection info
# -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:
# - Removal of many non-text MIME parts from messages.
# - Limit posts to 2 bytes <= msg body size <= 40000
#
# 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 without 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#d/>
</+digest/subscribers#d/>
</+digest/bounce#d/>
# for extra address db
</+allow/>
</+allow/subscribers/>
# for blacklist
</+deny#k/>
</+deny/subscribers#k/>
# moderator db & mod queue dirs. Needed for -m, -r -s, so we just
# make them by default.
</+mod/>
</+mod/subscribers/>
</+mod/pending/>
</+mod/accepted/>
</+mod/rejected/>
# links: dot -> dir/editor
</:/editor/>
</:-owner/owner/>
</:-digest-owner/owner#d/>
</:-return-default/bouncer/>
</:-digest-return-default/digest/bouncer#d/>
</:-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/>
# Not needed, except for message moderation.
</-moderator#eM/>
# We don't clean out text files to make it easier for users
# doing manual config by e.g. touching dir/remote.
# 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
</#W/>
|<#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#W/>
|<#B#>/ezmlm-warn '<#D#>' || exit 0
</#dW/>
|<#B#>/ezmlm-warn -d '<#D#>' || exit 0
</editor/>
# reject shouldn't be configured for sublist.
</#^0/>
# full reject is now default, to get To/Cc: listaddress requirement
|<#B#>/ezmlm-reject -T '<#D#>'
# -k => reject posts from blacklisted addresses. Done for moderated
# lists as well - allows removal of unwanted noise.
</#k^0/>
|<#B#>/ezmlm-issubn -n '<#D#>/deny' || { echo "Sorry, I've been told to reject your posts. Contact <#L#>-owner@@<#H#> if you have questions about this (#5.7.2)"; 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#>/allow' '<#D#>/mod' || { 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 (#5.7.2)"; exit 100 ; }
</#um/>
|<#B#>/ezmlm-gate '<#D#>' '<#D#>' '<#D#>/digest' '<#D#>/allow' '<#D#>/mod'
# 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 unless -w.
</#W/>
|<#B#>/ezmlm-warn '<#D#>' || exit 0
# for digest bounces
</#dW/>
|<#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 is complicated. We use ezmlm-receipt if -6 AND -w, but ezmlm-return
# if (-6 and -W) OR (not -6 and -w). Since there is no or, we need 2 lines.
</bouncer/>
|<#B#>/ezmlm-weed
</#^6/>
|<#B#>/ezmlm-return -D '<#D#>'
</#6W/>
|<#B#>/ezmlm-return -D '<#D#>'
</#6w/>
|<#B#>/ezmlm-receipt -D '<#D#>'
</digest/bouncer#d/>
|<#B#>/ezmlm-weed
</#^6d/>
|<#B#>/ezmlm-return -d '<#D#>'
</#6Wd/>
|<#B#>/ezmlm-return -d '<#D#>'
</#6wd/>
|<#B#>/ezmlm-receipt -d '<#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#E/>
return-path
return-receipt-to
content-length
precedence
x-confirm-reading-to
x-pmrqc
# Only one allowed
list-help
list-unsubscribe
list-post
</lock/>
</lockbounce/>
</digest/lockbounce#d/>
</digest/lock#d/>
</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#E/>
# Good for mailing list stuff (and vacation program)
Precedence: bulk
# To prevent indexing by findmail.com
X-No-Archive: yes
# rfc2369
list-help: <mailto:<#l#>-help@@<#h#>>
list-unsubscribe: <mailto:<#l#>-unsubscribe@@<#h#>>
list-post: <mailto:<#L#>@@<#H#>>
Reply-To: <#l#>@@<#h#>
# max & min message size
</msgsize#x/>
40000:2
# 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
application/activemessage
application/andrew-inset
application/applefile
application/atomicmail
application/dca-rft
application/dec-dx
application/mac-binhex40
application/mac-compactpro
application/macwriteii
application/news-message-id
application/news-transmission
application/octet-stream
application/oda
application/pdf
application/postscript
application/powerpoint
application/remote-printing
application/slate
application/wita
application/wordperfect5.1
application/x-bcpio
application/x-cdlink
application/x-compress
application/x-cpio
application/x-csh
application/x-director
application/x-dvi
application/x-hdf
application/x-httpd-cgi
application/x-koan
application/x-latex
application/x-mif
application/x-netcdf
application/x-stuffit
application/x-sv4cpio
application/x-sv4crc
application/x-tar
application/x-tcl
application/x-tex
application/x-texinfo
application/x-troff
application/x-troff-man
application/x-troff-me
application/x-troff-ms
application/x-ustar
application/x-wais-source
audio/basic
audio/mpeg
audio/x-aiff
audio/x-pn-realaudio
audio/x-pn-realaudio
audio/x-pn-realaudio-plugin
audio/x-realaudio
audio/x-wav
image/gif
image/ief
image/jpeg
image/png
image/tiff
image/x-cmu-raster
image/x-portable-anymap
image/x-portable-bitmap
image/x-portable-graymap
image/x-portable-pixmap
image/x-rgb
image/x-xbitmap
image/x-xpixmap
image/x-xwindowdump
text/x-sgml
video/mpeg
video/quicktime
video/x-msvideo
video/x-sgi-movie
x-conference/x-cooltalk
x-world/x-vrml
# These can also be excluded, but for many lists it is desirable
# to allow them. Uncomment to add to mimeremove.
# application/zip
# application/x-gtar
# application/x-gzip
# application/x-sh
# application/x-shar
# chemical/x-pdb
# --------------------- Handle SQL connect info
</-sql#^6e/>
</-digest/sql#^6e/>
</-allow/sql#^6e/>
</sql#6W/>
<#6#>
</sql#6w/>
<#6#>:<#L#>@@<#H#>
</digest/sql#6dW/>
<#6#>_digest
</digest/sql#6dw/>
<#6#>_digest:<#L#>_digest@@<#H#>
</allow/sql#6/>
<#6#>_allow
# -------------------- End sql stuff
</prefix#f/>
[<#L#>]
</text/trailer#t/>
---------------------------------------------------------------------
To unsubscribe, e-mail: <#L#>-unsubscribe@@<#H#>
For additional commands, e-mail: <#L#>-help@@<#H#>
</text/bottom/>

--- Administrative commands for the <#l#> list ---

I can handle administrative requests automatically. Please
do not send them to the list address! Instead, send
your message to the correct command address:

To subscribe to the list, send a message to:
   <<#L#>-subscribe@@<#H#>>

To remove your address from the list, send a message to:
   <<#L#>-unsubscribe@@<#H#>>

Send mail to the following for info and FAQ for this list:
   <<#L#>-info@@<#H#>>
   <<#L#>-faq@@<#H#>>

</#d/>
Similar addresses exist for the digest list:
   <<#L#>-digest-subscribe@@<#H#>>
   <<#L#>-digest-unsubscribe@@<#H#>>

# ezmlm-make -i needed to add ezmlm-get line. If not, we can't do
# multi-get!
</text/bottom#ai/>
To get messages 123 through 145 (a maximum of 100 per request), mail:
   <<#L#>-get.123_145@@<#H#>>

</text/bottom#aI/>
To get message 12 from the archive, send a message to:
   <<#L#>-get.12@@<#H#>>

</text/bottom#i/>
To get an index with subject and author for messages 123-456 , mail:
   <<#L#>-index.123_456@@<#H#>>

They are always returned as sets of 100, max 2000 per request,
so you'll actually get 100-499.

# Lists need to be both archived and indexed for -thread to work
</text/bottom#ai/>
To receive all messages with the same subject as message 12345,
send an empty message to:
   <<#L#>-thread.12345@@<#H#>>

# 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#/>
The messages do not really need to be empty, but I will ignore
their content. Only the ADDRESS you send to is important.

You can start a subscription for an alternate address,
for example "john@@host.domain", just add a hyphen and your
address (with '=' instead of '@@') after the command word:
<<#L#>-subscribe-john=host.domain@@<#H#>>

To stop subscription for this address, mail:
<<#L#>-unsubscribe-john=host.domain@@<#H#>>

In both cases, I'll send a confirmation message to that address. When
you receive it, simply reply to it to complete your subscription.

</text/bottom/>
If despite following these instructions, you do not get the
desired results, 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 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.

</#a/>
Copies of these messages may be in the archive.
</#aI/>
To get message 12345 from the archive, send an empty message to:
   <<#L#>-get.12345@@<#H#>>

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

To receive a subject and author list for the last 100 or so messages,
send an empty message to:
   <<#L#>-index@@<#H#>>

<//>
Here are the message numbers:

</text/dig-bounce-num/>

I've kept a list of which digests 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. I do not archive
the digests themselves, but you may be able to get the messages
from the main list archive.

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

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

To receive a subject and author list for the last 100 or so messages,
send an empty message to:
   <<#L#>-index@@<#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. You can re-subscribe
by sending an empty message to the following address:
   <<#l#>-subscribe@@<#H#>>

</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#d/>
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#>

</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 other mailing lists,
but I think you will find them intuitive and easy to use.

Here are some instructions for the tasks you may have to perform
as a list-owner and/or moderator.

Remote subscription
-------------------
As a moderator, you can subscribe and unsubscribe any address to
the mailing list. To subscribe "john@@host.domain", simply put
a hyphen after the command word, then his address with '=' instead
of the '@@'. For instance, to subscribe that address, send mail to:
   <<#L#>-subscribe-john=host.domain@@<#H#>>

You can similarly remove the address by sending a message to:
   <<#L#>-unsubscribe-john=host.domain@@<#H#>>

</#d/>
For the digest list:
   <<#L#>-digest-subscribe-john=host.domain@@<#H#>>
   <<#L#>-digest-unsubscribe-john=host.domain@@<#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 your wish has been granted.
</#R/>
I will send a confirmation request to the user address, in this
case <john@@host.domain>. All the user has to do is to reply to 
this confirmation request message.
<//>

The confirmations are necessary to make it extremely hard
for a third party to add or remove an address to the list.

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#>

</#d/>
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/>
Since this list is moderated for subscriptions, I will send a
second confirmation request to the moderator(s). Since the user
has already confirmed the desire to be on the list, you as the
moderator can be highly confident that the subscriber address is
real. If you want to approve the users request, simply reply to
my CONFIRM message. If not, you can simply delete my message or
possibly contact the potential subscriber for more information.
</#S/>
Subscriptions work the same way.
<//>

The user can also use:

   <<#L#>-subscribe-mary=host.domain@@<#H#>>
   <<#L#>-unsubscribe-mary=host.domain@@<#H#>>

to have mail sent to "mary@@host.domain". Only if she receives mail
at this address will she receive the confirmation request and be
able to reply to it.

Your address and identity will not be revealed to the subscriber,
unless you send mail directly to the user.

</#rl/>
To get a subscriber list for <#L#>@@<#H#>, send a message to:
   <<#L#>-list@@<#H#>>

To get a list transaction log <#L#>@@<#H#>, send a message to:
   <<#L#>-log@@<#H#>>

</#rld/>
For digest subscribers:
   <<#L#>-digest-list@@<#H#>>
and:
   <<#L#>-digest-log@@<#H#>>

</#rn/>
You can remotely edit the text files that make up the responses the
list sends out. To get a list of files and editing instructions, mail:
   <<#L#>-edit@@<#H#>>

</#m/>
Moderated posts
---------------
When posts are moderated, I will save the posted message and send
you a copy together with instructions. The message to you will
have "MODERATE for ..." as the subject.

To accept the post, just reply to the 'Reply-To:', which I have
configured with the correct "accept" address address. You do not need
to include the post itself. In fact, I will ignore anything you send
me as long as the address you send to is correct.

If you want to reject it, send mail to the 'From:' address, which
I have configured with the correct "reject" address. This can
usually be done by 'reply-to-all', then deleting any address other
than the "reject" address. You may add a comment to the sender between
two lines starting with three '%'. I will send only this comment to the
sender with the rejected post. Again, I will not reveal your identity.

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. You administrator can also
set up the list so that such "ignored" messages are simply deleted
without notification, rather than returned to sender.
<//>

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/>
The enclosed message was submitted to the <#L#>@@<#H#>
mailing list. If you'd like to approve it for distribution to all
the subscribers, please e-mail:

!A

Usually, this happens when you just hit the "reply" button. You can
check the address to make sure that it starts with
"<#L#>-accept". If this does not work, simply copy the
address and paste it into the "To:" field of a new message.
</#x/>

Alternatively, click here:
	mailto:<#A#>
<//>

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

!R

Usually, it is easiest to hit the "reply-to-all" button, and then
remove all the addresses except the one starting with
"<#L#>-reject".
</#x/>

Alternatively, click here:
	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#E/>
--- 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 more information on how to interact with the
<#L#> mailing list, just send an empty message
to <#L#>-help@@<#H#>.

</text/mod-timeout/>
I'm sorry, the list moderators for the <#L#> list
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. This request
either came from you, or it has already been verified by
the potential subscriber.

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

!R

Usually, this happens when you just hit the "reply" button.
If this does not work, simply copy the address and paste it into
the "To:" field of a new message.
</#x/>

or click here:
	mailto:<#R#>
<//>

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

Thank you for your help!

</text/mod-unsub-confirm/>
A request has been made to remove

!A

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

!R

Usually, this happens when you just hit the "reply" button.
If this does not work, simply copy the address and paste it into
the "To:" field of a new message.
</#x/>

or click here:
	mailto:<#R#>
<//>

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

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:

!R
</#x/>

or click here:
	mailto:<#R#>
<//>

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

Sorry for the trouble.

	<#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:

!R

Usually, this happens when you just hit the "reply" button.
If this does not work, simply copy the address and paste it into
the "To:" field of a new message.
</#x/>

or click here:
	mailto:<#R#>
<//>

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.

</#q/>
Some mail programs are broken and cannot handle long addresses. If you
cannot reply to this request, instead send a message to
<<#L#>-request@@<#H#>> and put the
entire address listed above into the "Subject:" line.

</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

was already on the <#l#> mailing list when I received
your request, and remains a subscriber.

</text/sub-ok#E/>
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:

!R
</#x/>

or click here:
	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:

!R

Usually, this happens when you just hit the "reply" button.
If this does not work, simply copy the address and paste it into
the "To:" field of a new message.
</#x/>

or click here:
	mailto:<#R#>
<//>

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, mary@@xdd.ff.com receives messages
with return path: <<#l#>-return-<number>-mary=xdd.ff.com@@<#H#>.

</#q/>
Some mail programs are broken and cannot handle long addresses. If you
cannot reply to this request, instead send a message to
<<#L#>-request@@<#H#>> and put the entire address listed above
into the "Subject:" line.

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

!A

was not on the <#l#> mailing list when I received
your request and is not a subscriber of this list.

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.

For some mail programs, you need to make the headers visible to
see the return path:

For Eudora 4.0, click on the "Blah blah ..." button.
For PMMail, click on "Window->Show entire message/header". 

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 and a list of addresses that you might be subscribed
under to my owner:

    <#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#n/>
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.
faq                 frequently asked questions specific to this list.
get_bad             in place of messages not found in the archive.
help                general help (between 'top' and 'bottom').
info                list info. First line should be meaningful on its own.
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.
top                 top of all responses.
</#tn/>
trailer             added to all posts sent out from the list.
</#n/>
unsub_bad           to subscriber if unsubscribe confirm was bad.
unsub_confirm       to subscriber to request unsubscribe confirm.
unsub_nop           to non-subscriber after unsubscribe.
unsub_ok            to ex-subscriber after successful unsubscribe.

</text/edit-done#n/>
The text file was successfully updated.
</text/info#E/>
No information has been provided for this list.
</text/faq#E/>
FAQ - Frequently asked questions of the <#l#>@@<#H#> list.

None available yet.

@


1.2
log
@Resolved merge conflicts.
@
text
@d1 1
a1 1
#$Id: ezmlmrc,v 1.1.1.1 2000/11/12 21:14:25 dlr Exp $
@


1.1
log
@Moved here from sandbox/tigrisq.
@
text
@d1 1
a1 1
#$Id: ezmlmrc,v 1.1 2000/05/01 21:33:57 jrobbins Exp $
@


1.1.1.1
log
@Merging newhelm tree into helm, as per IZ issue #557.  Previous major version of helm is tagged TIGRIS_NOV_11_2000.
@
text
@d1 1
a1 1
#$Id: ezmlmrc,v 1.1 2000/10/05 20:05:39 jrobbins Exp $
@

