On Tue, 30 Sep 1997, Jeffrey Goldberg wrote:
> Date: Tue, 30 Sep 1997 18:11:58 +0100 (BST)
> From: Jeffrey Goldberg <J.Goldberg@cranfield.ac.uk>
> To: Nick Metrowsky <email@example.com>
> Cc: majordomo-users@GreatCircle.COM
> Subject: Re: Bridging Majordomo Mailing Lists and Newsgroups
> On Tue, 30 Sep 1997, Nick Metrowsky wrote:
> > [...] I was
> > just asked to see if there is a away for messages going to a majordomo
> > mailing list can be sent to a newsgroup and vica-versa.
> We've cobbled together a couple of perl scripts that we use for
> local newsgroups/mailing lists. It's not pretty, and the scripts
> are not well built.
> The basic idea is to have the newsgroup "moderated", but have the
> moderator email address go to two things. one to send to the
> real list and the other to a script that automatically approves
> the news post.
> Eg. We have a moderated newsgroup
> cran.comp.applic.patran and the moderator is
> That address has the following
> cran-comp-applic-patran-request: "|/usr/info/majordomo/wrapper majordomo -l cran
> cran-comp-applic-patran: c-c-a-patran-list, c-c-a-patran-post
> c-c-a-patran-post: "|/usr/info/news/mail2news/post-approved cran.comp.applic.patran"
> c-c-a-patran-list: "|/usr/info/majordomo/wrapper resend -l cran-comp-applic-patran cran-comp-applic-patran-outgoing"
How can one accomplish this if news server and Mj were on different hosts?
> post-approved is a very simple script that takes in a mail message,
> adds in an Approved: and talks NNTP.
I'd be very interested to see your script; would you be so kind and post
it here, or send it to me directly. I run innd on different host than Mj.
> So, this gets things working in both directions with no looping. It
> wouldn't work if we wanted the group to be functionally moderated.
How is the group moderated, then?
> We are using dnews, but there is nothing dnews specific about how this
> is done.
_/ _/_/_/ _/ ____________ __o
_/ _/ _/ _/ ______________ _-\<,_
_/ _/ _/_/_/ _/ _/ ......(_)/ (_)
_/_/ oe _/ _/. _/_/ ah firstname.lastname@example.org