PNX-dev -- P25 Network Exchange development list

About PNX-dev
English (USA)

A list for the active developers of linking P25 repeaters based on a common multicast/IP protocol.

This is not a user support list.

To see the collection of prior postings to the list, visit the PNX-dev Archives.

Using PNX-dev
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 PNX-dev

Subscribe to PNX-dev by filling out the following form. You will be sent email requesting confirmation, to prevent others from gratuitously subscribing you. This is a private list, which means that the list of members is not available to non-members.

    Your email address:
    Your name (optional):
    You may enter a privacy password below. This provides only mild security, but should prevent others from messing with your subscription. Do not use a valuable password as it will occasionally be emailed back to you in cleartext.

    If you choose not to enter a password, one will be automatically generated for you, and it will be sent to you once you've confirmed your subscription. You can always request a mail-back of your password when you edit your personal options.
    Pick a password:
    Reenter password to confirm:
    Which language do you prefer to display your messages? English (USA)
PNX-dev Subscribers
(The subscribers list is only available to the list members.)

Enter your address and password to visit the subscribers list:

Address: Password:   

To unsubscribe from PNX-dev, get a password reminder, or change your subscription options enter your subscription email address:

If you leave the field blank, you will be prompted for your email address
PNX-dev Posting Standards

Posting Guidelines

Keep it Short

The PNX-dev list maintains a maximum message length of 4000 kilobytes ;  Avoid including log output (select only the most relevant lines, or place the log on a website or in a pastebin instead) or excessively quoting previous messages in the thread (trim the quoted text down to the most recent/relevant messages only).

No HTML Mail, 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. Many list members actually block HTML because it is used for malicious code.

Not only does HTML mail be used to run malicious scripts, but when using handheld devices the time taken for the page to appear is also much higher.

(see "7 reasons why HTML e-mail is EVIL! ")

Starting a New Subject

When you send in a new topic, do not start by replying to an existing message, but rather, start a new message to "". 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. This messes up the archives too.

For details see

Write a Good Subject Line

Make a subject line that clearly tells us what you are doing. This is a point that can't be overemphasized.

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.

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.

Read the above mentioned pdf file on mailing list guidelines by Shakthi Kannan : . The illustrative document should clear all doubts.

Be Courteous

Be courteous and polite to fellow members in the list.

Do not Cross Post

Avoid posting to multiple lists simultaneously. Pick a mailing list that is most suitable for your post and just use that. CC'ing multiple lists should be avoided.

Post to the the mailing list that is most suited to your purpose and then just copy the link to that page or mailing list and paste to all the other mailing lists you want to post to. This will reduce the amount of data duplicated - only one copy will be accessed by all who read it.

No chain letters

Never send chain letters to the mailing list. A mail simultaneously sent to more than 10 users will not reach the list. This is to eliminate possible spammers/bulk mailers to reach the list.

Don't make social network connections through the mailing list

Do not send invitations to social networking sites through the mailing list. The email addresses of people on the mailing list is visible to the members. To add mailing list contacts to your social network, try searching them on the social networking site or contact through email & not the mailing list.

Commercial messages

When using the mailing list for commercial purpose, please prefix the subject line with "COMMERCIAL".


To unsubscribe from the list you can visit the PNX-dev List web page

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.

Do not use a PGP Style Signature that is not published

Use of PGP or GnuPG signing is encouraged. However, if the corresponding key is not published on a public keyserver, then the message will cause some email client applications (MUAs) that are PGP/GPG aware to hang while they try all known keyservers. This can take a long time and cause frustration for other users. If you have a unpublished key or new key consider attaching said key (in .asc format) to the email thread. For more information on how to properly create and use GPG keys, read the Creating GPG Keys page.

Use the common language

Please communicate in English. Other languages might be ignored merely because the users in these lists might only know English or use it as their common language.

Use standard language and not colloquial or regionally accepted abbreviations.Visit for more such acronyms.

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 (to a point). Do not use SMS language. Do not use dots(".....") to conclude the sentences as is common across social networks.


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_.

PNX-dev list run by bryan at
PNX-dev administrative interface (requires authorization)
Overview of all mailing lists

Delivered by Mailman
version 2.1.16
Python Powered GNU's Not Unix Debian Powered