I find myself confused on how the "uns?bscribe_policy" configuration
option works in Majordomo 1.94.5. In particular, I wish to know if
there is a way to require owner approval when a list member sends an
uns?bscribe request.
My experience is that irregardless of how I set this option, a user
can sucessfully uns?bscribe themself from a list.
I have looked at the majordomo code and it seems that the uns?bscribe_policy
only pertains when the requester does not match the subscriber address.
However, the comments in the configuration file indicate otherwise:
# unsubscribe_policy [enum] (open) <majordomo> /open;closed;auto;op
# One of three values: open, closed, auto; plus an optional
# modifier: '+confirm'. Open allows people to unsubscribe
# themselves from the list. Auto allows anybody to unsubscribe
# anybody to the list without maintainer approval. The existence of
# the file <listname>.auto is the same as specifying the value
** # auto. Closed requires maintainer approval for all unsubscribe
# requests to the list. In addition to the keyword, if the file
# <listname>.closed exists, it is the same as specifying the value
# closed. Adding '+confirm', ie, 'auto+confirm', will cause
# majordomo to send a reply back to the subscriber if the request
# didn't come from the subscriber. The reply includes a
# authentication number which must be sent back in with another
# subscribe command. The value of this keyword overrides the value
# supplied by any existent files.
The comments in "majordomo" describe a different situation though:
# Check to see if this request is approved, if the unsub policy is
# auto, or if the subscriber is the person making the request (even
# on a closed list, folks can unsubscribe themselves without the
# owner's approval).
....
# Either the request is approved, or the subscriber is the
# requester, so drop them from the list
Thanks, Michele Tomkin
Follow-Ups:
|
|
