[DarkPixel.com]

Download snppsend

snppsend:

When snppsend starts it will read configuration information from two files located in the ~/.snppsend/* directory.
After configuration files have been read from the users home directory, snppsend will proceed to read configuration file information from a second set of files located in /etc/snppsend/*

The two directories (~/.snppsend/ and /etc/snppsend) both should contain two files in the following formats:

File: providers
PagingProviderName <TAB> Host or IP Address <TAB> Port (Usually 444) <TAB> Max Chars

The following line would setup a paging provider of DorkPagingCo that has their SNPP server on 111.222.333.111 port 444. This provider allows you to send up to 240 characters per page.
DorkPagingCo <TAB> 111.222.333.111 <TAB> 444 <TAB> 240


File: receivers
ReceiverName <TAB> ProviderName <TAB> PagerNumber

The following line would setup a pager for JoeBob who uses DorkPagingCo
JoeBob <TAB> DorkPagingCo <TAB> 5554239755


Following the example, once those two files are setup, you can page JoeBob by typing the following command:
snppsend joebob<ENTER>
snppsend will then ask you for the message to send.


Known Bugs / Problems / ToDo:
A few places are still case sensitive. - When you type a receiver on the command line (snppsend joebob), it must be in lower case--no matter how they are specified in the receivers file. This will be fixed soon--but I wanted to get this initial version out. Just remember--command line must be in lower case always.

snppsend does not gracefully handle not finding configuration files. It usually dies with ugly error messages. You must have at least one providers file and one receivers file. It does not matter which of the two directories these files come from--and both files don't have to be in the same directory. providers can be in /etc/snppsend while receivers can be in ~/.snppsend.

Files in ~/.snppsend are loaded FIRST. This allows an individual to override the system configuration files with their settings. The two files are actually merged together. Files from the users home directory are loaded--then the /etc/snppsend files. If there is a "joebob" in the users config and a "joebob" in the system config, the users "joebob" will be loaded and the system entry will not.

Documentation does not exist. I want to change this. I will soon.
If you're a Perl programmer, read the source--I'm sure you can figure it out. Just don't hurt yourself laughing. This is my first attempt at writing perl by the way. ;)



Any bugs, comments, suggestions about snppsend can be emailed to code@darkpixel.com

If you need HELP with snppsend, please use my support address: support@darkpixel.com
Support is free, however please remember that I am trying to support it in my spare time and I am not earning anything from this.

The following information is also displayed in the header of snppsend:
This script is released to the public domain.
Use it, modify it, share it, hack it. Enjoy it.
Any updates I make will be posted on my website.
http://www.darkpixel.com/

If you update snppsend in a way that may be
meaningful to others, feel free to email me and
I will post your version on my site and link to yours.
I may even include your changes in the next version.


Some shout-outs
jeek in #pound-perl.pm on EFNet
Steve Kaylor and Brandon Zehm - their original script
inspired this program and I borrowed some of their
socket and snpp server communication code.


Copyright © 2006 DarkPixel.com