Looks like "Moderator" password is a non-issue[1].
"Admin" passwords were changed earlier, ... so we should be in
pretty good shape at this point.
footnotes/references/excerpts:
1. once upon a time the "Moderator" password was set. The one I had in
my notes was, I believe, passed to me the same time the "Admin" password had
been much earlier passed to me. I'm also fairly certain "way back then"
I verified that each password worked on each of the lists. Seems "Moderator"
password/…
[View More]functionality is disabled (as we desire it), as A) I checked, and
the old "Moderator" password no longer works, and B) the GUI admin stuff
quite effectively states that the "Moderator" role only works if both a
password is set for it, and an email is set for "Moderator" - and I
checked and all three lists have no email set for "Moderator" - so I believe
that effectively disables any "Moderator" capability or login - so I think
we're well covered there.
Quoting "Rick Moen" <rick(a)linuxmafia.com>:
> Quoting Michael Paoli (Michael.Paoli(a)cal.berkeley.edu):
>
>> Thanks - got it (from earlier encrypted contents you sent me) and verified
>> it authenticates.
>
>> Also, as you mentioned, "Moderator" password....
>
> I recommend against ever using this function, by the way. So, there's
> no point in setting its password. (I can detail the reason for that
> recommendation if anyone's interested. Long story. Short version is
> that it leads directly to mishaps that the person wielding that password
> cannot fix.)
>
>> It's quite possible many of the "misconfiguration" changes may have been
>> done - perhaps by someone who has "Moderator" password, and may not
>> even have "Admin" password.
>
> I don't think so, because I'm pretty sure nobody has set that password.
> However, the mishaps I allude to above involve someone accidentally
> checking a "autodiscard" or "ban" control on the admin queue page and
> submitting changes, then being unable to remove that address from the
> autodiscard or ban rosters upon realising his/her mistake, because those
> rosters are on an admin page to which moderators lack access.
>
> So, in theory, someone wielding a moderator password could have
> accidentally put Christian Einfeldt's address on the autodiscard list.
> All the other changes I discussed are possible only with a listadmin
> password.
>
>> If you don't want to be bothered with changing the "Moderator" password
>> (you already covered "Admin" - Thanks!) ... just say the word
>> and I'll take care of "Moderator" password.
>
> You're welcome to set it to something obscure and then forget what it
> is. That's probably the smartest thing to do with it. ;->
[View Less]
Somehow, it's reassuring to know that there are still pushy recruiters
who think it's somehow your problem that they were not permitted to send
to a totally inappropriate mailing list. It reassures me that nothing
fundamental has changed.
(I tried to give him useful assistance, though.)
----- Forwarded message from Mike Lee <mike(a)silverkeyinc.com> -----
Date: Wed, 5 Aug 2009 11:25:11 -0400
From: Mike Lee <mike(a)silverkeyinc.com>
To: balug-announce-owner(a)lists.balug.org
X-…
[View More]Spam-Status: No, score=0.8 required=4.0 tests=BAYES_50 autolearn=ham
version=3.2.5
Subject: FW: Request to mailing list BALUG-Announce rejected
Is there another way to get info to your people about this position?
Mike Lee, CEO/Founder
mikelee(a)silverkeyinc.com
mike(a)silverkeyinc.com
Twitter - silverkeyinc
http://www.linkedin.com/in/mikesilverkey
Click here to view current job openings.
408.257.1700
408.257.1717f
360.904.6485c
www.silverkeyinc.com
"Life is like a taxi - whether you're going anywhere or not, the meter keeps on ticking."
-----Original Message-----
From: balug-announce-bounces(a)lists.balug.org [mailto:balug-announce-bounces@lists.balug.org]
Sent: Wednesday, August 05, 2009 8:14 AM
To: Mike Lee
Subject: Request to mailing list BALUG-Announce rejected
Your request to the BALUG-Announce mailing list
Posting of your message titled "Sr. systems engr needed;
cash-positive company"
has been rejected by the list moderator. The moderator gave the
following reason for rejecting your request:
"balug-announce is simply not a jobs mailing list. Please see
http://lists.balug.org/listinfo.cgi/balug-announce-balug.org for
details. "
Any questions or comments should be directed to the list administrator
at:
balug-announce-owner(a)lists.balug.org
----- End forwarded message -----
----- Forwarded message from Rick Moen <rick(a)linuxmafia.com> -----
Date: Wed, 5 Aug 2009 09:23:28 -0700
From: Rick Moen <rick(a)linuxmafia.com>
To: Mike Lee <mike(a)silverkeyinc.com>
Subject: Re: FW: Request to mailing list BALUG-Announce rejected
Organization: Dis-
Quoting Mike Lee (mike(a)silverkeyinc.com):
> Is there another way to get info to your people about this position?
Short answer: no.
The only exception is that companies that have recently given a technical
presentation at a BALUG meeting, or have a confirmed upcoming technical
presentation, are permitted to send _a_ jobs solicitation to balug-talk
(http://lists.balug.org/listinfo.cgi/balug-talk-balug.org).
You may wish to consider the SVLUG Jobs mailing list, and other places
recommended on http://lists.svlug.org/lists/listinfo/jobs .
----- End forwarded message -----
[View Less]