[ uunet!user1.channel1.com!benny writes: ]
>
> I've recently come across a problem with command words causing posts to
> bounce as admin requests. The word "s**scribe" within the text of a
> message sent to an unmoderated list, caused that post to bounce to me as a
> subscription attempt. Is this normal? The email wasn't addressed to the
> majordomo, but rather to the list@domain.com. I'm guessing this would
> cause the same result if any of the list commands were used, although I
> haven't tested it. Is there a workaround to stop this from occurring?
Have you noticed any of these particular sections when you've set up a
list config file?
# administrivia [bool] (yes) <resend>
# Look for administrative requests (e.g. subscribe/unsubscribe) and
# forward them to the list maintainer instead of the list.
administrivia = yes
# taboo_body [regexp_array] (undef) <resend>
# If any line of the body matches one of these regexps, then the
# message will be bounced for review.
taboo_body << END
END
Or this when setting up the majordomo.cf file?
# Common things that people send to the wrong address.
# These are caught in the first 10 lines of the message body
# if 'administrivia' is turned on and the message isn't marked approved.
#
# The code that catches this should transparently redirect
# majordomo commands to majordomo. That would give the additional
# advantage of not having to add to this silly construct for
# each new majordomo command.
#
$admin_body = <<'END';
/\badd me\b/i
/\bdelete me\b/i
/\bremove\s+me\b/i
/\bchange\b.*\baddress\b/
/\bsubscribe\b/i
/^sub\b/i
/\bunsubscribe\b/i
/^unsub\b/i
/\buns\w*b/i
/^\s*help\s*$/i
/^\s*info\s*$/i
/^\s*info\s+\S+\s*$/i
/^\s*lists\s*$/i
/^\s*which\s*$/i
/^\s*which\s+\S+\s*$/i
/^\s*index\s*$/i
/^\s*index\s+\S+\s*$/i
/^\s*who\s*$/i
/^\s*who\s+\S+\s*$/i
/^\s*get\s+\S+\s*$/i
/^\s*get\s+\S+\s+\S+\s*$/i
/^\s*approve\b/i
/^\s*passwd\b/i
/^\s*newinfo\b/i
/^\s*config\b/i
/^\s*newconfig\b/i
/^\s*writeconfig\b/i
/^\s*mkdigest\b/i
END
If you still haven't figured it out, set 'administrivia = no', but
strictly at your own risk.
--
Dave Wolfe
References:
|
|
