Known/suspected bugs/Missing Features on current Zmailer sources

- Should use GNU Autoconfig to figure system facilities

- Manuals leave a lot to desire.. Especially a good users/administrators
  manual is in need

- Makefiles require a serious overhaul..
  ( -> GNU Autoconfig )

- Security expects "NOBODY" with value "-2", no other can be used!
  (Hmm..  It appears some others may work as well, why I didn't
   succeed with others ? /mea)

- MIME facilities are half-cooked (but work for the most of the time)

- Transporters should propably be able to down- AND upconvert
  headers (and bodies) when it comes to MIME-headers..
  For example it may be better to feed QP-decoded in 8-bit smtp
  to a server claiming it can receive 8BITMIME, even though it
  doesn't implement the thing in a truly kosher way..
  (One email->news gateway machine comes to mind..)
  This dual-translation applies to   smtp,  and  sm.  Just 8-bit
  decode applies to  mailbox, and errormail

- "error" -channel uses MIMEoid message wrapping, and should consider
  seriously (let user to configure) what to "Cc:" to postmaster.
  Some say the Postmaster should not get error message's body..
  (Error channel appears partly inside(!)  the codes of  'router'
  (in the rfc822.c), and 'scheduler' (in the msgerror.c), and partly
  as an external program  transports/errormail/errormail.c)

  IETF has a NOTARY-wg whose charter is to standardize Delivery Status
  Notification reporting.   For a copy of specs drafts, see:
		doc/draft-ietf-notary-*
  On  940829  the system has IETF-NOTARY support on SMTP, MAILBOX, and
  ERRORMAIL channels.  Others (SM, HOLD?) will follow someday...

  Finetunings are needed on returned codes. ALPHA quality ?
  (router/rfc822.c DOES NOT (yet) follow IETF-NOTARY format!)

  NOTARY demands, that "Rcpt:" entry on the returned message MUST
  contain FQDN address.  Plain userid is not enough..  (BUG!)

- Configuration files, esp.   cf/aliases.cf   has controversy in it.
  Many people think it is broken (I tend to agree) - 940614/mea

- Canned error messages are abysmal -- they need more complete ways to
  configure what is told and how, whole error facility needs an overhaul
  in fact..  (See mention above about: IETF NOTARY)

- Sometimes incoming SMTP can be a hellish load, need to introduce
  a load-limited incoming SMTP acceptor (smtpserver/smtpserver.c)

  (Rayan wrote it, but never released it..)

- Alias processing by "newaliases" (printaliases: run_praliases)
  is "interesting" -- if sysadm wants to add an alias like:
	"Example Name": realname
  That just doesn't work..

- Processing of several headers is questionable/lack of:
	Date:	-- should not alter the string content, even though
		   it parses it..  (So, it should not throw away
		   that text..)
		(940906 -- now the original one is used.)

	From: <>  -- should be valid! --- now is (940626/mea)
	Return-Path: <> -- as well ?
		
	Generic: header wrapping within N chars (like to 80-chars
		 space of BITNET) and also infinite wide systems,
		 like News.. (transports/libta/writeheaders.c ?)

	Generic: RFC-1342 aka. non-US-ASCII chars in the headers..
		 Auto-conversion and wrapping

- Scheduler apparently can loose its mind -- if a hold-channel
  entry keeps failing (at first), and then succeeds, scheduler
  (at the moment) doesn't recognize the situation!
  Restart of the scheduler fixes that, but is not elegant..

- Zmailer script-language, Zsh, could benefit from internal
  (simplified) version of  /bin/expr:
	a=$(/bin/expr "$home" : "\(/.*\)//*[^/]*/*") || return 99
