<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 15/12/2011 8:51 AM, clare johnstone wrote:
<blockquote
cite="mid:CAAoJK++0o0=yYyVjNPvqea-pgjSyyHtwQ_Eb6jPrv7cBXkH+-w@mail.gmail.com"
type="cite">
<pre wrap="">It was a bit confusing; Perhaps the error should refer to a
"non-subscriber to the list" rather than "non-member".</pre>
</blockquote>
Indeed, this is the issue. <br>
<br>
This is <i>Mailman</i>'s default wording and has nothing to do with
membership of the association. PLUG's mailing lists are generally
open for anyone to subscribe to and un-subscribe from at will. As
many will be aware, the <i>Mailman </i>software PLUG uses is a
self-service subscribe/un-subscribe, which can be accessed via
email, or on the web at <a class="moz-txt-link-freetext" href="http://lists.plug.org.au/mailman/listinfo/">http://lists.plug.org.au/mailman/listinfo/</a>.
Further details on PLUG's mailing lists are at
<a class="moz-txt-link-freetext" href="http://www.plug.org.au/resources/mailing-list">http://www.plug.org.au/resources/mailing-list</a>.<br>
<br>
In this case Arie was subscribed to the mailing list in question
from an old email address and posted to this list from a separate
email address, which added to the confusion. <i>Mailman </i>cannot
associate two separate email addresses as being the same person, so
identifies the new address as a non-subscriber (<i>non-member of the
<b>list</b></i>). I have explained and offered (<i>off list</i>)
to update the mailing list subscription details for him if he is
unable to do so through the self-service interfaces offered, and I
await Arie's acceptance of my offer (I don't generally believe we
should change someone's subscriptions without their consent).<br>
<br>
<br>
<br>
<b>Details for the interested</b><br>
While the template reply is customisable, it has a variable for the
"reason" a message was held, and that appears this is not easily
customisable (the template is used for many bounce options). It is
this "reason" field that has caused the confusion:<br>
<blockquote><tt>/usr/lib/mailman/Mailman/Handlers/Hold.py: reason
= _('Post by non-member to a members-only list')</tt><br>
</blockquote>
... and I suspect that if we were to change this reason text it
would either break some of mailman's internationalization lookups
(not that we need them, so this is minor). It uses PO files, which
use the original English text string as a key to lookup
translations, such as this French translation from the
fr/LC_MESSAGES/mailman.po file:<br>
<blockquote><tt>#: Mailman/Handlers/Hold.py:61</tt><br>
<tt>msgid "Post by non-member to a members-only list"</tt><br>
<tt>msgstr "Envoi par un non-abonn<E9> sur une liste
reserv<E9>e aux abonn<E9>s"</tt><br>
</blockquote>
<br>
There is no en/LC_MESSAGES/mailman.po to translate the English
into... English in mailman's current set up (shame, as we could
possibly do with an <i>en_AU</i> locale).<br>
<br>
However, the next security update or package upgrade would overwrite
this change, as this message is not designed to be customised
(clearly doing so could invalidate the lookup of translations).<br>
<br>
<br>
James<br>
<div class="moz-signature">-- <br>
<em>Mobile:</em> +61 422 166 708, <em>Email:</em>
james_AT_rcpt.to<br>
PLUG President 2011: <a href="http//www.plug.org.au">http://www.plug.org.au</a></div>
</body>
</html>