> What you want is "access_rules", the generalized access
> control mechanism.
> To consult the list owner on posts not coming from ti.com,
> use a stanza
> like:
>
> # Consult the owner if the user's host doesn't end in "ti.com"
> post
> consult
> $host !~ /ti\.com$/
>
> You can do a rather large number of things using this
> mechanism. You can
> restrict subscriptions (and indeed any command) this way as well.
I'm not at all familiar with mj2 options but the above stanza appears that
the original message will be sent to the owner of the mailing list if the
sender is not permitted to post to this mailing list. Then the owner has
the option to approve the posting of the message or to reject it. Depending
on the owner, this could take hours or days or maybe never. Meanwhile the
sender is thinking that his message was actually sent because he never
received any error message back. Is there also another option in mj2 to
automatically reject the original message and send an error back to the
sender? We have implemented an automatic rejection on our mj1 and do not
want to give it up when we go to mj2.
Regards,
Glen Hansel
Follow-Ups:
|
|
