Moin!
I'm having little trouble with a list that ought to be moderated. The documentation of SmartList says:
------------------------------------------------------------ http://www.hartzler.net/smartlist/Manual.html#3f
3f.Moderated lists ---------------
First create a file named "moderators", it should contain the fully qualified mail addresses of all the moderators for this list (i.e. just local usernames are not sufficient, at least include an @host or host! ). Then uncomment the appropriate "moderated_flag" line in rc.custom.
On Thu, Nov 01, 2001 at 10:39:04AM +0100, Martin Schulze wrote:
Moin!
I'm having little trouble with a list that ought to be moderated. The documentation of SmartList says:
The documentation ist wrong since you don't even need to supply a moderator address after "Approved: ". Only the moderator password is required.
Someone has to edit the manual ...
:0 * !$^Approved:.*$moderator_PASSWORD | formail -R"From X-Envelope-From:" -uDate: -iReturn-Receipt-To: \ -iRead-Receipt-To: -iAcknowledge-To: \ -A "X-Diagnostic: Unapproved submission to $list" \ -A "X-Diagnostic: Approve with Approved: moderator" | \ $SENDMAIL $sendmailOPT \ `cat moderators || echo "${maintainer:-$listmaster}"`
PS: I find it funny having to find out that the SmartList list is driven by Mailman these days. Is that a call for change for users?
Most SmartList users don't like this. The university hosting SmartList and procmail since many years were choosing Mailman. That's fashion and as long we don't have to read html mail it's better than not to have a reliable host.
Werner
Moin!
Werner Reisberger wrote:
On Thu, Nov 01, 2001 at 10:39:04AM +0100, Martin Schulze wrote:
Moin!
I'm having little trouble with a list that ought to be moderated. The documentation of SmartList says:
The documentation ist wrong since you don't even need to supply a moderator address after "Approved: ". Only the moderator password is required.
*sigh* And the moderation password has to be shared among all people who have posting permission on such a list. When one is kicked out of retires the password for all others have to be changed. That doesn't sound quite sane for me...
However, if the variable moderator_PASSWORD is set like follows:
moderator_PASSWORD=(joey@host.domain|(foo|bar)@fuzzy.org)
the mechanism works as I thought before, and no password has to be shared among several people
Someone has to edit the manual ...
Maybe you want to add some blurb describing the above setting.
Regards,
Joey
smartlist@lists.rwth-aachen.de
-
Martin Schulze -
Martin Schulze -
Werner Reisberger