<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Dear IMC Tech people,<br>
<br>
I'm sorry to bother you again, but am wondering if you can help with
this, or if I can, or both.<br>
<br>
Having read last month that Yahoo's DMARC mail trust settings were
breaking mailing lists including the IETF's own -<br>
<a
href="http://www.ietf.org/mail-archive/web/ietf/current/msg87153.html">http://www.ietf.org/mail-archive/web/ietf/current/msg87153.html</a><br>
... I wondered why it wasn't happening here. Well, it is.<br>
<br>
The effect is that, when a Yahoo user writes to an IMC mailing list
which has other Yahoo users as non-digest recipients, all of them -
sender and receivers - get bounce messages. The receivers get
fatal bounces which immediately suspend them from the list. This
is happening now.<br>
<br>
There are workarounds for this in the latest version of Mailman,
2.1.18, released just this last weekend --<br>
<br>
release notes here:<br>
<a
href="https://mail.python.org/pipermail/mailman-users/2014-May/076787.html">https://mail.python.org/pipermail/mailman-users/2014-May/076787.html</a><br>
<br>
including this:<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<pre> [...] a new Privacy options -> Sender filters -> dmarc_moderation_action
feature which applies to list messages where the From: address is in a
domain which publishes a DMARC policy of reject or possibly quarantine.
This is a list setting with values of Accept, Wrap Message, Munge From, Reject or Discard.
There is a new DEFAULT_DMARC_MODERATION_ACTION configuration setting to set the
default for this, and the list admin UI is not able to set an action
which is 'less' than the default. </pre>
What would it take to get Mailman 2.1.18 on the chambana.net mailing
list server?<br>
</body>
</html>