<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
If you got no list email since the 20th check the bottom of this
archive page starting with Christopher Svec's msg just above my msg
mentioning a "big hammer" : <a
href="http://mail.triembed.org/pipermail/triembed_triembed.org/2015-April/date.html">http://mail.triembed.org/pipermail/triembed_triembed.org/2015-April/date.html</a><br>
<br>
-Pete<br>
<br>
PS In case anybody cares, the GNU Mailman "general option" change
was this one:<br>
"
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<span style="color: rgb(0, 0, 0); font-family: 'Times New Roman';
font-size: medium; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height: normal;
orphans: auto; text-align: -webkit-right; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline
!important; float: none; background-color: rgb(221, 221, 221);"><font
face="sans-serif">Replace the From: header address with the
list's posting address to mitigate issues stemming from the
original From: domain's DMARC or similar policies." changed from
default to "munge from" (The TriEmbed list runs on Mailman
version 2.1.18-1)<br>
<br>
PPS I can't begin to understand the god-awful pile of
mis-represented binary that got into that "big hammer" msg I
sent. I thought I was sending a very small graphic file showing
the Mailman admin's view of the specific change described above.
Oh well.</font> <br>
</span><br>
</body>
</html>