Re: MODERATOR (NOT MODERATORS?) FOUND for rec.photo.moderated, comp.std.announce, comp.newprod, and comp.simulation

Rayner Lucas <usenet202101@magic-cookie.co.ukNOSPAMPLEASE> wrote:

ahk@chinet.com says...

. . .

I'm personally in the same boat. Has someone written a parser that I
could modify to strip Mail headers, leaving the proto article
otherwise intact to be injected into Usenet?

I'm a clueless git with respect programming languages, but I can
follow patterns if I discover other headers added by Mail servers that
require stripping.

If you're on some sort of Unix system, you might actually be able to do
most of the work using just the 'formail' mail-formatting utility: this
has options to strip/append/rename headers, and/or keep only the headers
you specify.

Ah. That I might be able to learn. Thank you.

PyModerator takes the approach of creating a proto-article using only
the following headers from the original email message:

Does it retain or strip X- headers?

Subject
From
Reply-to
Organization
References
Newsgroups
Followup-to

It uses its own simplistic parser to create a dictionary of headers
(ParseMessageLines() in serverFiles.py), but if I were writing it from
scratch I'd use email.parser from the standard library.

Thanks

STUMP, meanwhile, strips some headers and renames others, using a
combination of formail and Perl regular expressions (see
bin/submission.pl and bin/processApproved in the STUMP source tree).
Again, this probably isn't the best way; using a module such as
Email::Simple or Email::MIME and keeping only a short list of allowed
headers might be more sensible.

STUMP and WebSTUMP are overkill for the low-volume newsgroup.

My succession plan is going to be begging more of the group's regulars
to step up. I volunteered but I'm kind of stuck.

Respect to you for stepping up. We've also found that getting more
volunteers is a difficult task.

I haven't solved the problem yet, and let me be the first to object to
my own moderator succession plan as wishful thinking on my part.