mailman3: update to 3.3.9

3.3.9

Configuration
* BREAKING CHANGE: logging.http section has now been split into two parts,
  logging.http is for the Mailman internal code and logging.gunicorn is
  for Gunicorn specifically since they have different logging formats.
  This should fix suprious errors with KeyError: t that was often
  confusing for users.
* Python 3.9 is now the minimum supported version of Python.

Bugs fixed
* config.mta.remove_dkim_headers now applies to messages to -owner.
* The master process now robustly detects when runner processes terminate
  and restarts them.
* Setting Postfix transport_file_type: regex without setting something
  for postmap_command: no longer throws an exception.
* When bounce processing disables delivery for a user, the user窶冱 score is
  reset so it will be zero if delivery is enabled.
* The mailman shell command now works and displays the banner with
  use_ipython: yes.
* Bogus Message-ID headers that have been observed in the wild are now fixed.
* Raising StopIteration in a workflow process no longer creates a
  mailman.error log entry.
* The task runner now evicts old, processed bounce events.
* We now require authheaders>=0.15.2.
* Digests no longer contain a bogus Archived-At header.
* Content filtering will no longer add its report to a non-mixed multipart
  message but will wrap the message and add the report to the wrapper.
* The administrivia rule will now decode encoded message bodies.
* Email address validation now accepts quoted local parts and @ in local part.
* The default for max_recipients has been reduced to 10 to avoid possible lost
  mail when a large number of invalid recipients causes the MTA to disconnect.
* Messages preserved or forwarded by content filtering are now the original
  message rather than the content filtered one.
* List welcome and goodbye messages to users with English preferred_language
  now have their Subject: RFC 2047 encoded as needed.
* Bounce processing notifications due to a DSN for multiple users now have
  the DSN attached to each notice.

New Features
* There is a new dmarc_addresses list attribute which is a list of email
  addresses and patterns matching email addresses. If a post is From: an
  address matching one of these, dmarc mitigations will be applied
  regardless of the From: domain窶冱 dmarc policy.


(markd)