Returned mail: Service unavailable
Mail Delivery Subsystem
MAILER-DAEMON at eskimo.com
Mon Oct 28 07:00:00 EST 1996
This is a MIME-encapsulated message
--RAA25443.846552334/mail.eskimo.com
The original message was received at Mon, 28 Oct 1996 17:20:28 -0800 (PST)
from [129.229.101.1]
----- The following addresses have delivery notifications -----
<phillip.dillinger at sealabs.com> (unrecoverable error)
----- Transcript of session follows -----
... while talking to klawatti.sealabs.com.:
>>> DATA
<<< 550 Too much data
554 <phillip.dillinger at sealabs.com>... Service unavailable
--RAA25443.846552334/mail.eskimo.com
Content-Type: message/delivery-status
Reporting-MTA: dns; mail.eskimo.com
Received-From-MTA: dns; [129.229.101.1]
Arrival-Date: Mon, 28 Oct 1996 17:20:28 -0800 (PST)
Final-Recipient: rfc822; phillip.dillinger at sealabs.com
Action: failed
Status: 2.0.0
Remote-MTA: dns; klawatti.sealabs.com
Diagnostic-Code: smtp; 250 Recipient ok
Last-Attempt-Date: Mon, 28 Oct 1996 17:25:30 -0800 (PST)
--RAA25443.846552334/mail.eskimo.com
Content-Type: message/rfc822
Return-Path: grassu at isis.cecer.army.mil
Received: from isis.cecer.army.mil ([129.229.101.1]) by mail.eskimo.com (8.7.6/
8.6.12) with ESMTP id RAA25216 for <phillip.dillinger at sealabs.com>; Mon, 28 Oct
1996 17:20:28 -0800 (PST)
Received: (from listserv at localhost) by isis.cecer.army.mil (8.7.6/8.7.3) id TAA
12586; Mon, 28 Oct 1996 19:18:03 -0600 (CST)
Date: Mon, 28 Oct 1996 19:18:03 -0600 (CST)
Message-Id: <199610290118.TAA12586 at isis.cecer.army.mil>
X-Authentication-Warning: isis.cecer.army.mil: listserv set sender to grassu at li
st-server.cecer.army.mil using -f
To: phillip.dillinger at sealabs.com
From: Majordomo at cecer.army.mil
Subject: Welcome to grassu
Reply-To: Majordomo at cecer.army.mil
--
Welcome to the grassu mailing list!
If you ever want to remove yourself from this mailing list,
you can send mail to "Majordomo" with the following command
in the body of your email message:
unsubscribe grassu phillip.dillinger at sealabs.com
Here's the general information for the list you've
subscribed to, in case you don't already have it:
To: grassu-list at moon.cecer.army.mil
Subject: Intro to the GRASShopper lists [posted once a month]
-------------------------------------------------------------------------
About the GRASS GIS Mailing Lists
Office of Grass Integration
[This document is sent out to the GRASS Users' Electronic Mailing List
about once a month as a reminder and introduction to the list manager
software.]
The Office of GRASS Integration at USACERL set up a service that will be of
interest especially to those GRASS users who have access to electronic mail.
We have set up two e-mail lists to foster communication between GRASS Users
and GRASS Programmers. The lists work on the principle of "mail exploding"
-- a user mails a note to one address, and the computer at that address
"explodes" the letter, re-mailing it to everyone who subscribes to the
list. Replies to the original letter generally go to the list as well (if
there is general interest in the answer), but can be directed solely to the
original author if you desire. Both lists are also automatically preserved in
an archive, and users may at any time request a file containing an archive of
list messages.
These lists exist to foster communication between parties interested in the
GRASS GIS software; many CERL employees will participate in the lists, but on
an infrequent and informal basis. The list will be maintained and stored
on CERL computers; however, CERL will not officially monitor the content,
intent, or accuracy of any messages that pass through the list. The
point-of-contact for the list is:
grass-lists-owner at moon.cecer.army.mil
The list for GRASS users and friends is called "grassu" (short for
"GRASS users"), while the list for programmers and system-level users is
called "grassp" (short for "GRASS programmers"). Topics for discussion
on the |grassu-list| may include questions about various GRASS
applications, sources of (or reviews of) third-party support, and various
and sundry other experiences with GRASS. |Grassp-list| topics will
include discussion of the algorithms and intricacies of current GRASS
programs, programming hints and ideas for new GRASS applications, and other
prorgrammer-oriented issues. Note that the grassp-list is |not| the
best (nor even an appropriate) place to report suspected bugs in GRASS
code; the current <bug.report.sh> program and correspondance with OGI are
the preferred problem-report procedures.
ACCESSING THE MAILING LISTS:
Each mailing list has two addresses:
(1) the mailing address used to "explode" messages out to all subscribers, and
(2) the mailing address to send commands to the list-management software
(e.g., to subscribe and unsubscribe from the list).
(1) If you wish to send an e-mail message to all subscribers of a list,
the e-mailing address should take the form of:
grassu-list at moon.cecer.army.mil
for the GRASS user's list, and
grassp-list at moon.cecer.army.mil
for the GRASS programmer's list. {1}
{Footnote1: These, and all other e-mail addresses in this article, are
provided in an "Internet-standard" format; different host computers might
require different specifications of the address. The system administrator
at each site should be able to help if the addresses here do not work as
specified.}
(2) The other important address for each list is the destination of commands t
o
the list-management software (such as subscribe, unsubscribe, etc.). These
messages should be e-mailed to to:
grassu-request at moon.cecer.army.mil
or
grassp-request at moon.cecer.army.mil
as appropriate. Multiple commands may be included in messages. Commands
must be located in the BODY of the letter; commands that appear on the
"Subject" line will be ignored. Only one command should appear per line.
Upper- or lower-case letters may be used for commands, and they may be
abbreviated to simply the first three letters if desired.
All commands are acknowledged with return e-mail.
COMMANDS:
Commands that the server will accept are given below.
Commands should be sent in the BODY of your email message
and be addressed to "Majordomo".
Commands that appear in the "Subject" line of your e-mail message
will NOT be processed.
HELp
Retrieves a copy of the listserv software's help file.
LISts
Retrieves names of lists that are served by this MajorDomo server.
SUBscribe <list> [<address>]
This command subscribes yourself (or <address> if specified)
to the named mailing list <list>. The subscriber's e-mail address is
taken from the "From:" line of the subscription letter if not specified
in the body of your letter.
UNSubscribe <list> [<address>]
This command unsubscribes you (or <address>, if specified),
from the specified <list>.
WHIch [<address>]
This command returns the names of the lists to which you
(or <address>, if specified) are subscribed.
WHO <list>
This command returns a list of the specified <list>'s subscribers.
INFO <list>
Retrieves general introductory information for the named <list>.
END
Stop processing commands (useful if your mailer adds a signature).
INDex <list>
This command retrieves a list of the specified mailing <list>'s
archive files, which you can subsequently obtain using the "GET" command.
GET <list> <filename>
Retrieves a copy of the specified <filename> from the specified
<list>'s archive directory. Case and spelling ARE important; the filename
specified must |exactly| match a file shown by the "INDex" command.
A message acknowledging the request will be mailed to the user.
If the file is short, the user will simply receive a copy of it
in mail. For example, the command "GET grassu-list LOG"
(capitalization of "LOG" is important) will cause the list-server
to mail back a copy of the most recent messages to the list (which are
always stored in the file named "LOG").
If the file is very long, the list server software will <uuencode>
the file and split it into several mail-sized chunks. ("uuencode" and
"uudecode" are common UNIX programs to encode files for e-mail transport.
The user's local computer must have the <uudecode> program in order to decode
these files. The acknowledgement note will inform the user how many
chunks to expect, and each chunk will have a subject line that specifies
"filename: part X of Y".
EXAMPLE OF LIST USAGE:
To subscribe to one of the lists:
Send a mail message to either
grassu-request at moon.cecer.army.mil
or
grassp-request at moon.cecer.army.mil
with "subscribe <list> [<addresss>]" in the BODY of your letter.
Replace <list> with either:
grassu-list
or
grassp-list
Replace [<address>] with the complete email address to which you wish your
email to be sent.
If you do not specify an <address> in the body of your letter, the list
will subscribe you to the list at the email address given in your email
header's "From:" line.
E.g.:
"subscribe grassu-list nixon at diego.cecer.army.mil"
might be used to subscribe user "nixon" to the grass user's list.
SUMMARY
These two lists are provided by OGI as a service for the GRASS community; we
hope that they will prove to be useful resources. We encourage you to try
several commands to experiment with the lists. If there are any questions,
feel free to send mail to:
grass-lists-owner at moon.cecer.army.mil
or contact the OGI by phone or mail.
-------------------------------------------------------------------------
--RAA25443.846552334/mail.eskimo.com--
More information about the grass-user
mailing list