<div dir="ltr">I have experience with Mailman, and don't mind pitching in.<font face="yw-b3b03f93acb29dde874548d979c14638352bd06e-7d4f749507d8db5b910a0b87ed2362da--o" style></font><div><br></div><div>j</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Sun, Dec 15, 2013 at 3:44 AM, William Drake <span dir="ltr"><<a href="mailto:wjdrake@gmail.com" target="_blank">wjdrake@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks much Tapani. Is there anyone here who’d have the bandwidth to handle this, or share handling this with someone else?<br>
<br>
Bill<br>
<div class="HOEnZb"><div class="h5"><br>
On Dec 15, 2013, at 8:25 AM, Tapani Tarvainen <<a href="mailto:ncuc@TAPANI.TARVAINEN.INFO">ncuc@TAPANI.TARVAINEN.INFO</a>> wrote:<br>
<br>
> Managing Mailman is perhaps the most important of the e-tasks<br>
> I listed, given how much NCUC work relies on email,<br>
> and it needs attention frequently and often rapid response.<br>
> On the other hand it's also very easy, technically anyone can<br>
> do it, the primary requirement is conscientiousness,<br>
> or reliability if you will.<br>
><br>
> It is also easy to share between several people in many<br>
> ways, but the very least there should be two people who<br>
> can do "everything", or at least one all-purpose admin<br>
> and one moderator. Different lists could have different<br>
> managers, now they're all managed by same people (I and<br>
> Wilson) and have same password (ncuc1:/root/mailman.passwd,<br>
> which Brenden can also access).<br>
><br>
> Mailing list management tasks are probably familiar enough,<br>
> but here's a quick summary with rough estimate of frequency:<br>
><br>
> (1) Allowing or disallowing messages held because of some rule.<br>
> Common situations are members using a different sender address than<br>
> the one they're subscribed with, too many Cc: addresses, too big<br>
> messages, cross-postings resulting in non-members posting, &c.<br>
> These happen weekly, sometimes more often, even several in one day,<br>
> and usually should be handled quickly (within the same day).<br>
><br>
> (2) Approving subscription requests. This is much less<br>
> frequent and tends to happen in bursts a couple of times a<br>
> year, especially the EC list after elections and the discuss<br>
> list after admitting new members, occasionally at other times,<br>
> like when someone changes their address.<br>
> (The EC list is exceptional in that unsubscribe also needs<br>
> moderator approval.)<br>
> And of course if working teams or the like start getting<br>
> more active using their lists they may increase this, but then<br>
> it might make sense to delegate subscription approvals to<br>
> whoever coordinates the team.<br>
><br>
> Mailman has distinct administrator and moderator roles,<br>
> moderator basically just doing the two tasks above, i.e.,<br>
> approving or disapproving messages and (un)subscriptions,<br>
> and it might well make sense to have, say, two administrators<br>
> for the lot and in addition moderator rights to others in<br>
> some lists (whenever someone complains about too slow<br>
> moderation in some list, offer to make them moderator...)<br>
><br>
> (3) Mass subscriptions. I'll mention this separately from<br>
> the above, as it cannot be done with the moderator password<br>
> and is technically somewhat different. Not difficult though,<br>
> usually it's simply cut'n'pasting list of addresses.<br>
><br>
> (4) Creating new lists. Infrequent, never really urgent, easy.<br>
> The mail system has been set up to recognize new lists<br>
> automatically as long as they use addresses of the form<br>
> <a href="mailto:something@lists.ncuc.org">something@lists.ncuc.org</a>, so all it takes is the Mailman list<br>
> creation form (<a href="http://lists.ncuc.org/cgi-bin/mailman/create" target="_blank">http://lists.ncuc.org/cgi-bin/mailman/create</a>) -<br>
> no need to worry about editing alias files or whatever various<br>
> documents talk about.<br>
><br>
> (5) Adjusting list settings, like maximum messages size &c.<br>
> Rare, usually only needed after list creation, but sometimes<br>
> needed to handle spam attacks or temporarily moderating some<br>
> list member who's gone crazy &c.<br>
><br>
> That's about it. There are also some list-related tasks that<br>
> I've omitted, but they're either one-off things that have been<br>
> done already (general mail system settings) or such that they<br>
> usually aren't done at all (like messing with archives), and<br>
> also technically belong to linux admin (cannot be done with<br>
> the web GUI).<br>
><br>
> --<br>
> Tapani Tarvainen<br>
> _______________________________________________<br>
> E-team mailing list<br>
> <a href="mailto:E-team@lists.ncuc.org">E-team@lists.ncuc.org</a><br>
> <a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/e-team" target="_blank">http://lists.ncuc.org/cgi-bin/mailman/listinfo/e-team</a><br>
<br>
_______________________________________________<br>
E-team mailing list<br>
<a href="mailto:E-team@lists.ncuc.org">E-team@lists.ncuc.org</a><br>
<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/e-team" target="_blank">http://lists.ncuc.org/cgi-bin/mailman/listinfo/e-team</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>---------------------------------------------------------------<br>Joly MacFie 218 565 9365 Skype:punkcast<br>WWWhatsup NYC - <a href="http://wwwhatsup.com" target="_blank">http://wwwhatsup.com</a><br>
<a href="http://pinstand.com" target="_blank">http://pinstand.com</a> - <a href="http://punkcast.com" target="_blank">http://punkcast.com</a><br> VP (Admin) - ISOC-NY - <a href="http://isoc-ny.org" target="_blank">http://isoc-ny.org</a><br>
--------------------------------------------------------------<br>-
</div>