> but it "I" still have a problem. when a message come to the list owner
> for approval on a moderated list.
> how does he tag it as approvled? we use pine as the mail reader.
One of my list moderators has the same problem. She uses Pine too, and
Pine doesn't allow for piping of messages through the "approval" script.
She can't save the message and then invoke the approval program on the
file, either, because she's on some weird, distributed system that's not
Unix compatible and handles remailed messages in a really weird manner
(it's complicated but let's just say it's through Carnegie Mellon U. and
that should suffice! :-)
Anyway, here's how she approves messages manually:
Just save the message, trim the Received headers, add an "approved"
line as the very first line, and send it to the *list* itself.
Yes, that's to *list* and not to majordomo. This is how you approve a
message, manually, to go to the list. Just remember that *commands* go
to *majordomo*, whereas *messages* go to the *list* and you'll be fine.
The message would start like this (message, itself, borrowed from the
bass mailing list :-)
Approved: password
Date: Tue, 23 May 1995 13:44:17 -0600 (MDT)
From: EDWARDD@somesystem.EDU (Edward Someguy)
To: Bass Mailing List <bass>
Subject: Help with 1259 subs; I want to build BIG speakers!
Boy, I sure wish I had some test equipment for this speaker building stuff.
All I have is my ears and a RS SPL meter and some test tones from the
Stereophile disk. Anyway I did some nearfield measurements (2" off of the
dust cap at 110 db) on the 1259 subs and hey, they got no deep bass. The
frequency sweeps are given below:
[...]
If you get the password wrong, it should get caught as an admin request,
unless you really mess up the syntax :-)
--
Diane Close
close@lunch.engr.sgi.com
I'm at lunch all day. :-)
Follow-Ups:
References:
|
|
