mailman
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Mailman's Approval Duties Denied Me.


From: Ralph Corderoy
Subject: Re: Mailman's Approval Duties Denied Me.
Date: Fri, 23 Feb 2018 01:19:24 +0000

Hi Bob,

> > http://lists.nongnu.org/archive/html/nmh-announce/2018-02/msg00001.html

Thanks for your analysis of that list's problems, and how they apply to
the other two nmh ones I admin too.  I'll carry out those suggestions
tomorrow.

> The problem you saw today is that the sender of that message is in the
> accept_these_nonmembers list.  Therefore mail for that address will be
> shipped right through without delay.  I suggest clearing that list.
> However that is the only address there.  That does suggest that
> someone only recently (such as today maybe) approved that message from
> the summary page and added that sender to the accept list.

`norm', a nice guy, is an octogenarian user of nmh, and one of its
original authors as MH back at Rand Corp.  He gives us useful insight,
but would never need to post to announce, or have been put on that list.

Also, if he was on it when his email arrived then Mailman wouldn't have
sent me this `requires approval'.

    Received: from lists.gnu.org ... by mailwash26.pair.com ... 22 Feb 2018 
11:51:42 -0500
    Received: from localhost ... by lists.gnu.org ... 22 Feb 2018 11:51:40 -0500
    Received: from localhost ... by lists.gnu.org ... 22 Feb 2018 11:51:39 -0500
    Subject: Nmh-announce post from address@hidden requires approval
    From: address@hidden
    To: address@hidden
    Message-ID: <address@hidden>
    Date: Thu, 22 Feb 2018 11:51:38 -0500

norm's email was `Date: Thu, 22 Feb 2018 08:51:22 -0800' so it matches,
with Mailman sending a few seconds later.

> Third if you suspect that someone else also has the password to the
> mailing list admin interface then I suggest changing that password.

I changed all three to distinct passwords when I was made admin.  The
other two main developers didn't want to get involved so I've told no
one.  They're styled like `8nTdAEjdn2q'.

> > I've turned on emergency list moderation in the hope that will flag
> > up
>
> Good.  That is always appropriate when there are such issues.

Yep, gives me breathing space.

That norm was added to accept_these_nonmembers suggests it's one of the
moderator helpers that's used to keeping future workload down by
updating those lists as they approve, discard, etc.  I'm pretty sure I
cleared it from the historic cruft it had when I became admin because I
wanted to vet each to prevent noise.

> The Mailman log says only:
> 
> Feb 22 12:30:40 2018 (26099) nmh-announce: held message approved,
> message-id: <address@hidden>
> 
> And that is all I know.  Time on lists.gnu.org is -0500 US/Eastern.

That matches when the held-up email continued on its journey.  The email
that arrived here from the list has Received that give `from', `by', and
date as

    shell1.rawbw.com  eggs.gnu.org         2018-02-22 11:51:33 -0500
    Debian-exim       eggs.gnu.org         2018-02-22 11:51:37 -0500
    eggs.gnu.org      lists.gnu.org        2018-02-22 11:51:38 -0500
    localhost         lists.gnu.org        2018-02-22 12:30:45 -0500
    lists.gnu.org     mailwash26.pair.com  2018-02-22 12:30:47 -0500

> I suggest changing the list password.

Sorry, it wasn't me, and no one else knows them.  (Ignoring the normal
Mailman thing of storing them plain and sending reminders.)

This thing where the three nmh lists don't have `helper moderation' any
more, is that a mechanical device where their queue contents simply
aren't presented to helpers, or a `please remember to skip over those'
where folks could be fallible?  I'm not on a witch hunt, just trying to
lessen the chances next time.  :-)

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy



reply via email to

[Prev in Thread] Current Thread [Next in Thread]