hello everyone. just recently subscribed, i'm an admin working out of
cambridge, massachusetts.
i've made some modifications to our local copy of majordomo (1.94.4) that
i should explain ahead of asking my question.
many of the local shell users on this system are former or current unix
systems and list administrators, and they asked if i could somehow set up
majordomo in such a way that they could edit their list config files in
the shell, rather than editing those files and emailing them to the
parser. i run a similar system that allows apache vhosts to edit their
own <virtualhost> configs.
interested in the challenge, i set out to implement the change. i started
making changes with a mind to adding these features without removing any
existing functionality. my design is as follows.
majordomo's listdir is /usr/lists. within that directory, each directory
has its own directory, in which the subscription and config files are
kept. ie:
/usr/lists majordom.lists drwxr-x--x
/usr/lists/example tj.lists drwxrws---
example tj.lists -rw-rw----
example.config tj.lists -rw-rw----
i made changes to majordomo to accommodate the additional directory,
mostly just changes to functions dealing with file paths.
recently, i discovered an embarrasingly giant hole in my testing:
do_unsubscribe is broken. it is currently impossible to unsubscribe from
any list via email.
the break occurs with the chown() function called from
do_unsubscribe. the error is majordomo_abort, with the line failed and
the error "operation not permitted".
my best explanation is that since majordomo is running as majordomo, it's
not allowed to chown the list files back to the list owner.
i'm looking for suggestions to solve the issue without further reducing
any functionality. now that some of these originally low traffic lists
are picking up these same users who were excited to edit their configs by
hand are rapidly growing weary of hand-unsubscribing list members.
any help y'all could provide would be much welcome.
thanks.
|tj
Follow-Ups:
|
|
