-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sat, Aug 16, 2008 at 11:18, Matthew Copple mcopple@kcopensource.org wrote:
We went through this just a few months ago, when we reenacted the 30 Years War through the list. The consensus was that the list works as it is.
<snip />
Chris Bier had a neat idea of making a copy of every incoming message to the current list, and sending it to a second list's moderation queue. Combining that with a request that off topic stuff contain [OT] in the subject. I believe that to be the best solution, and am willing to throw my time into moderating. I will also pursue starting an entirely separate mailing list, if for no other reason, then to learn mailman. If I complete that before Chris' split-list idea is in place, there will be fragmentation, and two sets of archives. That would be rather in-elegant, but the best I can do.
There are two mailman capabilities that could deal with this. 1. People use an OT in the subject line for anything not KCLUG or Linux related gets put into a topic which people can subscribe to or related to that, everything not including KCLUG or Linux in the subject line gets filtered into an OT list.
2. A kclug-moderated list gets created getting a duplicate of all posts. It would be a moderated list, and only on-topic posts would be sent to list subscribers.
Mailman Topic Detail: topics_enabled (topics): Should the topic filter be enabled or disabled?
The topic filter categorizes each incoming email message according to regular expression filters you specify below. If the message's Subject: or Keywords: header contains a match against a topic filter, the message is logically placed into a topic bucket. Each user can then choose to only receive messages from the mailing list for a particular topic bucket (or buckets). Any message not categorized in a topic bucket registered with the user is not delivered to the list.
Note that this feature only works with regular delivery, not digest delivery.
The body of the message can also be optionally scanned for Subject: and Keywords: headers, as specified by the topics_bodylines_limit configuration variable.