|App_rpt-users -- Users of Asterisk app_rpt|
This list is for users of app_rpt and other Free Software based on Asterisk for radio linking.
To see the collection of prior postings to the list, visit the App_rpt-users Archives.
To post a message to all the list members, send email to
You can subscribe to the list, or change your existing subscription, in the sections below.
|Subscribing to App_rpt-users|
Subscribe to App_rpt-users by filling out the following form. You will be sent email requesting confirmation, to prevent others from gratuitously subscribing you. This is a hidden list, which means that the list of members is available only to the list administrator.
|App_rpt-users Posting Guidelines:|
➡ Check the archives
Please check the archives before posting a question. It's quite possible someone has already experienced the same issue and fixed it before.
➡ Be concise
The interest list maintains a maximum message length of 100 kilobytes. Remember that hundreds of copies of your message will exist in mailboxes -- please keep your messages as short as possible. Avoid including log output (select only the most relevant lines, or place the log in a bpaste instead) or excessively quoting previous messages in the thread (trim the quoted text down to the most recent/relevant messages only).
➡ Plain text please
Set your mailer to send only plain text messages to the list (How? ). Why? HTML is designed for web pages, not emails, and uses a lot more bandwidth. It also makes the archives much harder to read.
➡ Starting a New Subject
When you send in a new topic, do not start by replying to an existing message and deleting the subject, but rather, start a new message to "email@example.com". This keeps messages organized by thread, for people who like to use threads (on high-volume mailing lists like this one, threads can be a great convenience).
Furthermore, please do not recycle messages. Recycling messages is replying to an existing thread by changing the thread name. This creates confusion and diverts the number of people replying to the topic. Also ensure your email client inserts a proper "In-reply-to:" header or "References:" header. This ensures replies will stay in the proper thread.
➡ Write a Good Subject Line
Make a subject line that clearly tells us what you need. This is a point that can't be overemphasized. Try "I can't get my Tunnel interface to come up" instead of "Argg - help me!!!" Why? So that people with certain skills, looking for someone to help, will notice your message. That helps you get help from the right people quickly.
➡ If You Are Replying to a Message
Make sure we can tell what you are replying to. Place each part of your reply after the text it addresses (i.e., NO Top-Posting, please see "Wikipedia - Top Posting" and links therein for more on this). Most mail readers automatically put a '>' character in front of each replied-to line. It gives a conversational flow to the text, and people know what you're replying to. Trim irrelevant material. It makes it easier to read your reply and helps the reader to stay on subject. Using bottom, interleaved posting is recommended as it is more organised.
The fact that you're sending the email from a smart-phone or similar device doesn't invalidate those guidelines. Please consider sending the reply at a later time when you have access to your regular email system or send a private reply instead.
➡ Let us know when your question is answeredWhen you get a solution to your question (or find it yourself after posting to the list), reply to your original e-mail describing what solved your problem, adding a [SOLVED] to the end of the subject line. This will let people know that you don't need help any more with this and can look for other posts to help. Also, it makes a search in the archives easier when someone has a related problem in the future.
➡ Proper posting style
Top posting is replying to a message on "top" of the quoted text of the previous correspondence. This is highly unwanted in mailing lists because it increases the size of the daily digests to be sent out & is highly confusing and incoherent. By default, most email clients use this (includes gmail & hotmail). Please, remove the irrelevant part of the previous communication(in case of more than a single correspondence) and use bottom, interleaved posting.
Do not over-quote by the hierarchy level in the correspondence.
Bottom, interleaved posting is replying to the relevant parts of the previous correspondence just below the block(s) of sentences. For a comment to another block of sentences of the same quoted text, you should move below that relevant block again. Do not reply below the whole of the quoted text. Also remove any irrelevant text.
Please provide URLs to articles wherever possible. Avoid cutting and pasting whole articles especially considering the fact that all may not be interested. Pasting whole articles may also amount to copyright violations, which is not something that this list encourages.
Read the above mentioned pdf file on mailing list guidelines by Shakthi Kannan. The illustrative document should clear all doubts.
➡ Avoid long signatures and disclaimers
We find value in your main content rather than signatures. One or two lines would be optimal to convey messages that must be included in your signature and avoid huge disclaimers describing how your mail is private and confidential while sending things to the mailing list. If your company/organization enforces that in the mail gateway, use a webmail with pop/imap access like gmail for instance. Such disclaimers aren't enforceable half of the time and are monumentally silly in a public mailing list.
➡ Use the common language
Please post and communicate in English, it's the common language of amateur radio. Other languages might be ignored merely because the users in these lists might only know English or use it as their common language.
Use the universally accepted standard English. Always do a spell check before mailing to the list. Grammar doesn't matter as long as one is understood. Do not use SMS language. Do not use dots(".....") to conclude the sentences as is common across social networks.
➡ DO NOT USE ALL CAPITALS
Using capital letters in your sentences is considered shouting. It is considered as being rude. If you want to emphasize on something *use this* or _this_.
The above isn't intended to be a complete list for rules, but a general guideline. Most of this was taken from The Fedora Project Mailing List Guidelines.
Eric S. Raymond has a great guide on mailing lists and how to ask questions the right way for your further reading.