The Local Mail Server
A Mail File Server on the Destkop
In an effort to supply administrators and programmers with useful code and configuration information, a web site mail server has been set up on the local desk top machine. Sometimes when you are working on a project, it can be quite convenient to have a "model" to go by as you are solving the "challenges" that lie between you and success!
You may, of course, always print out a web page for reference, but obtaining the actual copy will get you that much closer to implementing the application since you may "extract" the mailed document as a working file which you may then edit and "beat into submission." :) Configure, I mean. :)
To activate the mailer, which uses an enhanced format of the "mailto:" html option, click on the "Mail it to me" link from any Mail Panel, and if your mailer is tied into your browser, which most are, your mail application will be opened and ready to add text to the body. There is no need to write anything unless you are in a communicative mood; you just click on the "Send" button and out it goes...
On the server side, the request is trapped by procmail and, in most cases, the file is sent back as a plain text auto-response. However, it may also be sent in a MIME format for tar.gz distributions or packages. You then need to extract it from your mailer and, if a config file, probably substitute my callsigns with your callsigns. And, further, you may need to modify the code or data to suit your system and operating requirements.
A quick note about availability! The server is not a 24x7 operation, more like a 10x7. I open up here between 6 and 7 am EST and close down about 4 or 5 pm. I am usually up seven days a week, but there are periods when I may be away for up to three (3) weeks at a time. When up, I pop for mail about every two (2) hours. Please check here to see if the mail file server is available.
A Few Operational Details...
E-Mail File Server Status Mail File Server up Machine 44.56.26.10 Current Documents Available 21
- Extracting a file from a UNIX/Linux mailer
Once you have received your data in your mailbox, you may save the document by using this command:
- w <number_of_email> <name_of_file>
Where the number of the email is the ennumerated listing number associated with each piece of mail, and the file name is anything you choose... This operation will create a file in the current directory. It will not contain any email header information.If you need that, then use the "s" command instead of the "w" command as noted above. This will save the entire "raw" file, headers and all...
NOTE: These comments pertain to the original text/character-based mailer, /bin/mail, that comes standard with every UNIX/Linux system. (Other mailers like Pine, for example, have their own methods of saving email to regular flat files.)
- Converting Callsigns Using sed
After extracting your file, you should change all instances of my callsigns to your callsign. Here is how to do that:
- cat "the_file" | sed -e 's/KA1FSB/<your_callsign>/g' > "the_file.copy"
... or ...
- cat autoexec.nos | sed -e 's/KA1FSB/AA1AA/g' > autoexec.nos.copy
Now you will have a new file with your callsigns in place. You must eventually copy the new file back over the old one. But, it is sometimes a good idea to finish your edits and modifications in the "copy" file before overwriting the original.- Using the vi editor
You may also use the vi editor to replace all former callsigns with your callsign. First make a copy or backup of the original file and then edit the copy. Start up vi and from its colon (:) prompt issue this command:
- :1,$s/old_item/new_item/g
Where old item is probably my callsign and new item is yours. The line tells vi to replace all lines beginning at line one through to the end of the text, also replacing multiple "targets" in any given single line. Then use "x" to quit and save, or "w" to just save.- A List of Available Files and Software
Each file below is "mailable" by clicking on the title of the document. This will open your mailer with the subject line containing its name in a format that my procmail auto-responder will recognize. Click on the "send" button and the request will be sent back to the file server here. Currently, there are 21 files available.
- Makefile.txt
This is the Makefile which runs the compile for JNOS. I have included it here for printing purposes. You should really use(edit) the file that came with your distribution since the tabs may become mangled when sent through mailers.
- TraceBot
A suite of programs comprising Perl robots among other config files that opens a socket to the Trace Server on JNOS and then opens a socket to the Convers Server. It reads from the first and writes to the second.
- abscopy.plx
A filter program in Perl which copies data from the Trace Server and writes it to a file.
- autoexec.nos
This is the master runtime configuration file which supplies the JNOS application with a complete listing of instructions. This is a partial file which calls out to various other files. Those other files are included in this listing...
- ax25d.conf
This manages all the incoming requests for the AX25 Utilities. It directs inputs to sub-applications via interfaces.
- axports
The master ports configuration file for the AX25 Utilities. This is an essential file and where you begin configuring the interfaces.
- config.txt
This is the config file for the JNOS compile. The Makefile and "make" need this file to build the working binary for JNOS. It is called config.txt here so that it will not conflict with any other configs, such as config.h or config.unix, etc. Eventually you need to rename or copy this into config.h.
- do_ax25
A large install script for setting up the AX25 Utilities. This manages the start up routines to get the utilities up and running.
- do_beacon
A very simple script for setting up a beacon for the AX25 Utilities. It could serve as a "model" for other low level scripts...
- do_convers
A set up script for getting the convers going on JNOS. This sets the links for the ping-pong conver server, not the internal convers on JNOS.
- do_hf
Configuration data for setting up the HF radio port using the interface hf. This is for a JNOS port.
- do_kisskam
Simple script for the KAM TNC.
- do_kissparms
A shell script to adjust the radio parameters on various AX25 devices.
- do_netrom
Sets up the parameters for netrom on JNOS.
- do_pk-kw
A special script to put the PK-232 into kiss mode...
- do_screen
Determines the way the screen behaves on JNOS.
- do_slips
A Linux shell script to set up the IP configs and routing for the link into JNOS using the sl0 interface.
- do_vhf
A sample stand-alone JNOS script for setting up a vhf interface. You might want to refer to this as a guide or edit it to suit your needs...
- node.conf
A configuration data file for the LinuxNode. The "node" is the user front-end or BBS for the AX25 Utilities. It manages the number of facilities that the user can access and run...
- scripts
This is a "grab bag" assortment of various scripts that are the extentions to the autoexec.nos file. They are bundled here for ease of sending, but they are all available individually too.
- startnos
A shell script to start up the JNOS server.
- The Mail Panel
The mail panel is frequently displayed at the end of a page where you may request a text document or distribution (code package) by mail. It lists the requirements that must be met in order for the "mailto:" command to work. It also warns about the possible "pitfalls" of code transfers by mail and the probable wait time until delivery. In most cases, this panel will be displayed, but it may also just be referred to, a link to here. (So this is a glossary item in disguise... :)
The "excuses" are my excuses for why this might not work... Not your excuses for delaying the "download." :)
If your mailer doesn't like the embeded commands, then you may have to fill it in manually. Most mailers will respond OK, but some do not accept long character-embeded strings in the "mailto:" command. I am trying to make this easy, but sometimes even the best plans become spoiled...
Mail Document Request for: Some Document or Code Package
A Few Caveats:
- Be sure your local mailer is properly "hooked" into your browser.
- Allow up to 24 hours for delivery, although 3-6 is typical...
- Mailed copy, being the latest "on-line" version, may differ slightly from above.
- Click on "Mail it to me" below to activate your mailer, then send from there.
- Please don't change the subject field. (Additional text body comments OK.)
- Sometimes server is down for extended periods of time... (1-10+ days)
- (You obtain, modify and run all data/code at your own risk.)
Enough "excuses," just Mail it to me!
- If your browser-linked mailer doesn't seem to respond, you may send a
null-bodied email to ka1fsb@att.net with a subject of"Code Request - some-document" not including the quotes... (Some browsers and their mail agents do not like excessive string data in the mailto format.)
(Courtesy KBNorton Computer Services)