Log Message:
Update to 1.1.9 (approved by kim@). From the changelog:

* New feature courtesy of Mark Horn. ACTION_EXPIRED_DATED has been
  extended to support handling multiple ages of dated messages. So you
  could for example 'bounce' mail to dated addresses that have been
  expired for more than a week, 'hold' if longer than a month, and
  'drop' if over a year, while still setting the default behavior to
  'confirm'.  For more information and an illustrative example, see
  http://wiki.tmda.net/ConfigurationVariables#ACTION_EXPIRED_DATED

* TMDA's internal copy of the Python email package has been upgraded
  to v4.0.1.

* The bin/tmda-* programs have been revamped to use Python's new
  'optparse' library.

* TMDA can now optionally store unconfirmed messages in a "Maildir"
  rather than in TMDA's custom pending queue format.  This allows you
  to use any mail reading program that supports Maildir to browse or
  search your pending queue, rather than the 'tmda-pending' and
  'tmda-cgi' programs, though the latter will still work.

* tmda-filter has a new command-line option, '-e/--environ' which you
  can use to add a VAR=value pair to the environment.  One example use
  of this is to allow TMDA to be setup as a Postfix transport.
  Contributed by Bernard Johnson.

* tmda-filter will defer incoming deliveries if the sticky bit is set
  on your home directory (as determined by the $HOME variable).  This
  allows you to safely edit the contents of ~/.tmda/ on a live system
  if you need to.

* tmda-ofmipd now has "one-session" mode through the '--one-session'
  command-line option, courtesy of Stephen Warren.  This allows you to
  use xinetd or tcpserver, possibly in conjunction with stunnel, to
  spawn tmda-ofmipd, rather than having tmda-ofmipd bind to a port and
  accept connections on its own.

* The new 'dot-tmda' directory in contrib contains a working ~/.tmda/
  structure that can be used with only a few changes.  See the README
  in that directory for more info.  Not documented yet outside of the
  README, but this might help new TMDA users get started quicker.

* Some of the tmda-* programs will now run on native win32
  (tmda-address, tmda-check-address, tmda-pending, and tmda-keygen).

* tmda-ofmipd has a new option (--pure-proxy) that can proxy mail for
  non-TMDA users in addition to TMDA users.  This might be useful if
  you run a mixed environment, and want to use tmda-ofmipd for
  everyone.  See `tmda-ofmipd --help' for more on this option.

* New feature from David Bremner.  Add 'shell=' and 'python=' tag
  actions to the outgoing filter.  This allows you to add
  dynamic/shell escaped headers from the outgoing filter file.  For
  example usage, see the TMDA/Hashcash HOWTO I've prepared at
  http://wiki.tmda.net/TmdaHashCashHowto

* The template system has been reorganized to simplify things for
  users of multi-lingual templates among others.  See
  http://wiki.tmda.net/TemplateHowto and the UPGRADE notes below.

* Messages are now simply deleted from your pending queue once they
  are confirmed or released rather than being renamed with a '3,C' or
  '3,R' suffix.  This provides simpler, more intuitive behavior and
  decreased storage requirements.

* Fixed a bug in TMDAINJECT that caused Message-ID and Date headers to
  differ when sending to multiple recipients.

* Fixes to the tmda.spec file that should allow RPMs to be built with
  Python 2.3.x.

* Tilde expansion is now done automatically for variables in
  /etc/tmdarc and ~/.tmda/config, so you no longer have to use
  os.path.expanduser() to do this yourself.  e.g,

  TEMPLATE_DIR = "~/.tmda/templates"

  now ``just works''.

* New 'whitelist' behavior for tmda-pending and tmda-cgi, controlled
  by http://wiki.tmda.net/ConfigurationVariables#PENDING_WHITELIST_RELEASE

* A new 'pipe-headers' incoming filter file source.  Identical to
  'pipe' except that it only pipes the headers to the program, instead
  of the headers + body.  This should offer greater performance and
  reliability when processing the message body isn't required.

* A new feature to add Mail-Followup-To headers from tmda-sendmail or
  tmda-ofmipd to messages.  See
  http://wiki.tmda.net/ConfigurationVariables#MAIL_FOLLOWUP_TO