Because of oddities in permissions, it is possible that when you run

mailmanctl -u, you might not be able to completely delete a list
through the web.  This is because the archives are written with the
group of the mailmanctl script, which can be changed if that's not
root, but ttw list deletion will try to delete the archive as group
mailman.  If the users don't match (and they usually won't),
permission crash.

This just includes a warning and some helpful information in the
docstring.

1 files changed, 6 insertions, 0 deletions

diff --git a/bin/mailmanctl b/bin/mailmanctl
index 2bd3db7cf..0292e1f38 100644
--- a/bin/mailmanctl
+++ b/bin/mailmanctl
@@ -56,6 +56,10 @@ Options:
         and the program is run as the current user and group.  This flag is
         not recommended for normal production environments.
 
+        Note though, that if you run with -u and are not in the mailman group,
+        you may have permission problems, such as begin unable to delete a
+        list's archives through the web.  Tough luck!
+
     -s/--stale-lock-cleanup
         If mailmanctl finds an existing master lock, it will normally exit
         with an error message.  With this option, mailmanctl will perform an
@@ -313,6 +317,8 @@ def main():
 
     if checkprivs:
         check_privs()
+    else:
+        print _('Warning!  You may encounter permission problems.')
 
     # Handle the commands
     command = args[0].lower()