"BUGS", or rather: "Open Issues" on the ZMailer-3.0 scheduler:

- When activating idle processors, should attempt to use
  transporter with SAME target host as last time  (so the
  SMTP-transporter can keep a sort of connection cache...)

- Should implement "idlemin=", which per default is 0, and
  when set would force a minimun wait before the process
  were taken from the idle pool to anything but the task
  it was doing last. (Keeping SMTP connection caches around..)

- Does the thread (re)scheduling work as it should ?
	- Esp. when a thread-ring has more threads, than it
	  can have transport processes, it may be overactive
	  to try to start threads (to be checked)
  Propably it doesn't, have to investigate..

- IETF NOTARY-WG error reports
