*******************************************************************
* Please note that due to the large number of reports apparently *
* resulting from phone line noise and other "accidental" reports, *
* we are now pre-filtering messages that do not have a meaningful *
* subject. We apologize if this causes us to miss your report. *
*******************************************************************
This is an automated response to your Pine[R] bug report. The purpose of
this message is to: 1) acknowledge receipt of your report, 2) apologize in
advance for the fact that you may not receive any other response to it, 3)
assure you that if it is a bug report or enhancement suggestion, we will
look at it carefully, and 4) tell you how to get more information or help.
Pine is now used by literally millions of people around the world, and
thousands more every day. Not surprisingly, the number of messages sent
to our "pine-bugs" address has become enormous. Since we receive no
funding to support anyone outside the University of Washington, it is no
longer possible to answer all of them individually.
Other sources of help:
o In addition to Pine's context-sensitive internal help text, also read
the Release Notes (the R command on the Main Menu.)
o Check out the Pine Frequently Asked Questions (FAQ) list. To get a
copy by email, simply REPLY to this message, or send any message to:
pine-faq @
docserver .
cac .
washington .
edu
o Check with your local support staff. If you are not sure how to
contact them, try sending a very polite note to "postmaster"
on your system, asking that your inquiry be directed to the help desk.
o If you can't get any help from your local support staff (or you
*are* the local support staff), consider sending a message to the
world-wide "pine-info" email list at:
pine-info @
cac .
washington .
edu
or post to the comp.mail.pine newsgroup (pine-info and comp.mail.pine
are linked together, so there is no need to both send email and post).
Your message will be seen by thousands of Pine users and system
administrators, one of whom may have just the information you seek.
o If you are handy with FTP or WWW tools, you may find some useful
documentation on our Pine Information Center servers:
ftp://ftp.cac.washington.edu/pine
http://www.cac.washington.edu/pine
o If you really, *really* need to get in touch with the Pine development
team directly, send a message to:
pine @
cac .
washington .
edu
However: please try all the other alternatives first, and understand
that because so many people are now sending messages to that address
as well --many of which are inquiries that could be answered by reading
the documentation or FAQ-- it is no longer possible for us to respond
to all of them.
Note that we get many questions that are not actually about Pine. In case
your inquiry concerns programs such as talk, chat, or IRC, or problems
with disk space on your system, or with unknown/invalid email addresses,
please contact your local computer support staff. However, we still
welcome actual bug reports and suggestions.
With sincere apologies for this impersonal response,
The Pine Development Team Pine is a registered trademark
University of Washington of, and copyright by, the
Seattle, WA, USA University of Washington.
|
|
