Dear Subscribers,
The following is an update to list of the Usage
Guidelines for the R:BASE RBASE-L Email List Server.
-----------------------------------------------------
Our goal is to provide a productive and informative
environment, for ANY person wishing to participate, to
discuss their R:BASE related achievements, experiences,
and other information that is relevant to the R:BASE
subject. This forum is open to ALL who abide by the
rules that are in place, which are designed to protect
the rights of the entire group, not just a particular
individual.
This list server is to be used for ALL productive
exchanges between subscribers to discuss R:BASE issues
related to programming, applications, technical issues
and the like. Job solicitation is permitted as this list
is a great source of opportunity to all of its members.
The following suggestions are a guide to the creation
of efficient and effective messages to other subscribers.
--------------------------
When Posting Your Messages
--------------------------
* Use "plain text." Suppress HTML effects from your posts
to List Servers. Some subscribers are using email readers
that cannot make any sense of HTML. The colors, fonts,
sizes, images, and background images that look great to
you on your workstation can be unreadable on other people's
workstations. HTML style settings can add many kilobytes to
the size of your message, and can easily swell your message
size, and follow up replies, to the point where it will
exceed the limits for some users on the List Server. For
example, if you are using MS Outlook Express, in your contact
list, right click "[email protected]", select "Properties,"
click the "Name" tab, and put a check in the box for "Send
plain text message".
* Remove any lengthy signatures which have multiple contact
lines of information for yourself. As an email list server,
your email address is sufficient.
* Remove any "disclaimer" signatures from your posts. These
also add many kilobytes to the messages.
* Use a clear subject, that helps a reader determine whether
your message is of interest to him or her.
* Do not start your subject with any of these words: HELP,
SUBSCRIBE, CANCEL
* Quote back enough of a preceding message to orient readers
to the context. Not all readers retrieve messages with the
same frequency you do, nor do their email readers sort
messages in the same order as yours. Don't assume everyone
will know what message you are responding to.
* Do not quote entire long preceding messages with your
answer. Quote just enough to set the context.
* Attach only very small attachments. When possible, include
code samples within the text, not as attachments, since some
people reading your message have email readers that cannot
interpret the MIME content.
* If you want to share large files with the group, do not
attach them to your List Server messages. Direct readers to
a web page from which they can download it, or ask them to
email you directly -- off the list -- with personal requests.
Large attachments will probably cause your message to be
blocked by the List Server administration settings. Even if
it does get through, you will be clogging lots of email
servers, sending that large attachment to hundreds of people,
when only a few of whom may have a use for it.
* Never attach an executable file. Most companies' mail
servers, filters, or virus checkers will bar your message
from being delivered, for fear it contains a virus.
* Do not let your email client ask for a receipt for mail
you post to a list server.
* Do not mark messages to a list server as "high priority."
For most people receiving list server messages, direct
personal business mail is always a higher priority than bulk
mail. As important as your message may seem to you at the
time, list servers are, in reality, distributing bulk mail.
* The RBASE List Server is not the main system to use to report
bugs or make requests for new features, although bringing those
items up on the List Server is a great way to discuss workarounds
for bugs, and the overall usefulness of feature requests. There
is a separate system set up for problem reports for bugs and
enhancement requests. Those items should be reported through
www.rbase.com\rbg7rdcc, the R:BASE Developers' Corner Crew.
There is a full bug and feature request reporting and tracking
system there. That's the fastest and most effective way to get
the problems corrected in production releases, as the R:BASE
Development Team does not automatically hear about the items
reported here. You can email files that illustrate problems to
mailto:[EMAIL PROTECTED]
We hope you find your RBASE List Server subscription useful!
Best Regards,
John Minyo II
R:BASE Technologies, Inc.
Customer Service
http://www.rbase.com
[EMAIL PROTECTED]
(724) 733-0053
--- RBASE-L
================================================
TO POST A MESSAGE TO ALL MEMBERS:
Send a plain text email to [email protected]
(Don't use any of these words as your Subject:
INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH,
REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP)
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: INTRO
================================================
TO UNSUBSCRIBE:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: UNSUBSCRIBE
================================================
TO SEARCH ARCHIVES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: SEARCH-n
(where n is the number of days). In the message body,
place any
text to search for.
================================================
