This message is sent to the list periodically, as a guide to the creation of efficient and effective messages to other R:Base users and developers. New bullet points are added from time to time, as they are suggested by members. Please review these suggestions for usage and etiquette:
* Use "plain text." Suppress HTML effects from your posts to list servers. Many subscribers are using email readers that cannot make any sense of your HTML. The colors and fonts and sizes that look great to you on your workstation can be really ugly or even unreadable on other people's workstations. HTML style settings can add many kilobytes to the size of your message, and easily can swell your message size to the point where it will exceed the limits for this plain text email list server. If you are using MS Outlook Express, for example, in your contact list, right click on [EMAIL PROTECTED], select "properties," click the "name" tab, and put a check in the box for "send plain text message." * 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 or many file extensions will often 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, only a few of whom may have a use for it. * Never attach an executable file. Most companies' mail servers or virus checkers will bar your message from being delivered, for fear it contains a virus. * Replies that are personal comments, and thank yous, and things that are not intended for 300 people to read, should be replied to the original SENDER of the email, not necessarily to rbase- [EMAIL PROTECTED] * 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. * Use your real name, not a "screen name" or "handle," and use both your first name and last name in your email "from" settings, (unless you have a really distinctive name like Razzak, Sami, or Oma.) There are many people named Dan and Ben and Jim and Mike and Bill on the list server. Help everyone keep each other straight. * The R:Base List server is not the 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. You should know that there is a separate system set up for problem reports for RBTI products. Those items should be reported through www.rbase.com\rbg7rdcc (the R:BASE Developers' Corner Crew), or through email to [EMAIL PROTECTED] That is the fastest and most effective way to get the problems corrected in production releases. Wayne Erickson and the development programming team are not members of the list server, and don't automatically hear about things reported here. You can email files that illustrate problems to [EMAIL PROTECTED] Bill Downall volunteer List Manager, [EMAIL PROTECTED]
