[Mailman-Users] Inconsistent post approval options

Fantastic; this list strips enclosures.
You can see the page at http://www.luannocracy.com/mailman.html

Please help solve this mystery!

It looks to me like eckhardt at satorlaser.com is not a subscriber
to the list. That would explain why there's not moderate bit for you
to clear for this person.

Our list is set up so that non-subscribers get automatically rejected
and told they need to subscribe before posting. Normally we never get
a chance to manually approve (or reject) postings from
non-subscribers.

Filters are applied in an order determined by the GLOBAL_PIPELINE list
in Defaults.py or mm_cfg.py or the list's own pipeline attribute if it
has one. Moderate is not the first filter applied, thus a post from a
Moderated bember could be caught by another filter first. Likewise, a
post from a non-member can be caught by another filter first.

In the case you show, the post was held for:

Reason: Message body is too big: 94200 bytes with a limit of 75 KB

This test is applied in the Hold handler and thus takes priority over
any filters applied by later handlers.

However, both list membership and moderation are handled in the
Moderate handler which normally comes before Hold in the pipeline, so
presumably, the poster of this message is a list member and is not
moderated if this list uses the default pipline.

Except, as Brad correctly notes, this post looks like it came from a
non-member because the "Add to filters" and Ban options are shown as
opposed to the notation that the poster is a list member. Maybe the
list does use a non-default pipeline or maybe I'm missing something in
the sequence of how these are handled.

I seriously doubt that. DongInn, you didn't do anything funky with
the Mailman filter pipeline, did you?
I think we still have a mystery here, then.

He has confirmed that it's the standard pipeline.
Ditto.

Do we? The screen at http://www.luannocracy.com/mailman.html says the
message was held because "Reason: Message body is too big: 94200 bytes
with a limit of 75 KB". Was the message in fact too big? If so, it was
held for a valid reason.

The only issue is whether it should have been held for "moderated
member" instead. If in fact, it was posted by a moderated member, it
should be held for that reason because that test precedes the too big
test.

Likewise if it was posted by a non-member.

But if it was posted by a unmoderated member, it would be held for "too
big" as it was. The fact that the page at the above link seems to
indicate the post is from a non-member is not relevant because it
determines membership status at the time the admindb page was visited,
not at the time of the post. If the poster unsubscribed or changed
e-mail address after posting, the admindb page may not be correct
about membership status.

You could check your mailman subscribe log to determine if the poster
was a member at the time of the post, but this won't give moderation
status. Also it won't show if the member changed his/her e-mail
address.