autoSend is a neat little utility I cooked up to do automatic
    runs of xmitBin on a periodic basis (I usually run autoSend as a
    cron job).  It allows you to "batch up" things to get sent out.  I've
    found it particularly useful when mailing patch parts of postings to
    people or doing daily posts to my favorite newsgroup.  Since I run it
    from cron, all I have to do is make sure the data is ready, and 
    autoSend can do its thing at a good time when my system/network load
    is low (like in the wee hours of the morning, for example).
	autoSend requires xmitBin, of course.  It also requires a data
    input file "autoSend.dat" to reside in the data directory defined in 
    the autoSend script ("datDir").  The supporting awk scripts (mkList.awk
    and doList.awk) should be available in the binary directory, also
    defined in the autoSend script ("binDir").
	The format of the data file can take one of two forms - either

  	<destination> <file> FULL|<patchParts> <other_xmitBin_options>

				...or...

  	*LIST* <destination> <number_to_send> <other_xmitBin_options>

	In the case of the first form, either the complete file (if "FULL" 
    is used) or the appropriate parts of the specified <file> will be sent 
    to the specified <destination>.  A couple of examples of these type of
    lines are as follows:

	deej marlin.jpg FULL -label fish 'Cool picture of a marlin!'
	lucklessUser puzzle.jpg 1,9-11 'Missing puzzle pieces'
	alt.binaries.pictures.misc secret.gif FULL -post -as stealthUser

	The other form gives you a way to collect a whole bunch of things
     to send together and send them out without choking the destination all
     at once.  In this case, you need to have a <destination>.send file in
     the data directory that contains all of the file paths that will be sent 
     (xmitBin options may be specified after the file path as well).  In this
     case, autoSend *always* sends the full file (patch parts are not possible
     when using the *LIST* option).  An example of this type of line is as 
     follows:

	*LIST* alt.binaries.sounds.misc 2 -l train -a alt.binaries.sounds.d

	...and alt.binaries.sounds.misc.send might contain:

	/mySounds/trains/woowoo.au 'Train whistle'
	/mySounds/trains/chugachuga.au 'Train starting out'
	/mySounds/trains/kaboomoo.au 'Train derailment - full cattle cars'
	/mySounds/trains/hisss.au 'Brakes being applied'

	In the example above, the first two files (woowoo.au and 
    chugachuga.au) will be sent the first time that autoSend is run, and the
    second two files (kaboomoo.au and hisss.au) will be sent the next time.
	After autoSend runs, it clears out the appropriate information from
    autoSend.dat and <destination>.send, so that it doesn't get re-sent the
    next time autoSend is run.  The removed information is saved in the data
    directory in the file dataBack.<dateStamp>, in case you need to get it
    back for some reason, or if you want to see what got sent on a particular
    day.
	autoSend always runs xmitBin with the -nc option, so you either have 
    to already have a description in place, or specify the -nd option as one 
    of the <other_xmitBin_options>.  Also, if you use the extra subject
    information option to xmitBin, be sure to include that data in single 
    quotes in both the <destination>.send and autoSend.dat files (as shown in 
    the examples).
	Good luck, and have fun with autoSend!