> jb> - Moderated (requires Approved: <passwd>)
> Why does it have to be moderated?
Only one person publishes the newsletter. It is not a
'discussion' area. I've been doing this semi-manually via
Pegasus distribution list for over a year and don't want to
flood people with email they're not expecting. (A large
maority of subscribers are in Europe/Asia where they pay
for connect time by-the-minute.)
> If you have only one person who is allowed to post, why
> not explicitly allow them to post? You can do this by
> putting their address in a file (in the list directory)
> like list.allow and setting restrict_post = list.allow and
> moderate = no. If anyone else tries to post, everything
> behaves as if the list were moderated. (This is a bit
> more difficult if you don't have access to the machine
> running the lists.)
I hesitate to use any feature that says '# This mechanism
will be replaced in a future version of majordomo/resend.',
and might not work next week.
> jb> The basic malfunction is that the goofball multipart
> jb> stuff from Eudora prevents Maj from seeing the
> password in the first
> jb> line as applied to the 'original' post.
> Is it really impossible to get Eudora to just add an
> Approved: header?
> That would also bypass the whole problem.
1st I never would have guessed that. Doc says 'Approved:
password in first line of message', and 'header' is not
2nd Without some stripping process the password would be
passed on in the header of the outgoing msg? Dunno, unless
it really would be handled same as 'message password' and
3rd Unless absolutely necessary I don't wanna need to teach
users new tricks just to get a list to work. This one
moderator is someone who asked me 'what's uuencode?'. Good
guy, but shouldn't need to learn to jump through hoops just
to attach a file to a message. Also, if this ever happens
again, I have to teach every new moderator how to do it.
4th Poster might want/need to post from varying emailers.
Either need to do the 'user header' thing for each emailer,
or cant't post at all. I've tried Win16 Eudora and Pegasus,
Linux xfmail and Pine, and moderator has also tried Win32
MSIE and NN. So far Pegasus is the -only- thing that can do
> jb> So, does anyone know of any fix for this problem? A
> procmail 'message
> jb> massager' script?
> Maybe, but the first method seems the easiest for
I don't mind doing a little extra work myself if it saves
me and a lot of other people excessive annoyance/work.
> (Majordomo-workers will note the synchronicity; we have
> been discussing how
> to deal with approval of multipart messages today.)
I see mention in the archives about scanning further than
the 'first line' for 'Approved: passwd', that it is 'not
easy'. I'm gonna give a try at procmail to do that for now.
Scan for only the -first- 'Approved:', strip it, add it as
the first line, and pass it on. Don't want to scan for more
than one Approved:, I can conceive of some knucklehead
cracker sending a msg with several thousand Approved: lines
just looking for the password.
Have a :) day!