2.99.50s18 out

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

Ok, I did today actually 3 tries at cutting the ZMailer 2.99.50s18 out..

First of all, smtpserver's 'DATA' command crashing at 2.99.50s17 was bad :-(
But I wasn't at all happy with some other things either.  ChangeLog below.

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


1999-05-14  Matti Aarnio  <mea@mea.tmt.tele.fi>

	* VERSION 2.99.50s18

	* smtpserver/smtpdata.c:
	    BASE64 encoding of 7 chars long name yields a BASE64 string
	    with two '=' chars, that was considered bad by the decoder..
	    ( I think there should be only one '=' char, but Netscape
	      Communicator 4.51 does it that way :-(  )

	* router/functions.c:
	    Old (very old!) 'old-vs-new' scheduler locking scheme
	    causes problem at Solaris 2.6. Peter IP (Toronto) got
	    ZMailer router process pids 6/7/8/9, which the router
	    treated somewhat poorly..

	* configure.in:
	    Autosense OpenSSL at default location, if not otherwise defines.

1999-05-13  Matti Aarnio  <mea@mea.tmt.tele.fi>

	* router/router.c:
	    Move  openlog()  a couple lines down so that also interactive
	    routers will use it.

	* router/rfc822.c:
	    Change the Received: header 'id' information to be the same
	    which syslog() uses, and which is reported at the smtpserver.
	    Eases looking for message spoolids at syslog outputs.

	* transports/smtp/smtp.c:
	    Overhauled error processing in various situations, now an
	    EX_TEMPFAIL condition will use next MX server (if one is
	    available) very much independent of where along the code
	    the problem occurred.   Originally a problem in e.g. connection
	    setup until EHLO/HELO probe was retryable to an MX, but now
	    a much latter problem phase (DATA + . yielding 4** code,
	    for example) can do the same.
	
	    Latter continued the theme with logging of the smtp client session
	    to one client with weird looking problem:  Ah, finally some clue
	    on the PIPELINING problem; smtp_sync() ignored (or treated poorly)
	    certain way how EXIM responds when it has disk full.  We missed
	    the initial MAIL FROM-> 4** code, and errored with the latter
	    "503 No sender yet given"... D'uh..  (Likely this was entirely
	    ZMailer problem, but was it only introduced yesterday, or has it
	    been lurking there all along with PIPELING, and never spotted
	    before ??)  It manifested as never accumulating queue to sites
	    using PIPELINING, and behaving like above..

	* smtpserver/smtpserver.h, smtpserver/cfgread.c,
	  smtpserver/smtpserver.c, smtpserver/smtptls.c,
	  smtpserver/smtpsmds.c, proto/smtpserver.conf.in:
	    Much work again, now to parametrize ways of selectively adding
	    pieces of "Received:" header contained commentary information.
	    Features: ident, whoson, auth-username, tls-cipher, tls-client-cert
	    Added also:  "PARAM AUTH-LOGIN-also-without-TLS" which allows
	    paintext "AUTH LOGIN" to be used without successfull STARTTLS.

1999-05-12  Matti Aarnio  <mea@mea.tmt.tele.fi>

	* smtpserver/smtpserver.c:
	    Fix introduced accidental NULL referral.

	* SiteConfig.in:
	    Partially undo previous change to SiteConfig.in;
	    let the  FORCEPUNT  to be there...

	* scheduler/scheduler.c, scheduler/update.c:
	    Fixed the 'stored recipient count' gauge leakage.