

		Changes to QuickPage from v3.1 to v3.2
		---------------------------------------

	- The QuickPage source is totally lint free (at least when
	  compiled on Solaris 2.x systems).

	- An ANSI compiler (such as gcc) is now required for building
	  QuickPage.  I really didn't want to do this, but one of my
	  goals was to make QuickPage "lint free" and I just couldn't
	  do that with varargs without making the function declarations
	  ANSI compliant.  I apologize for any hardships this may cause.
	  However, I suspect most people are using ANSI compilers anyway,
	  this hopefully won't be much of a problem.

	- The long awaited "e-mail status notification" is here.  Pages
	  submitted with a high priority (i.e. level 0) cause e-mail to
	  be sent to the submitter whenever a page succeeds or fails.

	- A new keyword ("administrator") can be used in the configuration
	  file to notify the QuickPage administrator of failed pages.

	- Page groups are now supported.  A new keyword ("group") can
	  be used in the configuration file to specify page groups.
	  Group members can have optional duty schedules so they won't
	  be paged unless they're on duty.

	- A new -P option like was added which works exactly like the
	  existing -p option, with the exception that any -a, -c, and -l
	  options are not reset to their default values.

	- A bug in previous versions of QuickPage required the "password"
	  keyword in a service specification to start with "1" in order
	  to comply with the IXO/TAP protocol specification.  This typo
	  has been fixed and a service password is no longer required.
	  Any "password=1" entries in qpage.cf should be removed unless
	  you know for a fact your service requires them.

	- Pages now have unique message IDs which can be used to track
	  status via syslog messages.

	- The -d flag now keeps the daemon in the foreground and prints
	  messages to stderr instead of logging them via syslog().

	- Using the -i flag as root now prints a warning message telling
	  the user that daemon mode may behave differently since it doesn't
	  run as root.

	- A new -Q flag can be used on the QuickPage server to list all
	  pages currently in the page queue.

	- Queue files now contain the submitter's hostname.

	- A "client only" version is now supported which should compile
	  on just about every platform.

	- Previously, if a page to multiple recipients failed for one
	  recipient, everyone would get a another copy on successive
	  retries.  This has been fixed.

	- The "goodtries" counter was written to the queue file correctly
	  but it was ignored when the file was read.  This caused pages to
	  be retried forever, regardless of the "maxtries" setting in the
	  configuration file.  This has been fixed.

	- It is no longer a fatal error for the client if the SNPP server
	  refuses to accept CALLerid information.

	- Use 8-bit bytes if not using parity.

	- Service names are included in log messages.

	- The QuickPage source code is now more compatible with other
	  operating systems.

	- The code which parses e-mail messages (the -m option) is now
	  more robust.

	- The SEND command now performs a RESEt before returning.

	- The LEVEl command now returns a valid response code.


		Changes to QuickPage from v3.0 to v3.1
		---------------------------------------

	- A new -m option tells the client to read an e-mail message
	  from standard input.  Apparently lots of people wanted this
	  even though it goes against the intent of RFC-1861.

	- Multiple SNPP servers are permitted for redundancy.

	- The argument to the -a option can now be specified either as
	  YYMMDDHHMMSS or by using the previous syntax.

	- The time specified by the HOLDuntil command is now computed
	  correctly when a timezone is supplied.

	- Some of the messages returned by the SNPP server are now
	  slightly more intuitive.

	- Whitespace in the CALLerid argument is now preserved.

	- Pages longer than 1024 bytes are now handled correctly.
