Update to alpha release 19990221.

AUTHORS

@@ -0,0 +1 @@
+Edward S. Marshall <emarshal@logic.net>

docs/CHANGES → ChangeLog

@@ -1,3 +1,16 @@
+Changes since 1.4:
+
+- Converted to automake/autoconf for configuration, which should make
+  it easier to extend portability.
+
+- Added support for checking multiple addresses in one invokation.
+
+- Added support for reading addresses to check from standard input, by
+  specifying an argument of '-'.
+
+- Changed rbl.dorkslayers.com to relays.orbs.org, due to a change in
+  management.
+
 Changes since 1.3:
 
 - Fixed output bug with some odd combinations of -q and -t.

INSTALL

@@ -0,0 +1,185 @@
+(For installation instructions which are specific to rblcheck, please
+see "docs/INSTALL".)
+
+Basic Installation
+==================
+
+   These are generic installation instructions.
+
+   The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation.  It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions.  Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, a file
+`config.cache' that saves the results of its tests to speed up
+reconfiguring, and a file `config.log' containing compiler output
+(useful mainly for debugging `configure').
+
+   If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release.  If at some point `config.cache'
+contains results you don't want to keep, you may remove or edit it.
+
+   The file `configure.in' is used to create `configure' by a program
+called `autoconf'.  You only need `configure.in' if you want to change
+it or regenerate `configure' using a newer version of `autoconf'.
+
+The simplest way to compile this package is:
+
+  1. `cd' to the directory containing the package's source code and type
+     `./configure' to configure the package for your system.  If you're
+     using `csh' on an old version of System V, you might need to type
+     `sh ./configure' instead to prevent `csh' from trying to execute
+     `configure' itself.
+
+     Running `configure' takes awhile.  While running, it prints some
+     messages telling which features it is checking for.
+
+  2. Type `make' to compile the package.
+
+  3. Optionally, type `make check' to run any self-tests that come with
+     the package.
+
+  4. Type `make install' to install the programs and any data files and
+     documentation.
+
+  5. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  To also remove the
+     files that `configure' created (so you can compile the package for
+     a different kind of computer), type `make distclean'.  There is
+     also a `make maintainer-clean' target, but that is intended mainly
+     for the package's developers.  If you use it, you may have to get
+     all sorts of other programs in order to regenerate files that came
+     with the distribution.
+
+Compilers and Options
+=====================
+
+   Some systems require unusual options for compilation or linking that
+the `configure' script does not know about.  You can give `configure'
+initial values for variables by setting them in the environment.  Using
+a Bourne-compatible shell, you can do that on the command line like
+this:
+     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
+
+Or on systems that have the `env' program, you can do it like this:
+     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
+
+Compiling For Multiple Architectures
+====================================
+
+   You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory.  To do this, you must use a version of `make' that
+supports the `VPATH' variable, such as GNU `make'.  `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script.  `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.
+
+   If you have to use a `make' that does not supports the `VPATH'
+variable, you have to compile the package for one architecture at a time
+in the source code directory.  After you have installed the package for
+one architecture, use `make distclean' before reconfiguring for another
+architecture.
+
+Installation Names
+==================
+
+   By default, `make install' will install the package's files in
+`/usr/local/bin', `/usr/local/man', etc.  You can specify an
+installation prefix other than `/usr/local' by giving `configure' the
+option `--prefix=PATH'.
+
+   You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files.  If you
+give `configure' the option `--exec-prefix=PATH', the package will use
+PATH as the prefix for installing programs and libraries.
+Documentation and other data files will still use the regular prefix.
+
+   In addition, if you use an unusual directory layout you can give
+options like `--bindir=PATH' to specify different values for particular
+kinds of files.  Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.
+
+   If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+Optional Features
+=================
+
+   Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System).  The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+   For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+Specifying the System Type
+==========================
+
+   There may be some features `configure' can not figure out
+automatically, but needs to determine by the type of host the package
+will run on.  Usually `configure' can figure that out, but if it prints
+a message saying it can not guess the host type, give it the
+`--host=TYPE' option.  TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name with three fields:
+     CPU-COMPANY-SYSTEM
+
+See the file `config.sub' for the possible values of each field.  If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the host type.
+
+   If you are building compiler tools for cross-compiling, you can also
+use the `--target=TYPE' option to select the type of system they will
+produce code for and the `--build=TYPE' option to select the type of
+system on which you are compiling the package.
+
+Sharing Defaults
+================
+
+   If you want to set default values for `configure' scripts to share,
+you can create a site shell script called `config.site' that gives
+default values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists.  Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Operation Controls
+==================
+
+   `configure' recognizes the following options to control how it
+operates.
+
+`--cache-file=FILE'
+     Use and save the results of the tests in FILE instead of
+     `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
+     debugging `configure'.
+
+`--help'
+     Print a summary of the options to `configure', and exit.
+
+`--quiet'
+`--silent'
+`-q'
+     Do not print messages saying which checks are being made.  To
+     suppress all normal output, redirect it to `/dev/null' (any error
+     messages will still be shown).
+
+`--srcdir=DIR'
+     Look for the package's source code in directory DIR.  Usually
+     `configure' can determine that directory automatically.
+
+`--version'
+     Print the version of Autoconf used to generate the `configure'
+     script, and exit.
+
+`configure' also accepts some other, not widely useful, options.

Makefile.am

@@ -0,0 +1,44 @@
+## Process this file with automake to produce Makefile.in
+
+AUTOMAKE_OPTIONS = 1.4
+
+SUBDIRS = .
+
+bin_PROGRAMS = rblcheck
+rblcheck_SOURCES = rblcheck.c
+
+EXTRA_DIST = \
+	README.ALPHA			\
+	sites.h				\
+	config/install-sh		\
+	config/missing			\
+	config/mkinstalldirs		\
+	docs/BUGS			\
+	docs/CREDITS			\
+	docs/INSTALL			\
+	docs/NOT-TODO			\
+	docs/PLATFORMS			\
+	docs/TODO			\
+	utils/README			\
+	utils/test_origip.sh		\
+	utils/test_rblcheck.sh		\
+	utils/dns/Makefile		\
+	utils/dns/dump.c		\
+	utils/qmail/Makefile		\
+	utils/qmail/origip.awk		\
+	utils/qmail/origip.c		\
+	utils/sendmail/origip.pl
+
+.PHONY: files release sanity snapshot
+
+files:
+	@files=`ls $(DISTFILES) 2> /dev/null `; for p in $$files; do \
+	  echo $$p; \
+	done
+
+release:
+	rm -rf .deps */.deps
+	$(MAKE) distcheck
+
+snapshot:
+	$(MAKE) dist distdir=$(PACKAGE)-`date +"%y%m%d"`

NEWS

@@ -0,0 +1,12 @@
+Changes since 1.4:
+
+- Converted to automake/autoconf for configuration, which should make
+  it easier to extend portability.
+
+- Added support for checking multiple addresses in one invokation.
+
+- Added support for reading addresses to check from standard input, by
+  specifying an argument of '-'.
+
+- Changed rbl.dorkslayers.com to relays.orbs.org, due to a change in
+  management.

README

@@ -1,4 +1,4 @@
-rblcheck 1.4 - Command-line interface to Paul Vixie's RBL filter.
+rblcheck 1.5 - Command-line interface to RBL-style filters.
 Copyright (C) 1997, Edward S. Marshall <emarshal@logic.net>
 
 This program is free software; you can redistribute it and/or modify
@@ -15,13 +15,9 @@ You should have received a copy of the GNU General Public License
 along with this program; if not, write to the Free Software
 Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
 
---
+-------------------------------------------------------------------------------
 
-$Id$
-
---
-
-This program is a very basic interface to DNS filters such as the RBL
+This program is a very basic interface to DNS listings such as the RBL
 filter developed by Paul Vixie and the MAPS project. The basic idea of the
 filter is that when someone is blacklisted for email abuse of some sort, a
 new domain name is resolved of the form "2.0.0.127.domain.name.com", where
@@ -30,19 +26,26 @@ would be the IP address 127.0.0.2), and "domain.name.com" is the base
 domain name of the filtering service (such as "rbl.maps.vix.com", for the
 MAPS project RBL filter).
 
-For information on compiling this program, see the file docs/INSTALL.
+For information on compiling this program, see the file docs/INSTALL. For
+generic information on using the supplied "configure" script, see the file
+INSTALL.
 
 This program has only been tested by the author under Linux 2.x, Solaris
 2.5.1, and Solaris 2.6, but there's no reason it shouldn't work on another
 platform, as long as a working resolver library exists (the one from BIND
 will do perfectly).
 
-For more information about RBL-style blacklists, please take a look at
-http://maps.vix.com/rbl/ and http://www.dorkslayers.com/ . For more
-information about BIND, drop by http://www.isc.org/bind.html . The
-official home for rblcheck is http://www.xnet.com/~emarshal/rblcheck/ .
+For more information about RBL-style blacklists, please see the "sites.h"
+file, which contains pointers to several RBL-alike listings.
+
+For more information about BIND, drop by http://www.isc.org/bind.html .
+
+The official home for rblcheck is http://www.xnet.com/~emarshal/rblcheck/ .
+
+Any ideas, bugfixes, porting notes, or requests for pizza delivery
+directions should be sent to me at "emarshal@logic.net". Don't bug the
+RBL service operators about it, since they didn't write it, and probably
+wouldn't like doing technical support for it.
 
-Any ideas, bugfixes, or porting notes should be sent to me at
-"emarshal@logic.net". Don't bug the MAPS or Dorkslayers people about this;
-they didn't write it, and probably woudn't like getting a bunch of mail
-about it.
+-- 
+Edward S. Marshall <emarshal@logic.net>