mailman-2.1.12-25.AXS4

Mailman is software to help manage email discussion lists, much like
Majordomo and Smartmail. Unlike most similar products, Mailman gives
each mailing list a webpage, and allows users to subscribe,
unsubscribe, etc. over the Web. Even the list manager can administer
his or her list entirely from the Web. Mailman also integrates most
things people want to do with mailing lists, including archiving, mail
<-> news gateways, and so on.

Security issues fixed with this release:

CVE-2002-0389
CVE-2015-2775

Fixed bugs:

* Previously, it was impossible to configure Mailman in a way that Domain-based
Message Authentication, Reporting & Conformance (DMARC) would recognize
Sender alignment for Domain Key Identified Mail (DKIM) signatures. Consequently,
Mailman list subscribers that belonged to a mail server with a "reject" policy
for DMARC, such as yahoo.com or AOL.com, were unable to receive Mailman
forwarded messages from senders residing in any domain that provided DKIM
signatures. With this update, the bug was fixed.
* Mailman used a console encoding when generating a subject for a "welcome
email" when new mailing lists were created by the "newlist" command.
Consequently, when the console encoding did not match the encoding used by
Mailman for that particular language, characters in the "welcome email" could be
displayed incorrectly. With this update, the problem was fixed.
* The "rmlist" command used a hardcoded path to list data based on the
VAR_PREFIX configuration variable. As a consequence, when the list was created
outside of VAR_PREFIX, it was impossible to remove it using the "rmlist"
command. With this update, this bug was fixed.
* Due to an incompatibility between Python and Mailman in Asianux Server 4,
when moderators were approving a moderated message to a mailing list
and checked the "Preserve messages for the site administrator" checkbox, Mailman
failed to approve the message and returned an error. This incompatibility has
been fixed with this update.
* When Mailman was set to not archive a list but the archive was not set to
private, attachments sent to that list were placed in a public archive.
Consequently, users of Mailman web interface could list private attachments
because httpd configuration of public archive directory allows listing all files
in the archive directory. The httpd configuration of Mailman has been fixed in
this update.