zmailer-2.99.48.patch3.test released ...

[Matti Aarnio <mea@nic.funet.fi>]

...
> Does this mean another place to patch in the 2.99.48p2 source tree or can
> I ignore this?  I already placed the patch you suggested in your earlier
> e-mail in the 'smtpdata.c' source file and that does solve the problem.
> Right now, because of the reported problems with 2.99.49b6, I am inclined
> to stand pat with 2.99.48p2+.  In fact, IMHO, it would be a good idea to
> put out a 3rd patch for 2.99.48 with the 'smtpdata.c' fix.  Anyway, as
> usual, thanks for the good responce!

	Ok, I made  zmailer-2.99.48.patch3.test  available at
	my workstation ( ftp://mea.tmt.tele.fi/ ).  I did compile
	test it at my workstation both with and without HAVE_MMAP...
	Report on its working, and I will make official release
	by storeing it into  ftp.funet.fi.

	* config.h.in, configure.in, configure:
	    - Pulled these from 2.99.49beta7

	* transports/sm/sm.c, transports/smtp/smtp.c,
	  transports/mailbox/mailbox.c:
	    "readalready" cache handling in case the MMAP is not
	    recognized properly (IBM AIX has problems at the auto-
	    detection of that feature..)

	* smtpserver/smtpserver.c, smtpserver/smtpcmds.c,
	  smtpserver/smtpdata.c:
	    - Wrong parameters in one logging call at the  BDAT  processing,
	    - Rearranged typeflush() calls, and pipeline status reporting.

> Roy
> rcb@press-gopher.uchicago.edu

	/Matti Aarnio <mea@nic.funet.fi>