The Best of Windows 95.com 1996 September/WIN95_09961.iso/mailsrv/LSV95.ZIP/win95.z/default.mailtpl

Text File | 1995-12-31 | 21KB | 463 lines

>>> INFO Information about the &LISTNAME list
There is no information file for the &LISTNAME list. Here is a copy of
the list "header", which usually contains a short description of the
purpose of the list, although its main purpose is to define various
list configuration options, also called
"keywords". If you have any question about the &LISTNAME list, write to
the list owners at the generic address:

.ce &OWNER

.dd &LISTHDR
>>> MOVE1 Change in your host server for the &LISTNAME list
.re owners
&WEEKDAY, &DATE &TIME

Your host server for the &LISTNAME list (&TITLE) has just been changed
from &LISTADDR to &NEWADDR by &MBX(&INVOKER).
You must now send mail to
&NEWADDR and direct administrative requests to the corresponding server.
>>> SIGNOFF1 &LISTNAME: &WHOM left the list
&WEEKDAY, &DATE &TIME

&MBX(&WHOM) has just signed off the &LISTNAME list (&TITLE).
>>> SIGNOFF2 Your request to sign off the &LISTNAME list
.re owners
&WEEKDAY, &DATE &TIME

No entry for your &WHOM address could be found in the &LISTNAME list
at &MYHOST. Here are a number of possible reasons why you might still
be getting mail from the list:

1. You could be subscribed under a different, but equivalent address. For
instance, if your e-mail address as it appears in the 'From:' line of
messages coming from you has the misfortune of depending on the distance
between your workstation and the terminal room door, you were probably
subscribed from a different address and, while your mail system knows
that the two addresses are equivalent, LISTSERV has no way to know that.
In this case the only thing you can do, beyond contacting the list owner,
is to send a "REVIEW &LISTNAME" command to find out under what address
you are subscribed, and try to duplicate it with the help of your user
support people.

2. If you are a BITNET user, you might be subscribed under your Internet
address and sending this command via BITNET, or vice versa. Most BITNET
sites have registered their Internet addresses in the BITNET nodes
database, BITEARN NODES (the "tag" containing this information is called
':internet' - if you do not understand any of this, just bring a copy
of this message to your user support people). Unfortunately, some sites
have still not done that, and in such cases LISTSERV has no way to
determine that, for instance, BITNET node XYZCOL1 is the same as
Internet host VM3.XYZ.EDU. If you suspect this might be your problem,
try resending your request via both interactive message (SEND under VMS,
TELL under VM) and e-mail.

3. You might be subscribed under an equivalent yet different address -
for instance, one with explicit gatewaying, or an X.400 address with
different ordering of the various components, etc. You could send a
"REVIEW &LISTNAME"
command and inspect the list membership to find out whether this
is the case, and ask the list owners to remove that address from
the list.

4. You could be subscribed to the list under another account, from which
mail
is being automatically forwarded to your &WHOM account. In that case you
should be able to leave the list by resending the signoff request from
the account in question.

5. You could be subscribed to the list indirectly, via a "redistribution"
list. That is, one of the subscribers to the LISTSERV list is in fact a
mailing list, to which you are yourself subscribed (note that this
"sub-list" is not necessarily managed by LISTSERV and, in fact, such
lists are often manually maintained, in which case the only way to leave
the list is to contact the person who maintains it). Since you are not
directly subscribed to &LISTNAME, the only way for you to stop getting
the postings is to contact the administrator of this sub-list and ask
him to sign you off.

You should be able to contact the list owners by simply replying to this
message (if you do not know how to reply to a message in your mailbox,
you can send a new message to '&OWNER' instead).
>>> DELETE1 Your removal from the &LISTNAME list
.re owners
&WEEKDAY, &DATE &TIME

You have been removed from the &LISTNAME list (&TITLE) by &MBX(&WHOM).
>>> AUTODEL1 Your removal from the &LISTNAME list
.re owners
&WEEKDAY, &DATE &TIME

You have been automatically removed from the &LISTNAME list (&TITLE) as a
result of repeated delivery error reports from your mail system. This
decision was based on the automatic error monitoring policy in effect for
the list, and has not been reviewed or otherwise confirmed by a human
being. If you receive this message, it means that something is wrong:
while you are obviously able to receive mail, your mail system has been
regularly reporting that your account did not exist, or that you were
otherwise permanently unable to receive mail. Here is some information
which may assist you or your local help desk in determining the cause of
the problem:

- The failing address is &ADDR.

- The first error was reported on &DATE1.

- Since then, a total of &ERR delivery errors have been received.

- The last reported error was: &MSG

PLEASE DO NOT IGNORE THIS MESSAGE. While you can of course re-subscribe
to the list, it is important for you to report this problem to your
mail administrator so that it can be solved. This problem is not specific
to the &LISTNAME list, and also affects your private mail. This means
that YOU HAVE PROBABLY LOST SOME PRIVATE MAIL AS WELL. Anyone trying to
write to you during the same time frame will probably have received the
same errors for the same reason. The &LISTNAME list is but one of the
many people who may have tried to write to you while your mail system
was malfunctioning.

DO NOT LET TECHNICAL PEOPLE CONVINCE YOU THAT THIS IS NORMAL. It is never
normal for a mail system to claim that a valid, working account does not
exist, just as it would not be normal for the post office to return some
of your mail with "addressee unknown" when the address was written
correctly. It is true that some mail systems are less reliable than
others, and your technical people may be doing the best they can with the
tools they have. But, ultimately, the level of service that you are
receiving is the result of a business decision, and not something due
to a universal technical limitation that one can only accept. Reliable
mail systems do exist, and it is ultimately up to you to decide whether
this level of service is acceptable or not.
>>> ADD1 You have been added to the &LISTNAME list
.re owners
&WEEKDAY, &DATE &TIME

You have been added to the &LISTNAME mailing list (&TITLE) by
&MBX(&INVOKER).

.im $SIGNUP
>>> ADD2 &LISTNAME: &WHOM joined the list
&WEEKDAY, &DATE &TIME

&MBX(&WHOM) has just subscribed to the &LISTNAME list (&TITLE).
>>> ADDREQ1 &LISTNAME: &WHOM requested to join
&WEEKDAY, &DATE &TIME

A request for subscription to the &LISTNAME list (&TITLE) has been
received from &MBX(&WHOM).

You can, at your discretion, send the following command to &MYNAMES to
add this person to the list:

.ce ADD &LISTNAME &WHOM &USERNAME

PS: In order to facilitate the task, this message has been specially
formatted so that you only need to forward it back to &MYNAMES and fill
in the password to have the command executed. Note that while the formats
produced by the forwarding function of most mail packages are supported,
replying will seldom work, so make sure to forward and not reply.
.fo off
-------------------------------------------------------------------------
// JOB PW=XXXXXXXX
ADD &LISTNAME &WHOM &USERNAME
// EOJ
>>> SETINFO Change in your subscription options for the &LISTNAME list
.re owners
&WEEKDAY, &DATE &TIME

&MBX(&INVOKER) has just altered your subscription options for the
&LISTNAME list as per the "&CMD" command.
For more information about subscription options, send a "QUERY &LISTNAME"
command to &MYNAMES.
>>> ADDMOD2 Change in your name registration for the &LISTNAME list
.re owners
&WEEKDAY, &DATE &TIME

&MBX(&INVOKER)
has just changed your name as it appears in the &LISTNAME list from
"&OLDNAME" to "&NEWNAME". If this is not correct, just issue a
"SUBSCRIBE &LISTNAME" command with the correct name - as though you were
not on the list and wanted to subscribe to it.
>>> ADDPW1 Your new password for &MYSELF
.re postmasters
&WEEKDAY, &DATE &TIME

&MBX(&INVOKER) has assigned a password of "&PW" to you for use with
&MYNAMES. You will need this password for the
Automatic File Distribution commands. Send an "INFO AFD" command to
&MYNAMES for more details on these commands.
>>> ADDPW2 Addition of a LISTSERV password for &WHOM
&WEEKDAY, &DATE &TIME

&MBX(&WHOM) has just been assigned a LISTSERV password for &MYSELF.
>>> ADDPW3 Request for addition of a LISTSERV password
&WEEKDAY, &DATE &TIME

&MBX(&WHOM)
has requested that a LISTSERV password of "&PW" be assigned to him
for use with &MYSELF. You can, at your discretion, issue the following
command to confirm this request:

.ce PWC ADD &WHOM &PW PW=createpw

PS: In order to facilitate the task, this message has been specially
formatted so that you only need to forward it back to &MYNAMES and fill
in the password to have the command executed. Note that while the formats
produced by the forwarding function of most mail packages are supported,
replying will seldom work, so make sure to forward and not reply.
.fo off
-------------------------------------------------------------------------
// JOB PW=XXXXXXXX
PWC ADD &WHOM &PW
// EOJ
>>> DELPW Removal of your password for &MYSELF
.re postmasters
&WEEKDAY, &DATE &TIME

&MBX(&INVOKER) has just removed your LISTSERV password for &MYSELF.
>>> RENEW1 Renewal of your subscription to the &LISTNAME list
&WEEKDAY, &DATE &TIME

Your subscription to the &LISTNAME list is due for renewal. If you wish
to remain subscribed to &LISTNAME, please issue the following command
to &MYNAMES at your earliest convenience:

.ce CONFIRM &LISTNAME


You will be automatically removed from the list if you do not send
a CONFIRM command within the next &DELAY days.

PS: In order to facilitate the task, this message has been specially
formatted so that you only need to forward it back to &MYNAMES
to have the command executed. Note that while the formats
produced by the forwarding function of most mail packages are supported,
replying will seldom work, so make sure to forward and not reply.
.fo off
-------------------------------------------------------------------------
// JOB
CONFIRM &LISTNAME
// EOJ
>>> RENEW2 Expiration of your subscription to the &LISTNAME list
.re owners
&WEEKDAY, &DATE &TIME

Your subscription to the &LISTNAME list has expired and you have failed
to confirm it in the &DELAY day delay that you had been granted. You
have therefore been automatically removed from the list. You can
re-subscribe to the list, if you want to, by sending the following
command to &MYNAMES:

.ce SUBscribe &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.

.im $SIGNUP
>>> $SIGNUP Standard blurb to new subscribers
Please save this message for future reference, especially if you are not
familiar with LISTSERV. This might look like a waste of disk space
now, but in 6 months you will be glad you saved this information when
you realize that you cannot remember what are the lists you are
subscribed to,
or what is the command to leave the list to avoid filling up your mailbox
while you are on vacations. In fact, you should create a new mail folder
for subscription confirmation messages like this one, and for the
"welcome messages" from the list owners that you will occasionally
receive after subscribing to a new list.

To send a message to all the people currently subscribed to the list,
just send mail to &LISTADDR. This is called "sending mail to the
list", because you send mail to a single address and LISTSERV makes
copies for all the people who have subscribed. This address
(&LISTADDR) is also called the "list address". You must never
try to send any command to that address, as it would be distributed to
all the people who have subscribed. All commands must be sent to the
"LISTSERV address", &MYNAMES. It is very important to understand the
difference between the two, but fortunately it is not complicated.
The LISTSERV address is like a FAX number, and the list address is like a
normal phone line. If you make your FAX call someone's regular phone
number by mistake, it will be an unpleasant experience for him but you
will probably be excused the first time. If you do it regularly, however,
he will probably get upset and send you a nasty complaint. It is the
same with mailing lists, with the difference that you are calling
hundreds or thousands of people at the same time, so a lot more people
get annoyed if you use the wrong number.

You may leave the list at any time by sending a "SIGNOFF &LISTNAME"
command to &MYNAMES. You can also tell LISTSERV how you want it to
confirm the receipt of messages you send to the list. If you do not
trust the system, send a "SET &LISTNAME REPRO" command and LISTSERV will
send you a copy of your own messages, so that you can see that the
message was distributed and did not get damaged on the way. After a while
you may find that this is getting annoying, especially if your mail
program does not tell you that the message is from you when it informs
you that new mail has arrived from &LISTNAME. If you send a "SET
&LISTNAME ACK NOREPRO" command, LISTSERV will mail you a short
acknowledgement instead, which will look different in your mailbox
directory. With most mail programs you will know immediately that this is
an acknowledgement you can read later. Finally, you can turn off
acknowledgements completely with "SET &LISTNAME NOACK NOREPRO".

.bb &DEFOPT ^= ''
Following instructions from the list owner, your subscription options
have been set to "&DEFOPT" rather than the usual LISTSERV defaults.
For more information about subscription options, send a "QUERY &LISTNAME"
command to &MYNAMES.

.eb
.bb &KWD(NOTEBOOK,1) = YES
Contributions sent to this list are automatically archived. You can
get a list of the available archive files by sending an
"INDEX &LISTNAME" command to &MYNAMES. You can then order these files
with a "GET &LISTNAME LOGxxxx" command, or using LISTSERV's
database search facilities. Send an "INFO DATABASE" command
for more information on the latter.

.eb
.bb &KWD(CONFIDENTIAL,1) = YES
IMPORTANT: This list is confidential. You should not publicly mention
its existence, or forward copies of information you have obtained from it
to third parties.
.bb &KWD(NOTEBOOK,1) = YES
Please note that the "GIVE" command is automatically
disabled for all archive files.
.eb

.eb
.bb CONCEAL not in &DEFOPT
.se x = &KWD(REVIEW)
.bb (&x ^= POSTMASTER) and (&x ^= OWNER)
Please note that it is presently possible for
.bb &x = PUBLIC
anybody
.eb
.bb &x ^= PUBLIC
other people
.eb
to determine that you are signed up to the list through the use of the
"REVIEW" command, which returns the e-mail address and name of all
the subscribers. If you do not want your name to be visible,
just issue a "SET &LISTNAME CONCEAL" command.

.eb
.eb
More information on LISTSERV commands can be found in the LISTSERV
reference card, which you can retrieve by sending an "INFO REFCARD"
command to &MYNAMES.
>>> SUB_CLOSED Message sent to user trying SUBSCRIBE on closed list
Sorry, the &LISTNAME list is closed. Contact the list owner
(&OWNER) for more information.
>>> SUB_OWNER Message sent to user trying SUBSCRIBE on by-owner list
Your request to join the &LISTNAME list has been forwarded to the list
owner for approval. If you have any question about the list, you can
reach the list owner at &OWNER.
>>> POST_EDITOR Message sent to user when posting is forwarded to editor
Your &MESSAGE has been submitted to the moderator of the &LISTNAME
list: &MBX(&MODERATOR).
>>> REQACK1 Your message to &LISTNAME-request@&MYHOST
&WEEKDAY, &DATE &TIME

Your message to &LISTNAME-request@&MYHOST has been forwarded to the
"list owners" (the people who manage the &LISTNAME list). If you wanted
to reach a human being, you used the correct procedure
and you can ignore the
remainder of this message. If you were trying to send a command for the
computer to execute, please read on.

The &LISTNAME list is managed by a LISTSERV server. LISTSERV
commands should always be sent to the "LISTSERV" address, ie
&MYNAMES.
LISTSERV never tries to process messages sent to the
&LISTNAME-request address; it simply forwards them to a human being,
and acknowledges receipt with the present message.

The "listname-request" convention originated on the Internet a long time
ago. At the time, lists were always managed manually, and
this address was defined as an alias
for the person(s) in charge of the mailing list. You would write to the
"listname-request" address to ask for information about the list, ask to
be added to the list, make suggestions about the contents and policy,
etc. Because this address was always a human being, people knew and
expected to be talking to a human being, not to a computer.
Unfortunately,
some recent list management
packages screen
incoming messages to the "listname-request" address and attempt to
determine whether they are requests to join or leave the list. They look
for words such as "subscribe", "add", "leave", "off", and so on. If they
decide your message is a request to join or leave the list, they update
the list automatically; otherwise, they forward the message to the list
owners. Naturally, this means that if you write to the list owners about
someone else's unsuccessful attempts to leave the list, you stand good
chances of being automatically removed from the list, whereas the list
owners will never receive your message. No one really benefits from this.
There is no reliable mechanism to contact a human being for assistance,
and you can never be sure whether your request will be interpreted as a
command or as a message to the list owners. This is why LISTSERV uses
two separate addresses, one for the people in charge of the list and one
for the computer that runs it. This way you always know what will happen,
especially if you are writing in a language other than English.

In any case, if your message was a LISTSERV command, you should now
resend it to &MYNAMES. The list owners know that you have received
this message and may assume that you will resend the command on your
own. You will find instructions for the most common administrative
requests below.

.FO OFF
*********************
* TO LEAVE THE LIST *
*********************
.FO ON

Write to &MYNAMES and, in the text of your message
(not the subject line), write: SIGNOFF &LISTNAME

.FO OFF
********************
* TO JOIN THE LIST *
********************
.FO ON

Write to &MYNAMES and, in the text of your message
(not the subject line), write: SUBSCRIBE &LISTNAME

.FO OFF
************************
* FOR MORE INFORMATION *
************************
.FO ON

Write to &MYNAMES and, in the text of
your message (not the subject line), write: "HELP" or "INFO" (without
the quotes). HELP will give you a short help message and INFO a list of
the documents you can order.
>>> CONFIRM1 Text of confirmation requests
Your command:

.ce &CMD

.bb &INFO = ''
requires confirmation.
.eb
.bb &INFO ^= ''
&INFO

.eb
To confirm the execution of your command, simply 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 &MYSELF (without using the "reply" function - this is very
important) and type "ok &CODE" as the text of your message.

Finally, your command will be cancelled automatically if you do not
confirm it within &EXPIRE. 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 command expire on its own.